Include an assertion in tests

org.openrewrite.java.testing.cleanup.TestsShouldIncludeAssertions

For tests not having any assertions, wrap the statements with JUnit Jupiter's Assertions#assertThrowDoesNotThrow(..).

Tags

  • RSPEC-2699

Recipe source

GitHub, Issue Tracker, Maven Central

  • groupId: org.openrewrite.recipe

  • artifactId: rewrite-testing-frameworks

  • version: 2.6.0

Options

TypeNameDescriptionExample

String

additionalAsserts

Optional. A comma delimited list of packages and/or classes that will be identified as assertions. I.E. a common assertion utility org.foo.TestUtil.

org.foo.TestUtil, org.bar

Usage

This recipe has no required configuration options. It can be activated by adding a dependency on org.openrewrite.recipe:rewrite-testing-frameworks:2.6.0 in your build file or by running a shell command (in which case no build changes are needed):

  1. Add the following to your build.gradle file:

build.gradle
plugins {
    id("org.openrewrite.rewrite") version("6.11.2")
}

rewrite {
    activeRecipe("org.openrewrite.java.testing.cleanup.TestsShouldIncludeAssertions")
}

repositories {
    mavenCentral()
}

dependencies {
    rewrite("org.openrewrite.recipe:rewrite-testing-frameworks:2.6.0")
}
  1. 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, Tracey Yoshima, Jonathan Schneider, Knut Wannheden, Patrick, Sam Snyder, Michael Keppler, Tim te Beek, Aaron Gershman

Last updated