qa-automation

Author end-to-end / UI-automation tests derived from the acceptance criteria, not from the implementation. Cover risk-tier critical journeys plus their key negative paths — not every path.

When to use / not use

• Use once acceptance criteria exist (from /api-contract) and an env can be brought up.
• Don't test against the implementation's internals, and never weaken assertions to make a test pass.

Inputs

feature, acceptance_criteria, optional contract_summary (for cross-service journeys), and optional test_cases_path — the design-phase functional test-case catalog (.maestro/<slug>/test-cases.md, from /functional-testcases).