Keep the scenario connected to its result.
The Gherkin engine runs the installed Cucumber CLI against the approved files and configuration. It preserves native reports, tool identity and artifact hashes. Scenario outlines retain their example-row identities, while backgrounds and hooks stay associated with the relevant scenario. That detail helps a developer locate the specific example behind a reported failure.
See where execution stopped short.
An undefined, ambiguous, pending or skipped step remains incomplete. A setup failure stays visible alongside the later assertions it prevented from running. A run with zero executed scenarios cannot pass. The approved tag selection is retained, so the result describes the reviewed scope and does not quietly expand a filtered subset into a claim about the entire feature.
- Inspect feature tags and individual scenario outcomes.
- Retain native evidence when setup or cleanup fails.
- Review changing outcomes across supported repeated invocations.
Evaluate a feature with clear acceptance examples.
Bring an important feature and its existing scenarios to an evaluation. We review the step definitions, required dependencies, target environment and approved expectations. Cucumber support depends on installed tooling and a qualified runner. Plain-language scenarios still need executable steps and meaningful assertions; a feature file by itself cannot establish that the application behaves correctly.