TestCase with non-trivial constructors

Reports test cases with initialization logic in their constructors. If a constructor fails, the @After annotated or tearDown() method won't be called. This can leave the test environment partially initialized, which can adversely affect other tests. Instead, initialization of test cases should be done in a setUp() or @Before annotated method.

Bad example:

  public class ImportantTest {
    private File file;

    public ImportantTest() throws IOException {
      file = File.createTempFile("xyz", ".tmp");
    }

    // ... tests go here
  }

Locating this inspection

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.

JUnitTestCaseWithNonTrivialConstructors

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | JVM languages | Test frameworks

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection JUnitTestCaseWithNonTrivialConstructors

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

IntelliJ IDEA 2025.2

Inspection Details
By default bundled with:	IntelliJ IDEA 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025