qa-test-management

What problem does it solves?

Managing QA test cases with consistent naming, structured organization, clear status transitions, and traceability to requirements is crucial for effective quality assurance. Without proper management, tests can become disorganized and difficult to track. This Skill ensures consistent QA test organization.

Core Features & Use Cases

• Naming Conventions: Automatic application of standard naming for QA test files (QA-YYYYMMDD-###-feature-name.md).
• Directory Structure: Maintenance of an organized qa-tests/ structure with draft/, active/, executed/, and archived/ subdirectories.
• Status Lifecycle: Enforcement of a clear test status workflow (DRAFT → ACTIVE → EXECUTED → ARCHIVED) with validation of transitions.
• Required Metadata: Ensures all test files include essential information like Test ID, Feature, Application, URL, Status, and Priority.
• PRD Traceability: Establishes clear links between QA tests and Product Requirements Document (PRD) sections.
• Use Case: Creating a new QA test plan for a feature, moving a test from DRAFT to ACTIVE, logging test execution results, linking tests to PRD requirements, or archiving outdated tests.

Quick Start

Use the qa-test-management skill to generate a template for a new QA test file, including all required metadata and sections.