bmad-testarch-framework

Scaffolds Playwright, Cypress, or backend test frameworks with fixtures, factories, and configuration.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/Hexalith/Hexalith.Parties --skill bmad-testarch-framework-hexalith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-framework
Source: https://github.com/Hexalith/Hexalith.Parties/tree/main/.agents/skills/bmad-testarch-framework
Command: npx skills add https://github.com/Hexalith/Hexalith.Parties --skill bmad-testarch-framework-hexalith

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test, @seontechnologies/playwright-utils, @faker-js/faker, @pact-foundation/pact, @seontechnologies/pactjs-utils, and includes references (resource) components.

What problem does it solve? Setting up a production-grade test framework from scratch involves dozens of decisions—framework selection, directory layout, fixture architecture, data factories, CI-ready configuration, and documentation—that are easy to get wrong and tedious to repeat across projects. ## Core Features & Use Cases - Stack-aware framework selection: Auto-detects frontend, backend, fullstack, or mobile projects and recommends Playwright, Cypress, pytest, JUnit, Go test, xUnit, RSpec, or Maestro with documented rationale. - Complete scaffold generation: Creates test directory structures, framework configs with tuned timeouts and reporters, environment files, fixture indexes with mergeTests, faker-based data factories with auto-cleanup, and sample tests following Given-When-Then and data-testid patterns. - Tri-modal workflow with resume: Supports Create, Resume, Validate, and Edit modes with progress tracking frontmatter, a validation checklist, and an optional write-time enforcement hook for Claude Code. - Use Case: A team starting a React storefront asks the agent to set up testing; the skill detects the Vite/React stack, scaffolds Playwright with auth fixtures and an order factory, adds npm scripts, and produces a tests/README.md ready for CI. ## Quick Start Tell the agent "let's set up the test framework" in your project root and it will detect your stack, pick a framework, and scaffold the full test suite.

Frequently Asked Questions about bmad-testarch-framework

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

FAQPage Schema
How do I set up a Playwright test framework for a new project?

Invoke the framework setup workflow and it auto-detects your stack from package.json, then scaffolds playwright.config.ts with tuned timeouts, reporters, and artifact policies. It also creates fixtures, data factories, sample tests, and a tests/README.md.

Playwright vs Cypress: which should I choose for E2E testing?

The workflow defaults to Playwright for large repos, multi-browser needs, heavy API plus UI integration, and CI parallelism. Cypress is recommended for small teams prioritizing developer experience, component testing, or simpler setup.

Does this test setup support backend languages like Python or Go?

Yes, backend stacks get idiomatic scaffolding: pytest with pyproject.toml config for Python, JUnit 5 for Java, Go test conventions for Go, xUnit for .NET, and RSpec for Ruby. Mobile projects get Maestro flows plus the app's unit test framework.

Can I resume an interrupted test framework setup?

Yes, the workflow saves progress with frontmatter tracking completed steps in a progress file. Selecting Resume mode loads that file, verifies previously created artifacts still exist on disk, and routes to the next incomplete step.

Why did the framework setup skip Pact contract testing?

Contract test scaffolding is gated on relevance: it only activates when a real consumer-provider boundary exists in or is started by the repo. If no such boundary is detected, no Pact artifacts are created to avoid a dead suite failing CI.