test-migration

JUnit 4 to JUnit 5 migration involves replacing @Before with @BeforeEach, @RunWith with @ExtendWith, and Assert.* with Assertions.*. Tests using @Test(expected=...) should be rewritten with assertThrows(), and the junit-jupiter dependency replaces the legacy junit artifact.

Spring Boot 3.2 tests use JUnit 5 natively, so remove @RunWith(SpringRunner.class) and the junit4 imports. Keep @SpringBootTest with TestRestTemplate, and update imports to org.junit.jupiter.api packages.

Yes, Mockito works with JUnit 5 through the mockito-junit-jupiter dependency. Replace @RunWith(MockitoJUnitRunner.class) with @ExtendWith(MockitoExtension.class) while keeping @Mock and @InjectMocks annotations unchanged.

Annotate the test class with @Testcontainers and declare a static PostgreSQLContainer with @Container. Use @DynamicPropertySource to inject the container's JDBC URL, username, and password into Spring's datasource properties.

Fix failing tests rather than disabling them, since skipped tests hide real regressions. Common fixes include resolving timing dependencies, removing hardcoded assumptions, and updating framework-specific behavior to match the target framework.

Run mvn clean test jacoco:report to generate coverage reports and compare line and branch coverage before and after migration. Configure JaCoCo rules with a minimum covered ratio, such as 0.80, to enforce coverage thresholds in the build.