bmad-testarch-automate

Analyze source structure and existing tests to plan and generate prioritized test coverage.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-testarch-automate-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-automate
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-testarch-automate
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-testarch-automate-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams systematically expand test automation coverage for an existing codebase, reducing gaps, duplication, and manual effort when adding reliable tests.

Core Features & Use Cases

  • Coverage analysis: Identifies what should be tested based on source code, existing tests, and available workflow artifacts.
  • Test planning and prioritization: Selects the right test levels and assigns priorities to focus effort on critical paths first.
  • Test generation workflow: Coordinates generation of API, E2E, backend, unit, integration, and contract tests with supporting fixtures and helpers.
  • Validation and iteration: Verifies outputs against a checklist, supports resume/edit flows, and includes guardrails for deterministic, maintainable tests.
  • Use case: A team with a partially tested feature set can use this Skill to analyze the repository, produce a coverage plan, generate missing tests, and validate the results in one structured workflow.

Quick Start

Ask the Skill to analyze your repository and generate prioritized test coverage for the codebase.

Frequently Asked Questions about bmad-testarch-automate

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

FAQPage Schema
How do I expand test automation coverage for an existing codebase?

To expand test automation coverage, analyze source structure, existing tests, and workflow artifacts to identify gaps, then generate prioritized API, E2E, backend, unit, integration, and contract tests with supporting fixtures.

What is the best way to plan and prioritize tests for critical paths?

Test planning and prioritization involves selecting appropriate test levels and assigning priorities based on coverage analysis of source code and workflow artifacts, ensuring effort focuses on critical paths first to reduce gaps and manual effort.

How do I avoid duplicate test coverage and flaky test outputs?

Avoid duplicate coverage and flaky outputs by applying deterministic test design, priority tagging, fixture planning, and checklist-based validation during test generation and revision to ensure maintainable, reliable test artifacts.

Can I generate API, E2E, and contract tests in one workflow?

Yes, you can coordinate generation of API, E2E, backend, unit, integration, and contract tests within a single structured workflow that includes supporting fixtures, helpers, and validation against a checklist.

Does this test generation workflow support resume and edit flows?

The test generation workflow supports resume and edit flows by validating outputs against a checklist, allowing iteration and revision of generated tests while maintaining deterministic guardrails for maintainable results.