mcaf-testing

Automate creation and maintenance of repository-conforming automated tests.

52|6|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/managedcode/MCAF --skill mcaf-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcaf-testing
Source: https://github.com/managedcode/MCAF/tree/main/skills/mcaf-testing
Command: npx skills add https://github.com/managedcode/MCAF --skill mcaf-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the creation and updating of automated tests to ensure changes conform to the repository's testing rules and conventions outlined in AGENTS.md.

Core Features & Use Cases

  • TDD-driven testing: write tests to specify behavior before or alongside implementation.
  • Docs-driven scenarios: derive test scenarios from docs/Features/* and ADR invariants to cover happy, negative, and edge cases.
  • Verification and reporting: ensure a build is run prior to tests, execute test suites, and capture evidence of verification (reports, coverage, and artifacts).

Quick Start

Create or update tests for the latest change following AGENTS.md guidelines and verify them by running the repository build and test suites.

Frequently Asked Questions about mcaf-testing

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

FAQPage Schema
How do I automate tests that follow repository rules in AGENTS.md?

Automated tests are generated and maintained according to AGENTS.md guidelines by deriving scenarios from docs/Features/* and ADR invariants, then verifying them through build, test, format, and analyze commands.

How do I generate test scenarios from feature documentation and ADRs?

Test scenarios are derived from docs/Features/* and ADR invariants to cover happy, negative, and edge cases, ensuring that bug fixes, features, and refactors align with documented behavior.

Can I use TDD to write tests before implementation using automated tooling?

TDD-driven testing is supported by automating the creation of tests that specify behavior before or alongside implementation, conforming to repository conventions.

What's the best way to ensure a build is run before executing integration tests?

A build is executed prior to running test suites to verify stability, capturing evidence through reports, coverage metrics, and artifacts for integration, API, and UI tests.

Does automated test generation work for refactors and bug fixes?

Automated test creation and updating applies to bug fixes, features, and refactors, ensuring all changes conform to the repository's testing rules and conventions.

How do I verify test coverage and report outcomes for new features?

Coverage and outcomes are verified by running repository build and test suites, capturing evidence of verification through reports and artifacts as specified by AGENTS.md guidance.