test-strategy

name	test-strategy
description	Designs a focused test plan for a feature, bug fix, refactor, or release by choosing the right unit, integration, end-to-end, and regression tests.

Test Strategy

Use this skill when a user asks what to test, how much to test, or how to validate a change before release.

Inputs

• Feature, bug fix, refactor, pull request, or release scope
• Existing test framework and commands
• Known risks, production incidents, or edge cases

Steps

1. Identify behaviors that must remain true, not just lines of code that changed.
2. Map risks to test levels: unit for pure logic, integration for contracts and data flow, end-to-end for critical user journeys, regression tests for bugs.
3. Prioritize tests by impact, likelihood, and cost to maintain.
4. Include negative cases, boundary cases, permissions, failure modes, and compatibility cases.
5. Recommend test data and mocks only where they preserve realism.
6. Define the smallest useful test suite for this change and the broader suite for release confidence.
7. Provide commands to run if they can be inferred from the repo.

Output

Return:

• Risk-based test matrix
• Recommended new or updated tests
• Existing tests to run
• Gaps that require manual QA or instrumentation
• Confidence assessment

Guidelines

• Avoid blanket "add more tests" advice.
• Prefer tests that fail for the right reason.
• Keep tests aligned with user-visible behavior and stable contracts.