bmad-testarch-atdd

Automating acceptance test generation for the TDD red phase involves creating test scaffolds from user story criteria. This process maps requirements to appropriate test levels, generating initial API and E2E tests using frameworks like Playwright and Pact.js.

ATDD test strategy mapping is the process of aligning acceptance criteria with specific test levels and priorities. It works by evaluating user story requirements and automatically documenting the necessary API, E2E tests, and external service mocking needs.

Yes, this test generation approach works with both frontend and backend projects. It handles various test levels and prioritization, applying step-file architecture to generate scaffolds for API tests using Pact.js and E2E tests using Playwright.

Generating test data factories and fixtures for E2E test automation requires defining data generation and cleanup rules. This approach creates structured data infrastructure using tools like Faker to support consistent test execution across acceptance criteria.

Yes, you need Playwright and Pact.js to automate acceptance test scaffolds in this workflow. These dependencies provide the core testing infrastructure for E2E browser automation and API contract mocking, alongside Faker for generating test data.

The best way to mock external services for API acceptance tests is to document mocking requirements during scaffold generation. This ensures external service interactions are defined upfront, allowing Pact.js to handle contract testing and isolate API behavior validation.