JUnit 5: The Next Step in Automated Testing for Java
summary
JUnit 5 targets a Java 8 baseline and ships as modular Platform/Vintage/Jupiter artifacts, so existing JUnit 4 suites run under Vintage while Jupiter provides the new programming model. Migration includes a junit-jupiter-migration-support dependency to keep rules/runners working; a demo shows a suite passing once that migration artifact is added. Key features shown are assertAll (multiple failures reported), the extension model (replaces rules/runners, supports Mockito/Testcontainers injection), parameterized/dynamic tests, CSV/aggregators, conditional disable, and parallel execution added in 5.3.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:54IBM
- 1:38Why change
- 2:59Modularity
- 3:36Backward Compatibility
- 7:08Migration Requirements
- 8:09Upgrading to JUnit 5
- 14:32Language Changes
- 15:11Extension Framework
- 19:08Dependency Injection
- 22:59Parameterised Tests
- 28:10Repeated Tests
- 31:18Test Interfaces
- 34:55Disable Filtering
related talks
51mJUnit 5 — The New Testing Framework for Java and Platform for the JVM
48mJUnit 5: New Opportunities for Testing on the JVM
51mWelcome to JUnit 5
51mJUnit 5: what's new and what's coming
01h 06mJUnit 5 — New Opportunities for Testing on the JVM
07mJUnit 5
51mJUnit 5
49mJUnit: time to shift into 5th gear!
