How do you create a test strategy for a new product or feature?

A good test strategy is risk-based. Start by mapping user flows and failure impact, then define: - Test scope (what’s in/out) - Test levels (unit, integration, E2E) - Environments and test data - Release gates and acceptance criteria Prioritize high-risk areas (payments, auth, data loss) and automate stable, repeatable checks first.