JUnit5 is more tolerant regarding the visibilities of Test classes and methods than JUnit4, which required everything to be public. JUnit5 supports
default package, public and protected visibility, even if it is recommended to use the default package visibility, which improves the readability of
code.
But JUnit5 ignores without any warning:
- private classes and private methods
- static methods
- methods returning a value without being a TestFactory
Noncompliant code example
import org.junit.jupiter.api.Test;
class MyClassTest {
@Test
private void test1() { // Noncompliant - ignored by JUnit5
// ...
}
@Test
static void test2() { // Noncompliant - ignored by JUnit5
// ...
}
@Test
boolean test3() { // Noncompliant - ignored by JUnit5
// ...
}
@Nested
private class MyNestedClass { // Noncompliant - ignored by JUnit5
@Test
void test() {
// ...
}
}
}
Compliant solution
import org.junit.jupiter.api.Test;
class MyClassTest {
@Test
void test1() {
// ...
}
@Test
void test2() {
// ...
}
@Test
void test3() {
// ...
}
@Nested
class MyNestedClass {
@Test
void test() {
// ...
}
}
}
