JUnit 5 obsolete assertions

Reports any calls to methods from the junit.framework.Assert, org.junit.Assert, or org.junit.Assume classes inside JUnit 5 tests.

Although the tests work properly, migration to org.junit.jupiter.api.Assertions/org.junit.jupiter.api.Assumptions will help you avoid dependencies on old JUnit version.

Example:

  import org.junit.Assert;
  import org.junit.jupiter.api.Test;

  public class MyTest {
    @Test
    public void simpleTest() {
      Assert.assertEquals(4, 2 + 2);
    }
  }

After the quick-fix is applied:

  import org.junit.jupiter.api.Assertions;
  import org.junit.jupiter.api.Test;

  public class MyTest {
    @Test
    public void simpleTest() {
      Assertions.assertEquals(4, 2 + 2);
    }
  }

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.

JUnit5AssertionsConverter

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 | JUnit

Inspection ID: JUnit5AssertionsConverter

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 JUnit5AssertionsConverter

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

IntelliJ IDEA 2025.3

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

Last modified: 03 December 2025