jvm-testing

You can standardize JVM tests by applying stack-agnostic patterns for JUnit 5, Mockito, AssertJ, and Testcontainers across Java projects. This approach ensures consistent unit, parameterised, and integration testing without tying your tests to a specific framework.

The best way to mock dependencies without overusing them is to apply Mockito mocking discipline. This skill guides you toward targeted mocking practices that prevent brittle tests and maintain expressive assertions using AssertJ.

Yes, you can use Testcontainers for integration testing in any JVM application. This skill covers spinning up real infrastructure like databases and message brokers to run reliable integration tests across stack-agnostic Java projects.

No, this JVM testing skill explicitly excludes Spring-specific test slices like @SpringBootTest, @WebMvcTest, and @DataJpaTest. Those framework-specific testing utilities are handled by dedicated spring-boot-plugin skills instead.

You should use AssertJ for assertions in your JVM tests to write expressive, fluent assertions that improve test readability. This skill incorporates AssertJ alongside JUnit 5 and Mockito to establish high-quality, standardized testing patterns.