Releases
This page lists the changes in each ReqCover release, newest first; for upgrade steps see Upgrading.
0.0.12
Section titled “0.0.12”Released 2026-11-16. GitHub release v0.0.12
Highlights
Section titled “Highlights”- 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. @ForRequirementon test classes (#71): for JUnit and TestNG, a requirement on a test class is covered when at least one test in the class passes.
Behaviour changes
Section titled “Behaviour changes”- Invalid coverage settings fail the build.
reqCover.minimumRequiredCoveragePercentmust be a number from 0 to 100 andreqCover.failIfBelowMinimummust betrueorfalse. Otherwise ReqCover logs an error, writes the report and fails the build, in JUnit, TestNG and Cucumber. Before,100%silently became0.0and 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.
Provisional behaviour
Section titled “Provisional behaviour”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.
0.0.11
Section titled “0.0.11”Released 2026-11-16. GitHub release v0.0.11
Highlights
Section titled “Highlights”- Cucumber support (#15) with the new
reqcover-engine-cucumbermodule. - Configurable report directory (#70): the new
reqCover.reportsDirsetting lets Maven users write the reports totarget/.
Cucumber
Section titled “Cucumber”- 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, thenjunit-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.
Report directory
Section titled “Report directory”- New setting
reqCover.reportsDirfor JUnit, TestNG and Cucumber. The default is stillbuild/reports/tests/reqcover.
For reporter authors
Section titled “For reporter authors”RequirementsCoverageReporterhas a new method,report(tracker, reportsDirectory). Its default implementation callsreport(tracker), so existing reporters keep working. See Reporters.
Known issues
Section titled “Known issues”- In Java, write
@ForRequirement(id = "#requirementId"). The short form only works in Kotlin.
0.0.10
Section titled “0.0.10”Released 2026-11-13. GitHub release v0.0.10
Highlights
Section titled “Highlights”- TestNG support with the new
reqcover-engine-testngmodule, configured through JVM system properties ortestng.xmlsuite 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.
Breaking changes
Section titled “Breaking changes”- Module renamed:
reqcover-junit-jupitertoreqcover-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; usereqCover.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 SurefireconfigurationParameters). - 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.xmlsuite 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.requirementsUrisis 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
@TestFactorytests 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.
Provisional behaviour
Section titled “Provisional behaviour”These rules may change based on feedback (GitHub issues):
- An empty
reqCover.requirementsUrisgives 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.failIfBelowMinimumcounts astrue.
Known issues
Section titled “Known issues”- #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.
0.0.9 and earlier
Section titled “0.0.9 and earlier”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.requirementsUristogether withreqCover.requirementsUri(fixed in 0.0.10). - 0.0.1 to 0.0.8: initial
@ForRequirementAPI, JUnit listener, OpenAPI source, support for parameterized tests, XML reporter and a first HTML reporter, and publishing setup.