Spock vs JUnit 5 - Clash of the Titans
summary
Compares Spock and JUnit 5 by examining specific features such as compact syntax, parameterized tests and other testing conveniences, assessing how JUnit 5 (a Java 8-optimized, from-scratch rewrite) stacks up against Spock. Evaluates whether Spock’s advantages remain significant or if JUnit 5 closes the gap, based on a 2018/2019 comparison.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:46Presentation plan
- 2:22Unit testing in Java - historical outline
- 5:19Development
- 6:37Tool support
- 9:25Test structure - BDD-like specification - in general mindbok
- 11:24Test structure - Spock
- 14:19Exception testing - JUnit 5
- 15:14Exception testing - Spock
- 19:20Conditional test execution - JUnit
- 22:49Conditional test execution - Spock
- 25:57Mocking - JUnit 5 • no built-in mocking framework Mockito - first port of call
- 27:40Mocking - Spock • built-in mocking subsystem
- 31:05Parameterized tests - JUnit 5
- 33:46Parameterized tests - Spock
- 41:44Summary - Features comparison
- 42:24Summary - the choice is yours
related talks
42mSpock vs JUnit 5 - Clash of the Titans
47mSpock vs JUnit 5 - Clash of the Titans
45mWhy Use Spock Instead of JUnit Mockito for Your Java Tests
45mWhat to Expect from Spock 2?
51mSpock Framework: The Ultimate Framework for Testing Your Java Applications
46mEasy testing with Spock
18mSpeedup unit testing with the Spock framework
46mSmarter Java Testing with the Spock Framework