mcaf-testing

Design and run automated tests per AGENTS.md rules with TDD and derived scenarios.

20|Updated Feb 1, 2026

Search Tags:#automation #testing #tdd #documentation #integration-testing #quality-assurance

Ready to run

npx skills add https://github.com/Zendevve/opentweak --skill mcaf-testing-zendevve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcaf-testing
Source: https://github.com/Zendevve/opentweak/tree/main/.codex/skills/mcaf-testing
Command: npx skills add https://github.com/Zendevve/opentweak --skill mcaf-testing-zendevve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add or update automated tests for a change (bugfix, feature, refactor) using the repository's testing rules in AGENTS.md. Use TDD where applicable; derive scenarios from docs/Features/* and ADR invariants; prefer stable integration/API/UI tests, run build before tests, and verify meaningful assertions for happy/negative/edge cases.

Core Features & Use Cases

Create and maintain automated tests that reflect documented behaviour and acceptance criteria.
Derive test scenarios from project docs (docs/Features/) and architectural decisions (docs/ADR/), focusing on integration/API/UI layers when appropriate.
Validate changes by running the repository's build and test processes, capturing verifications and artifacts for traceability.

Quick Start

Run the repository’s test suite following AGENTS.md to validate the change.

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 for code changes using repository testing rules?▼

Automated testing validates code changes by deriving scenarios from docs/Features/* and ADR invariants, applying TDD, and running a pre-test build. It prioritizes stable integration, API, and UI tests to verify meaningful assertions for happy, negative, and edge cases.

What's the best way to derive test scenarios from feature documentation?▼

Derive test scenarios from docs/Features/* and ADR invariants to align tests with documented behavior and acceptance criteria, prioritizing stable integration, API, and UI layers for meaningful validation.

How does TDD integration work with existing project documentation?▼

TDD integration applies test-driven development by deriving scenarios from docs/Features/* and ADR invariants, running pre-test builds, and capturing verification artifacts to ensure alignment with governance guidelines.

Can I use automated testing for integration, API, and UI layers?▼

Yes, automated testing prioritizes stable integration, API, and UI tests, validating meaningful assertions for happy, negative, and edge cases while adhering to AGENTS.md testing rules.

Why does automated testing run a build before executing tests?▼

Automated testing runs a pre-test build to validate the repository's build process before executing tests, ensuring that captured verification outcomes reflect actual behavior rather than build errors.

Do I need AGENTS.md and docs/Features to validate code changes?▼

Yes, AGENTS.md defines testing rules and docs/Features/* provides acceptance criteria, both required to derive test scenarios, validate changes, and report alignment with governance guidelines.