qa-test-management

QA Test Management Skill

Ensure consistent QA test organization, lifecycle management, and traceability.

Automatic Behaviors

When working with QA tests, automatically:

1. Apply naming conventions for QA test files
2. Maintain directory structure for test organization
3. Enforce status lifecycle transitions
4. Include required metadata in all test files
5. Link tests to PRD requirements for traceability
6. Track execution history with dates and results

Directory Structure

qa-tests/
├── draft/                    # Tests being written
│   └── QA-20250105-001-login.md
├── active/                   # Tests ready for execution
│   └── QA-20250104-002-checkout.md
├── executed/                 # Recently executed tests
│   └── QA-20250103-001-search.md
├── archived/                 # Historical tests
│   └── 2024/
│       └── QA-20241215-001-old-feature.md
└── screenshots/              # Test evidence
    ├── login-page.png
    └── checkout-success.png

File Naming Convention

QA-YYYYMMDD-###-feature-name.md

• QA - Prefix for all QA test files
• YYYYMMDD - Creation date
• ### - Sequential number for that day (001, 002, etc.)
• feature-name - Kebab-case feature description

Examples:

• QA-20250105-001-user-login.md
• QA-20250105-002-password-reset.md
• QA-20250106-001-checkout-flow.md

Status Lifecycle

DRAFT → ACTIVE → EXECUTED → ARCHIVED

Status	Description	Location
DRAFT	Being written, not ready for execution	qa-tests/draft/
ACTIVE	Ready to be executed by testers	qa-tests/active/
EXECUTED	Has been run, awaiting review/archival	qa-tests/executed/
ARCHIVED	Historical reference, no longer active	qa-tests/archived/YYYY/

Status Transitions

• DRAFT → ACTIVE: All test cases complete, metadata filled, reviewed
• ACTIVE → EXECUTED: Test has been run, execution log updated
• EXECUTED → ARCHIVED: Test cycle complete, moved to archive
• Any → DRAFT: Test needs rework (regression found, requirements changed)