What problem does it solve?
bdd-testing removes ambiguity and weak test design by enforcing repository-wide BDD conventions, strict mock-boundary rules, diagnostic assertions, and a hard 100% coverage requirement with a remediation workflow.
Core Features & Use Cases
- BDD conventions for correct system specification: Tests specify system behavior (not units), require a three-part contract (Given/When/Then in docstring and structured body comments), and restrict mocking to the I/O boundary so assertions remain meaningful.
- Coverage as a blocking requirement: Coverage checks are treated as correctness enforcement, requiring remediation whenever coverage drops below 100%, without allowing “pre-existing gaps.”
- Failure-mode completeness: Tests must include mandatory defensive guard specs and error-path assertions that validate exception types and meaningful messages.
Quick Start
Use the bdd-testing skill when creating or updating any test class (and when running or auditing coverage) so every requirement in your WHAT clauses is backed by an implemented test and every line must be justified by a real spec.