Validate specs
validate specs - Validate Gherkin specifications against quality contracts
The validate specs command checks existing .feature files against the specification contract, ensuring they follow proper Gherkin syntax, and project standards. Validation covers structure (Feature/Rule/Scenario hierarchy), tags, step formatting, and content quality. The command can validate a single file or recursively validate all .feature files in a directory. By default, output is in human-readable text format. Use --format json for machine-readable output.
Flags
| Flag | Description |
|---|---|
-q, --quiet (default: false) |
Suppress success messages and show only validation errors and warnings |
-v, --verbose (default: false) |
Show detailed validation output including metadata and additional context |
-f, --format (default: text) |
Output format for validation results (text for human-readable, json for machine-readable) |
Notes
Expected Output:
Displays validation results for Gherkin specification structure, tags, and step formatting. Shows errors and warnings with line numbers. Exit code 0 if all pass, 1 if critical errors found.
See Also
Tutorials | How-to Guides | Explanation | Reference
You are here: Reference — information-oriented technical descriptions of the system.