Misordered 'assertEquals()' arguments
Reports calls to assertEquals() that have the expected argument and the actual argument in the wrong order.
For JUnit 3, 4, and 5 the correct order is (expected, actual). For TestNG the correct order is (actual, expected).
Such calls will behave fine for assertions that pass, but may give confusing error reports on failure. Use the quick-fix to flip the order of the arguments.
Example (JUnit):
assertEquals(actual, expected)After the quick-fix is applied:
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.
MisorderedAssertEqualsArguments
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 MisorderedAssertEqualsArgumentsnote
Actual comment syntax will depend on the code language you are working with
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |