# Definition.test Strategy

> Define the holistic testing approach across functional, non-functional, and automation layers for the initiative.

- Skill: `majiayu000/definition-test-strategy` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/definition-test-strategy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/definition-test-strategy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/definition-test-strategy

---


# 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
```bash
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
1. Summarize feature scope, risks, and constraints.
2. Define testing objectives tied to quality risks and success metrics.
3. Produce a coverage matrix mapping test types to owners, environments, and tooling.
4. Outline milestones with entry/exit criteria and reporting cadence.
5. 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.