definitiontest-strategy
Define the holistic testing approach across functional, non-functional, and automation layers for the initiative.
When & Why to Use This Skill
This Claude skill streamlines the software quality assurance process by generating a holistic test strategy. It covers functional, non-functional, and automation layers, enabling QA leads to define risk-based priorities, coverage matrices, and clear project milestones for efficient software delivery and improved product reliability.
Use Cases
- Strategic QA Planning: Developing a comprehensive test strategy for new product initiatives, ensuring alignment between engineering, product, and QA teams before development begins.
- Risk-Based Testing: Prioritizing testing efforts by mapping quality risks to specific objectives and success metrics to optimize resource allocation and focus on critical features.
- Multi-Platform Coverage Mapping: Creating detailed matrices to track testing progress across various environments, devices, and automation frameworks to ensure consistent performance.
- Non-Functional Requirement Integration: Defining structured approaches for critical non-functional areas like performance and accessibility to ensure the software meets all quality standards.
| name | definition.test_strategy |
|---|---|
| phase | definition |
| description | Time, tooling, or staffing constraints to consider. |
| - name | constraints |
Purpose
Equip QA teams with a thorough test strategy document ready to align with engineering and product before delivery begins.
Pre-run Checklist
- ✅ Review discovery risk assessment outcomes.
- ✅ Gather architectural diagrams and integration dependencies.
- ✅ Confirm available automation frameworks and environment readiness.
Invocation Guidance
codex run --skill definition.test_strategy \
--vars "feature={{feature}}" \
"scope={{scope}}" \
"non_functional={{non_functional}}" \
"constraints={{constraints}}"
Recommended Input Attachments
- Historical defect data or production incident summaries.
- Existing test plans or automation coverage reports.
Claude Workflow Outline
- Summarize feature scope, risks, and constraints.
- Define testing objectives tied to quality risks and success metrics.
- Produce a coverage matrix mapping test types to owners, environments, and tooling.
- Outline milestones with entry/exit criteria and reporting cadence.
- Highlight dependencies, data needs, and automation investments.
Output Template
## Test Strategy Overview
Feature: {{feature}}
Scope: {{scope}}
## Testing Objectives
- Objective — Risk addressed — Metric
## Coverage Matrix
| Test Type | Owner | Environment | Tooling | Automation | Notes |
| --- | --- | --- | --- | --- | --- |
## Milestones & Criteria
| Milestone | Entry Criteria | Exit Criteria | Target Date | Owner |
| --- | --- | --- | --- | --- |
## Dependencies & Data Needs
- Dependency:
- Mitigation:
Follow-up Actions
- Review strategy with engineering and product leadership for sign-off.
- Translate coverage needs into executable test cases in the test management tool.
- Track progress and update strategy as scope evolves.