All Classes and Interfaces

Class	Description
FeatureIndexer	Numbers Feature/Scenario titles directly in the source .feature files according to a configured IndexingMode.
FeatureNameFormatter	Converts a Feature title into a directory-safe camelCase name.
FeatureParser	Parses a single Gherkin .feature file and extracts all scenarios.
FeatureSnippet	A single snippet file written for one Feature, within one status.
GenerateFeatureDocsTask	Gradle task that scans .feature files and writes all scenario titles to a single AsciiDoc file.
GherkinToAsciidocExtension	DSL extension for the Gherkin-to-AsciiDoc Gradle plugin.
GherkinToAsciidocPlugin	Gradle plugin that registers the generateFeatureDocs task and wires the gherkinToAsciidoc DSL extension into the project.
GlueCodeScanner	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.
IndexingMode	Controls whether Feature/Scenario titles are numbered directly in the source .feature files, as configured via the indexing DSL property.
ProgressHistoryStore	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.
ProgressHistoryUpdater	Produces the next ScenarioProgressRecord map to persist, from the previously persisted map and the current run's scenarios.
ProgressReportOptions	Configuration for ProgressReportWriter.
ProgressReportWriter	Writes an AsciiDoc progress report that breaks scenarios down by ScenarioStatus and summarises the breakdown as a table of counts and percentages.
ReportTemplateRenderer	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.
ReportText	Shared explanatory text used by both ProgressReportWriter and ReportTemplateRenderer.
ScanProgressReporter	Emits periodic, low-overhead LIFECYCLE-level status lines for a long-running scan loop (feature file reindexing, feature file parsing, glue code scanning, ...), so a consumer watching the build knows the task is still alive and roughly how far along it is.
ScenarioClassifier	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.
ScenarioFingerprint	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.
ScenarioGrouping	Groups ScenarioInfo instances by the Feature they belong to.
ScenarioInfo	Immutable description of a single scenario parsed from a .feature file.
ScenarioProgressRecord	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.
ScenarioStatus	Implementation progress of a single scenario, as tracked when trackProgress is enabled.
SnippetWriter	Writes the listed.adoc/defined.adoc/implemented.adoc snippet files that back a progress report's include:: directives.
StatusSnippets	The snippet file(s) written for one ScenarioStatus.
StatusSummary	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.