Level Up Your Automated Tests
summary
A week-long spike adopts Spock + Groovy for the MongoDB Java driver and the team rewrites integration and unit tests, gaining built-in mocking, clearer given/when/then sections and data-driven tests; test readability improves, test count rises, CI (Jenkins/Travis) catches regressions earlier, flaky tests get triaged, and performance-sensitive tests remain in Java. A testing champion nudges culture change and the approach proves worth the language tradeoff.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:15Quiz Show
- 7:16Why we dont write tests
- 14:32How can we change behaviour
- 21:59Testing solutions
- 27:18Easier to read
- 27:49Test names
- 28:04Subject annotation
- 29:18Mock assertions
- 31:48Datadriven testing
- 32:44Colorblind tests
- 33:33Ignore tests
- 34:39Spock
- 38:17Groovy
- 42:34Writing readable tests
- 44:02Writing meaningful tests
- 46:07Conclusion
related talks
35mThe Groovy Way of Testing with Spock
46mEasy testing with Spock
18mSpeedup unit testing with the Spock framework
01h 12mUnit Tests as a Specification
45mWhy Use Spock Instead of JUnit Mockito for Your Java Tests
29mWhy I prefer Spock over JUnit
49mWhat Mr. Spock would possibly say about modern unit testing
42mTimeTest your java applications with Spockline01