bmad-testarch-automate

Orchestrate multi-step test generation and validate artifacts across API, UI, and backend layers.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-testarch-automate-mazenmrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-automate
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-testarch-automate
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-testarch-automate-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Expand test automation coverage by orchestrating a multi-step workflow to identify targets, generate tests via dedicated subagents, aggregate results into test files and fixtures, and validate outputs against a checklist to produce an automation summary.

Core Features & Use Cases

  • Orchestrates target discovery and coverage planning (Step 2) and generates a comprehensive test automation plan.
  • Dispatches parallel subagents for API, E2E, and Backend test generation (Step 3) while preserving a consistent output contract.
  • Aggregates subagent outputs and generates shared fixtures and helpers (Step 3c) to produce runnable tests.
  • Validates generated artifacts against a workflow checklist and saves a concise automation summary (Step 4).

Quick Start

Run the Create path to generate tests and artifacts for your codebase, then review results with Validate and adjust with Edit.

Frequently Asked Questions about bmad-testarch-automate

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

FAQPage Schema
How do I automate test architecture generation across API, UI, and backend layers?

Test architecture automation identifies codebase targets and orchestrates subagents to generate tests for API, UI, and backend layers. It coordinates multi-worker execution and aggregates outputs into shared fixtures and runnable test files.

What is the best way to orchestrate multi-worker test generation for a software project?

Multi-worker test generation dispatches parallel subagents for API, E2E, and backend tests while preserving a consistent output contract. It provisions shared fixtures and aggregates results into validated test artifacts.

How does fixture provisioning work during automated test planning?

Fixture provisioning aggregates subagent outputs to generate shared fixtures and helpers. This process produces runnable tests by consolidating generated artifacts across API, UI, and backend layers into a unified format.

Can I validate generated test artifacts against a workflow checklist automatically?

Automated validation checks generated test artifacts against a workflow checklist. It evaluates the aggregated test files and fixtures to save a concise automation summary of the orchestration results.

Does this test orchestration workflow require external dependencies to run?

This test orchestration workflow operates without external dependencies. It uses internal scripts to discover targets, dispatch parallel subagents for test generation, aggregate fixtures, and validate outputs autonomously.

When do I need end-to-end test planning and automated artifact aggregation?

End-to-end test planning is needed for software projects requiring reliable mode selection and multi-worker coordination. Automated artifact aggregation ensures consistent output formatting across API, UI, and backend test layers.