- "Write tests. Not too many. Mostly integration."
- Integration tests strike a great balance on the trade-offs between confidence and speed/expense. This is why it's advisable to spend most (not all, mind you) of your effort there.
- biggest thing you can do to write more integration tests is to stop mocking so much stuff
- When you mock something you're removing all confidence in the integration between what you're testing and what's being mocked.
Recorded at SpringOne Platform 2016. Speaker: Adrian Cole Slides: http://www.slideshare.net/SpringCentral/how-to-properly-blame-things-for-causing-latency La...
This is a journey through three attempts to improve observability which are used to highlight the difference between "better monitoring" and "observability".
More and more teams are coming to the realization that automating every single test may not be the best approach. However, it’s often difficult to determine wh…
M. Beccaria, G. Angelis, M. Campostrini, and A. Feo. (2004)cite arxiv:hep-lat/0412020
Comment: 4 pages, 1 figure, Talk presented at Quark Confinement and the Hadron
Spectrum VI, Villasimius, Sardinia, Italy, September 21-25, 2004.
G. Stumme. Proceedings of the 10th International Conference on Conceptual Structures (ICCS 2002), volume 2393 of Lecture Notes in Computer Science, page 2-19. Springer, (2002)
C. Carpineto. Proceedings of the 10th International Conference on Conceptual Structures (ICCS 2002), volume 2393 of Lecture Notes in Computer Science, page 1. Springer, (2002)
C. Hookway. Proceedings of the 15th International Conference on Conceptual Structures (ICCS 2007), volume 4604 of Lecture Notes in Artificial Intelligence, page 59-68. Berlin, Heidelberg, Springer-Verlag, (July 2007)
G. Richmond. Proceedings of the 15th International Conference on Conceptual Structures (ICCS 2007), volume 4604 of Lecture Notes in Artificial Intelligence, page 15-28. Berlin, Heidelberg, Springer-Verlag, (July 2007)