Assertion arguments should be passed in the correct order
org.openrewrite.java.testing.cleanup.AssertionsArgumentOrder
Assertions such as org.junit.Assert.assertEquals
expect the first argument to be the expected value and the second argument to be the actual value; for org.testng.Assert
, it’s the other way around. This recipe detects J.Literal
, J.NewArray
, and java.util.Iterable
arguments swapping them if necessary so that the error messages won't be confusing.
Tags
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite.recipe
artifactId: rewrite-testing-frameworks
version: 2.14.1
Data Tables
Source files that had results
org.openrewrite.table.SourcesFileResults
Source files that were modified by the recipe run.
Source files that errored on a recipe
org.openrewrite.table.SourcesFileErrors
The details of all errors produced by a recipe run.
Recipe performance
org.openrewrite.table.RecipeRunStats
Statistics used in analyzing the performance of recipes.
Usage
This recipe has no required configuration options. It can be activated by adding a dependency on org.openrewrite.recipe:rewrite-testing-frameworks:2.14.1
in your build file or by running a shell command (in which case no build changes are needed):
Add the following to your
build.gradle
file:
Run
gradle rewriteRun
to run the recipe.
See how this recipe works across multiple open-source repositories
The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.
Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.
Contributors
Patrick Way, Patrick, Knut Wannheden, Tim te Beek, Jonathan Schnéider, timo-abele
Last updated