• A feature set or release needs a top-level testing approach.
• Team must balance quality risk against schedule pressure.
• Stakeholders need rationale for scope, depth, and resource allocation.

• Deliver a practical test strategy.
• Define what to test first, what to defer, and why.
• Align QA, Dev, and product on risk-based quality goals.

1. Define business objective and acceptable failure tolerance.
2. Build risk map by module criticality and change frequency.
3. Select test levels and methods for each risk bucket.
4. Allocate resources, environments, and automation budget.
5. Set quality gates, metrics, and escalation criteria.
6. Review and adapt strategy based on execution feedback.

Input:

• 4 modules, limited QA headcount, high payment risk

Output:

• Risk-first strategy prioritizing payment + order + rollback
• Clear gate metrics (blocker count, critical flow pass rate)
• Deferred low-risk scope with explicit tradeoff note

Input:

• "Write a test strategy quickly"

Output (problem):

• Broad principles only, no scope prioritization or gate definition
• Cannot guide real execution decisions

• Do not provide one-size-fits-all strategy.
• Do not separate strategy from resource constraints.
• Do not define gates without measurable metrics.
• Do not hide deferred scope decisions.
• Do not freeze strategy when risk profile changes.