Course → 2 · Senior QA judgment → Senior QA — Real Cases
2 · Senior QA judgment
Severity vs priority in production defects
15 min · Module 14
In real teams, severity describes user/business impact; priority describes when to fix.
Example: a cosmetic typo can be high priority before a launch, but low severity. A data-loss bug on a rare admin path can be critical severity but medium priority if a workaround exists.
In the Lab: file defects on work tickets with honest severity, then decide whether the release is still shippable.
Example / notes
# Senior practice is judgment + evidence, not only automation.
# After finding a HelpDesk bug in the Lab:
# 1) Capture release version from #aut-release
# 2) File defect with steps / expected / actual
# 3) Submit fail or blocked report on the work ticketPractice in Lab: /lab/work/