bmad-testarch-atdd

Generates red-phase acceptance test scaffolds for TDD workflows using Playwright.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-testarch-atdd-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-testarch-atdd
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-testarch-atdd-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Writing acceptance tests before implementation is often skipped because it requires manually mapping acceptance criteria to test levels, building fixtures, and structuring failing tests. This Skill automates the ATDD red phase by generating skipped test scaffolds, data factories, fixtures, and an implementation checklist from a user story. ## Core Features & Use Cases - Red-Phase Test Generation: Creates E2E, API, and component test scaffolds marked with test.skip() that fail until the feature is implemented. - Test Infrastructure: Generates faker-based data factories, Playwright fixtures with auto-cleanup, mock requirements, and data-testid attribute lists. - Implementation Checklist: Produces an ATDD checklist mapping each test to concrete development tasks following the red-green-refactor cycle. - Use Case: Given a story like "user registration with email validation", the Skill produces failing Playwright API and E2E specs, a user factory, and a task list the developer activates one test at a time. ## Quick Start Ask the agent to write acceptance tests for your story file using ATDD, providing the path to the story markdown with its acceptance criteria.

Frequently Asked Questions about bmad-testarch-atdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write acceptance tests before implementation with ATDD?▼

Provide a story file with clear acceptance criteria and run the ATDD workflow. It maps each criterion to E2E, API, or component test levels and generates Playwright test scaffolds marked with test.skip() that fail until the feature is implemented.

What test levels does ATDD test generation support?▼

The workflow supports E2E tests for critical user journeys, API tests for business logic and contracts, component tests for UI behavior, and unit tests for pure logic. Level selection adapts to whether the detected stack is frontend, backend, or fullstack.

Does this workflow support Playwright and Cypress?▼

The preflight step checks for playwright.config.ts or cypress.config.ts as the test framework configuration. Generated examples and fixture patterns primarily target Playwright, including test.extend() fixtures and getByRole selectors.

Why are generated tests marked with test.skip()?▼

Tests are red-phase scaffolds in the TDD cycle: they assert expected behavior but would fail because the feature is not implemented. Developers activate one test at a time by removing test.skip(), confirm it fails, then implement until it passes.

Can the workflow generate Pact contract tests?▼

Yes, when the tea_use_pactjs_utils config flag is enabled, the API subagent generates consumer contract tests alongside API tests using pactjs-utils patterns, with provider scrutiny evidence documented per endpoint.