Course → 2 · Senior QA judgment → Senior QA — Real Cases
2 · Senior QA judgment
Risk-based testing before a release
18 min · Module 14
You rarely get unlimited time. Senior QA chooses what not to test as carefully as what to test.
Risk ≈ likelihood × impact. Focus on changed areas, money/auth paths, and historically buggy modules. In the Lab: deploy 1.1.0-rc, then prioritize work tickets for search, priority labels, and slow create.
Example / notes
# Example risk-ordered Lab plan after deploying 1.1.0-rc:
# 1) QA-103 search (P0 regression)
# 2) QA-104 priority label
# 3) QA-102 create ticket (slow path / waits)
# Defer low-risk settings polish if time-boxed.Practice in Lab: /lab/releases/