The test pyramid and what 'unit' really means, JUnit 5's Platform/Jupiter/Vintage split and the extension model, parameterized and dynamic tests, test doubles taxonomy (dummy/stub/fake/mock/spy — not just Mockito names), Mockito internals (proxy-based), ArgumentCaptor, TestContainers for real databases, TDD red-green-refactor, PITest mutation testing, and JMH benchmarking.
// Lessons
- 01soon
The Test Pyramid — Unit, Integration and E2E in Balance
- 02soon
JUnit 5 Architecture — Platform, Jupiter and Vintage
- 03soon
JUnit 5 Lifecycle — @BeforeAll, @AfterEach and the Order
- 04soon
JUnit 5 Extensions — @ExtendWith and Building a Custom Extension
- 05soon
Parameterized Tests — ValueSource, CsvSource, MethodSource
- 06soon
Test Doubles — Dummy, Stub, Fake, Mock, Spy (The Theory)
- 07soon
Mockito — @Mock, @Spy, @InjectMocks in Depth
- 08soon
Mockito — ArgumentCaptor, Verification Modes and Custom Answers
- 09soon
Spring Test Slices — @WebMvcTest, @DataJpaTest and Context Cost
- 10soon
TestContainers — Real Databases in Tests
- 11soon
TDD — Red-Green-Refactor in Practice
- 12soon
Mutation Testing with PITest and Microbenchmarking with JMH