Skip to content

fix: enforce BDD/E2E in dev-story — Gherkin gate + E2E required for UI flows#2276

Open
pablontiv wants to merge 1 commit intobmad-code-org:mainfrom
pablontiv:fix/enforce-bdd-tdd-e2e-dev-story
Open

fix: enforce BDD/E2E in dev-story — Gherkin gate + E2E required for UI flows#2276
pablontiv wants to merge 1 commit intobmad-code-org:mainfrom
pablontiv:fix/enforce-bdd-tdd-e2e-dev-story

Conversation

@pablontiv
Copy link
Copy Markdown

What

Four targeted changes to src/bmm-skills/4-implementation/bmad-dev-story/workflow.md that enforce BDD/E2E discipline when the TEA module is present.

Why

Without these changes, stories with user-facing flows complete without E2E tests and without Gherkin-described acceptance criteria, even when the TEA module is installed and configured. See #2275.

Note: this extends the intent of #2272 (ATDD gate) with Gherkin content verification and E2E opt-out (rather than opt-in).

How

  • Step 1: adds BDD/SDD/E2E pre-check gate — warns when TEA is installed but no ATDD checklist exists; warns when checklist has no Gherkin scenarios (Given/When/Then)
  • Step 5: red phase now identifies test type (unit vs E2E) before writing the failing test, making the E2E red phase explicit for UI tasks
  • Step 6: E2E tests required for all user-facing flows (removes the when story requirements demand them opt-in conditional)
  • Step 9 DoD: same language fix — E2E mandatory for UI flows, unit mandatory for logic/API

Testing

Verified locally against a project with TEA module installed: bmad-dev-story now warns at Step 1 when no ATDD checklist is found, and warns when the checklist contains no Gherkin scenarios.

…I flows

- Step 1: add BDD/SDD/E2E pre-check gate; warns when TEA is installed but
  no ATDD checklist exists, and warns when checklist has no Gherkin scenarios
- Step 5: red phase now identifies test type (unit vs E2E) before writing
  the failing test, so UI tasks explicitly require E2E red phase
- Step 6: E2E tests required for all user-facing flows (removes the
  'when story requirements demand them' opt-in conditional)
- Step 9 DoD: same language fix — E2E mandatory for UI flows
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant