All Classes and Interfaces

Class
Description
Numbers Feature/Scenario titles directly in the source .feature files according to a configured IndexingMode.
Converts a Feature title into a directory-safe camelCase name.
Parses a single Gherkin .feature file and extracts all scenarios.
A single snippet file written for one Feature, within one status.
Gradle task that scans .feature files and writes all scenario titles to a single AsciiDoc file.
DSL extension for the Gherkin-to-AsciiDoc Gradle plugin.
Gradle plugin that registers the generateFeatureDocs task and wires the gherkinToAsciidoc DSL extension into the project.
Scans a directory of Cucumber-JVM glue code (step definition source files) and extracts every @Given/@When/@Then step definition pattern as a compiled Expression.
Controls whether Feature/Scenario titles are numbered directly in the source .feature files, as configured via the indexing DSL property.
Reads and writes ScenarioProgressRecords as newline-delimited JSON (NDJSON), one record per line, sorted by ScenarioProgressRecord.fingerprint() so that git diffs of the persisted file are minimal and stable regardless of scenario reordering or scenarios moving between feature files.
Produces the next ScenarioProgressRecord map to persist, from the previously persisted map and the current run's scenarios.
Configuration for ProgressReportWriter.
Writes an AsciiDoc progress report that breaks scenarios down by ScenarioStatus and summarises the breakdown as a table of counts and percentages.
Renders a progress report from a user-supplied Mustache template, so that the generated AsciiDoc file references the snippets written by SnippetWriter via include:: directives instead of embedding their content verbatim.
Shared explanatory text used by both ProgressReportWriter and ReportTemplateRenderer.
Classifies a ScenarioInfo as ScenarioStatus.LISTED, ScenarioStatus.DEFINED, or ScenarioStatus.IMPLEMENTED based on whether it has steps, and whether every step has matching glue code.
Computes a stable identifier for a scenario from its name alone, deliberately ignoring which Feature file it currently lives in - so ProgressHistoryUpdater keeps recognising the same scenario even after it has been moved between feature files.
Groups ScenarioInfo instances by the Feature they belong to.
Immutable description of a single scenario parsed from a .feature file.
Persisted, per-scenario history of when a scenario first reached each ScenarioStatus stage, keyed by ScenarioFingerprint.fingerprint(String) rather than by feature file location - so the history survives a scenario being moved between feature files.
Implementation progress of a single scenario, as tracked when trackProgress is enabled.
Writes the listed.adoc/defined.adoc/implemented.adoc snippet files that back a progress report's include:: directives.
The snippet file(s) written for one ScenarioStatus.
The scenarios classified under one ScenarioStatus, along with the display text and summary figures used to render that status's heading, blurb, and summary table row.