test-strategy-author

Overview

A test strategy document answers the question "how do we know we're testing the right things?" Without it, test investment is gut-feel; with it, the team has a defensible artifact tying test work to risk and business goals.

This skill produces the document.

When to use

• A new product / large feature is in planning; the team needs to scope test investment.
• A multi-quarter initiative needs a published strategy stakeholders can review.
• An audit / compliance review requires a documented strategy.
• A new team forming around a product needs onboarding context.