UAST
JUnit 4 test can be JUnit 5
Warning
Sanity
New
Last modified: 03 December 2024Reports JUnit 4 tests that can be automatically migrated to JUnit 5. While default runners are automatically convertible, custom runners, method- and field- rules are not and require manual changes.
Example:
import org.junit.Assert;
import org.junit.Test;
public class RelevantTest {
@Test
public void testIt() {
Assert.assertEquals("expected", "actual");
}
}
After the quick-fix is applied:
import org.junit.jupiter.api.Assertions;
import org.junit.jupiter.api.Test;
public class RelevantTest {
@Test
public void testIt() {
Assertions.assertEquals("expected", "actual");
}
}
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
JUnit5Converter
This inspection requires that the JUnit 5 library is available in the classpath, and JDK 1.8 or later is configured for the project.
Inspection Details | |
---|---|
By default bundled with: | |
Can be installed with plugin: | JUnit, 243.23126 |
Thanks for your feedback!
Was this page helpful?