JUnit 5 - Shaping the Future of Testing on the JVM
summary
JUnit 5 targets Java 8+ with a modular engine + launcher architecture that separates discovery from execution and ships a JUnit‑4 engine so JUnit‑4/3 and JUnit‑5 tests can run together; the project is crowdfunded (about 54,000 from ~500 backers and four companies donated six weeks each) and already has an Alpha in Maven Central, ~2,000 commits, 19 contributors and 9 open issues for M1. Key, working features shown: the extensible extension model with method parameter resolution and instance post‑processors, conditional test execution, default method test interfaces, nested tests, and Gradle/Maven plugin support.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:21Sam Brannen
- 2:55Agenda
- 3:52Why a New Version of Unit?
- 5:37Modularity in JUnit 4
- 6:15JUnit 4 Runner API
- 10:14Crowdfunding Campaign
- 12:08Roadmap
- 13:15JUnit 5... in a Nutshell
- 14:53Architecture
- 17:54Launcher API
- 19:03TestEngine API
- 20:32JUnit 5 Extension Model
- 25:58JUnit 5 Programming Model
- 28:04Annotations
- 31:05Assumptions
- 36:40Test Names
- 37:28Dependency Injection for Methods
- 42:20Custom Tags
- 43:24Conditional Test Execution
- 44:50Interface Default Methods
- 45:57Nested Test Classes
- 46:42Spring Support for JUnit 5
- 51:13What's Missing?
- 52:42Resources and Feedback Channels
