aibdd-feature-file-writing-principle

What problem does it solve?

Prevents AIBDD feature files from degrading into “test-like steps without a rebuildable specification” by enforcing Specification by Example, data-complete Given sections, full result verification, and robust negative-path and idempotency coverage.

Core Features & Use Cases

• Specification by Example (SSOT): Ensures every feature example provides concrete inputs, actions, and observable outputs.
• Data-complete Given: Requires fixture manifests, templates, and seed/expected artifacts to be explicitly present rather than implicitly “known” from repo context.
• Full-result verification: Prioritizes exact comparisons of full projections (e.g., complete JSON) and full file contents over single-field or partial assertions.
• Negative-path rigor: Forces unknown directive/error scenarios to assert error classification plus exact preserved original text where applicable.
• Idempotency coverage: Requires separate examples that demonstrate reruns do not change outputs.
• Fixture-driven, harness CLI orientation: Encourages expressing specs using generalized, filesystem-oriented, CLI-driven harness workflows.

Quick Start

Ask an AI agent to rewrite your AIBDD .feature files following the aibdd-feature-file-writing-principle so each Scenario is data-complete, negative paths and idempotency are explicitly tested, and assertions verify complete outputs and preserved original text.