Skip to content

Releases

This page lists the changes in each ReqCover release, newest first; for upgrade steps see Upgrading.

Released 2026-11-16. GitHub release v0.0.12

  • JUnit 5 works again. Since 0.0.10, the JUnit engine forced JUnit Platform 6 on projects, so on JUnit 5 test discovery failed with DiscoveryIssueException. Your project’s own JUnit version is now used; tested with JUnit 5.13.4 and 6.1.3.
  • @ForRequirement on test classes (#71): for JUnit and TestNG, a requirement on a test class is covered when at least one test in the class passes.
  • Invalid coverage settings fail the build. reqCover.minimumRequiredCoveragePercent must be a number from 0 to 100 and reqCover.failIfBelowMinimum must be true or false. Otherwise ReqCover logs an error, writes the report and fails the build, in JUnit, TestNG and Cucumber. Before, 100% silently became 0.0 and turned the check off. See Configuration.
  • The coverage percentage in the log and the XML report always uses a dot (50.0); before, it followed the JVM’s default locale.

These rules may change based on user feedback:

  • A requirement on a test class is covered when at least one test in the class passes.
  • Invalid coverage settings fail the build rather than only logging a warning.

Released 2026-11-16. GitHub release v0.0.11

  • Cucumber support (#15) with the new reqcover-engine-cucumber module.
  • Configurable report directory (#70): the new reqCover.reportsDir setting lets Maven users write the reports to target/.
  • Link a scenario to a requirement with a tag, by default @req:<requirement id>, for example @req:#getUsers/200. A passing scenario covers every requirement it is tagged with. Tags on a feature or rule apply to all its scenarios.
  • Change the tag prefix with reqCover.cucumber.tagPrefix.
  • Register the plugin with cucumber.plugin=dev.reqcover.cucumber.RequirementsCoverageListener.
  • Settings come from JVM system properties, then cucumber.properties, then junit-platform.properties.
  • Works with Cucumber 7 and 8 (tested with 7.31.0 and 8.0.4) and uses your project’s Cucumber version.
  • Same rules as JUnit and TestNG: minimum coverage, failing the build, HTML and XML reports, errors for missing or malformed requirements files.
  • New setting reqCover.reportsDir for JUnit, TestNG and Cucumber. The default is still build/reports/tests/reqcover.
  • RequirementsCoverageReporter has a new method, report(tracker, reportsDirectory). Its default implementation calls report(tracker), so existing reporters keep working. See Reporters.
  • In Java, write @ForRequirement(id = "#requirementId"). The short form only works in Kotlin.

Released 2026-11-13. GitHub release v0.0.10

  • TestNG support with the new reqcover-engine-testng module, configured through JVM system properties or testng.xml suite parameters.
  • Fixes for false coverage results: a broken requirements file, a parameterized test that never passed, or parallel execution could make coverage look better than it was.
  • Module renamed: reqcover-junit-jupiter to reqcover-engine-junit-jupiter (Maven: reqcover-engine-junit-jupiter-jvm).
  • Requires JUnit 6 (Jupiter): on JUnit 5, test discovery fails. Fixed in 0.0.12.
  • reqCover.requirementsUri (singular) removed; use reqCover.requirementsUris. If still configured, the JUnit build fails with an explanation.
  • System properties now also take precedence over JUnit configuration parameters passed to the launcher (for example Gradle configurationParameter(...) or Surefire configurationParameters).
  • Requirements files that are missing, malformed or in an unsupported format now fail the build.

See Upgrading from 0.0.9.

  • TestNG engine with system properties, testng.xml suite parameters and automatic registration.
  • With several TestNG suites, the requirements files of all suites are combined and the strictest coverage settings apply.
  • Warnings when reqCover.requirementsUris is empty and when a requirements file contains no requirements.
  • #67: a malformed or non-OpenAPI requirements file fails the build instead of reporting 100% coverage.
  • #68 (JUnit): parameterized, repeated and @TestFactory tests only cover their requirement if at least one run passes.
  • #69: coverage no longer loses requirements when tests run in parallel.
  • #66: the coverage report is written before the build fails.
  • The HTML reporter is registered automatically.
  • A message that named the wrong properties file was corrected.

These rules may change based on feedback (GitHub issues):

  • An empty reqCover.requirementsUris gives a warning, and coverage is not checked.
  • A requirements file without requirements gives a warning and adds no requirements.
  • One passing run of a parameterized, repeated, data-provider or factory test covers its requirement.
  • With several TestNG suites, a suite that does not set reqCover.failIfBelowMinimum counts as true.
  • #70: reports are always written to build/reports/tests/reqcover/, also with Maven. Fixed in 0.0.11.
  • In Java, write @ForRequirement(id = "#requirementId"). The short form only works in Kotlin.

Early releases, 0.0.1 (August 2025) to 0.0.9 (September 2025), JUnit 5 Jupiter only, published as reqcover-junit-jupiter.

  • 0.0.9: engine support for several requirements sources; requirements files with the same name in several classpath entries are combined. The JUnit listener only honoured reqCover.requirementsUris together with reqCover.requirementsUri (fixed in 0.0.10).
  • 0.0.1 to 0.0.8: initial @ForRequirement API, JUnit listener, OpenAPI source, support for parameterized tests, XML reporter and a first HTML reporter, and publishing setup.

All releases on GitHub