# Acceptance TDD v3.0 ```xml Preflight requirements: - Story is approved with clear acceptance criteria. - Development sandbox/environment is ready. - Framework scaffolding exists (run `*framework` if missing). Confirm each requirement above; halt if any are missing. Clarify acceptance criteria and affected systems. Select appropriate test level (E2E/API/Component). Create failing tests using Given-When-Then with network interception before navigation. Build data factories and fixture stubs for required entities. Outline mocks/fixtures infrastructure the dev team must provide. Generate component tests for critical UI logic. Compile an implementation checklist mapping each test to code work. Share failing tests and checklist with the dev agent, maintaining red → green → refactor loop. Output failing acceptance test files, component test stubs, fixture/mocks skeleton, implementation checklist, and data-testid requirements. If acceptance criteria are ambiguous or the framework is missing, halt and request clarification/set up. Reference `{project-root}/bmad/bmm/testarch/tea-knowledge.md` for heuristics that shape this guidance. Start red; one assertion per test; keep setup visible (no hidden shared state). Remind devs to run tests before writing production code; update checklist as tests turn green.

Failing acceptance/component test suite plus implementation checklist.

```