qa-fixtures-aaa

Designs unit and integration tests using Arrange-Act-Assert structure with explicit fixtures.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill qa-fixtures-aaa-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-fixtures-aaa
Source: https://github.com/vovanostm-public/multica/tree/main/workflow-bundles/multica-specops-v5/codex_skills/.agents/skills/qa-fixtures-aaa
Command: npx skills add https://github.com/vovanostm-public/multica --skill qa-fixtures-aaa-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing maintainable tests is hard: tests often mix multiple behaviors, hide setup state in opaque fixtures, and assert on implementation details instead of observable behavior. This Skill enforces a disciplined Arrange-Act-Assert approach so tests read as specifications and regressions are caught reliably. ## Core Features & Use Cases - AAA Test Structuring: Converts existing or new tests into clean Arrange-Act-Assert form with a single act per test. - Fixture Design: Creates minimal, named, reusable fixtures that keep important state explicit rather than hidden. - Regression Strategy & Cleanup: Splits multi-act tests, deduplicates setup into helpers, and produces typed evidence outputs (qa.fixtures, qa.aaa_tests, verification.plan, verification.results). - Use Case: Given an implementation diff and acceptance criteria, generate a focused test suite with explicit fixtures, a verification plan, and a handoff to browser-based E2E testing when behavior requires it. ## Quick Start Ask the agent to design AAA-structured unit tests with explicit fixtures for the current implementation diff and acceptance criteria.

Frequently Asked Questions about qa-fixtures-aaa

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

FAQPage Schema
How do I structure unit tests using Arrange-Act-Assert?▼

Arrange only the necessary state, perform a single act on the behavior under test, then assert observable behavior rather than implementation internals. Tests structured this way read as specifications and are easier to maintain.

How to design reusable test fixtures without hiding state?▼

Create minimal, explicitly named fixtures and inline or clearly name any state that is important to understanding the test. Deduplicate repeated setup into helpers only when doing so does not hide intent.

When should a test be split into multiple tests?▼

Split a test whenever it contains more than one act. Each test should exercise a single behavior so failures point directly to the broken behavior rather than a mixture of causes.

When should unit tests hand off to end-to-end browser testing?▼

When the behavior under test requires a real browser environment, the unit/integration test stage hands off to a Playwright-based E2E stage rather than simulating browser behavior in unit tests.

What happens when acceptance criteria are missing for a test task?▼

The workflow blocks with a missing product evidence signal instead of guessing behavior. Tests are designed against acceptance criteria, implementation diffs, and existing tests, so absent criteria halt progress until evidence is provided.