planning-testing-strategy

Define a sufficient verification set tied to AC and risks AC/Goal + change list Critical scenarios, edge cases, risks Available environments and test data Map each key AC/risk to a check (unit/integration/e2e/manual) Define a regression minimum for adjacent impacted areas Define test data and environments Define acceptance signals (what counts as a successful verification)

Test scope

Test types

Key scenarios + edge-cases

Data / environments

Acceptance signals

</output_format> Checks are tied to changes/risks, not "just in case" Regression coverage exists around the impact area, not only the happy path </quality_rules>