Section 2 Review

Section 2 built the strategic foundation for the rest of this path: what a genuine test strategy is, how to allocate effort using risk, how to adapt strategy to a product's actual release model, and how to extend that thinking across an entire organization.

Knowledge Check

Work through these four scenarios before checking the Section 2 Solutions.

Scenario 1: The Two-Week Crunch

A QA Lead has two weeks before a release and needs to decide where to focus limited testing time across five feature areas with varying complexity and business impact. What should determine the allocation, and what's the specific method?

Scenario 2: The Faster Cadence

A team moving from monthly releases to twice-weekly releases asks whether their existing full-regression testing checklist still makes sense. What's the right response, per this section's reasoning?

Scenario 3: Three Definitions of "Critical"

A newly appointed Head of QA discovers that three product teams have three different definitions of what counts as a "critical" defect. What's missing, and what shouldn't be changed as a result?

Scenario 4: The 40-Page "Strategy"

A stakeholder asks a QA Lead for "the test strategy" and receives a 40-page document listing every planned test case for the next release. What did they actually receive, and what's missing?

Next: Check your answers against the Section 2 Solutions, then continue to Section 3 — Leadership.