java-unit-test-expert

To generate JUnit 5 unit tests for a Spring Boot service, provide the service class to generate self-contained, runnable tests using Mockito. It mocks only dependencies, covers normal, error, and boundary cases, and includes all necessary imports and annotations.

You should avoid mocking the system under test in Java unit tests to ensure you are testing actual behavior rather than mock interactions. This skill enforces strict isolation by mocking only external dependencies and DTOs, never the SUT itself.

To fix flaky tests in a Spring Boot 2.1.x project, apply strict mocking rules and robust assertion patterns using JUnit 5 and Mockito. This skill generates self-contained tests with unified numeric comparisons and proper isolation to prevent non-repeatable behavior.

Yes, this approach supports generating tests for Spring Boot controllers by utilizing the @WebMvcTest annotation. It produces runnable controller tests that mock only service dependencies, covering normal, exception, and boundary scenarios with all required imports.

The best way to increase unit test coverage for existing Java code is to design tests covering normal, error, and boundary cases for each non-static, non-private method. This skill generates coverage-driven JUnit 5 tests targeting over 80% line coverage.

Yes, you can use ReflectionTestUtils for private field injection in JUnit 5 tests when necessary. This skill employs robust assertion patterns and ReflectionTestUtils to handle private field injection while maintaining strict dependency mocking and test isolation.