HoangNguyen0403 Quality Engineering: Test Plan Authoring
Priority: P1 (HIGH)
Input
AC-* IDs and SRS lanes (unit/integration/E2E-web/E2E-mobile/API) from the
approved PRD/SRS. Never derive scenarios from reading the code — code shows
what exists, not what the acceptance criteria require.
Output
docs/srs/test-plan-[slug].md (and specs/[slug].md once Playwright Test
Agents are initialised on the target repo). Each scenario block: Steps,
Expected, @AC-n tag, priority, exactly one lane (web|ios|android|api).
One scenario covers one AC condition — do not fold multiple conditions into
one scenario.
Seed
tests/seed.spec.ts (or platform equivalent) carries only shared
prerequisites: auth and navigation to the starting screen. No assertions.
Mandatory Sections
Selector Gaps (elements the plan needs that have no stable id yet — feeds
specialist-testid-inserter, Phase P1, not yet implemented) and Data & Reset
(fixtures needed, how state resets between scenarios). Gaps must follow the
<screen>-<element>-<role> naming convention defined in
quality-engineering-selector-stability.
Relationship to Zephyr
Manual Zephyr TCs stay the system of record for business sign-off
(quality-engineering-zephyr-test-generation); this skill's scenarios carry
a bidirectional TC-key reference where one exists, and are additive, not a
replacement.
Anti-Patterns
- A scenario without an
Expectedoutcome. - A plan derived from source code instead of
AC-*. - Duplicating unit-level coverage in an E2E scenario.
- A scenario spanning more than one
lane. - A plan with no seed reference.
References
- Test Plan Template
- Playwright Agents Artifacts
- AC to Scenario Mapping
- Mobile Lane Matrix