Testing done right: From bugs to brilliance
summary
Explains why concise acceptance criteria and code reviews matter, shows a real bug where a test validated Instant not the controller, and argues for TDD plus BDD to catch regressions. Demos: Spring MockMVC, SpringBootTest, Mockito, Cucumber feature files, and SonarCloud linting; warns against mockitis and code-first test generation. Compares the classic testing pyramid to the testing trophy, and gives concrete integration strategies for microservices and contract testing.
AI-written summary · about
chapters (15)
- 0:00Introduction to quality
- 2:47Requirements and criteria
- 7:01Team best practices
- 7:50Introduction to testing
- 9:53Test types and approaches
- 13:19Avoiding code-first development
- 15:25Test-driven development
- 18:26TDD advantages and pitfalls
- 20:55Testing trophy and tools
- 23:27Integrated testing
- 26:20Behavior-driven development
- 29:10MockMvc for BDD testing
- 31:04Cucumber framework usage
- 35:14Microservices testing
- 39:39Conclusion and Q&A
related talks
29mEffective tests and testing effectively
01h 05mMicrotesting
42mUse testing to Develop Better Software Faster
01h 46mHow Java developers should test their applications (RU)
46mHow John Started to Like TDD (Instead of Hating It)
47mFrom Bugs to Brilliance: Testing Toolbox in Action
57mAdvanced Testing Techniques: Tips from the trenches
58mTesting Strategy - New Model, Better Outcomes