High severity · High priority
Checkout charges the customer but order creation fails. Core revenue flow and reconciliation are at risk.
QA guide · Triage
Severity asks how badly the defect affects the product or user. Priority asks how urgently the team should address it. They influence each other, but they are not the same decision.
Severity inputs: scope of impact, data loss, blocked workflow, security/privacy exposure, accessibility barrier and availability of a workaround.
Priority inputs: release timing, number of affected users, business criticality, legal/compliance deadline, support load, workaround cost and fix risk.
Checkout charges the customer but order creation fails. Core revenue flow and reconciliation are at risk.
A destructive admin-only workflow fails in a feature disabled for all production tenants. Impact is severe if enabled, urgency may be lower today.
A typo appears in the company name on a homepage launching in a national campaign tomorrow. Functionality is intact; business urgency is high.
A minor alignment issue appears in a rarely used secondary panel with no usability impact.
Pick three findings in the QA Lab. Give each a severity and a separate priority, then write one sentence defending each decision.
Ferramenta gratuita
O QA Evidence Generator roda localmente no navegador, dá um score determinístico de completude, aponta lacunas e exporta Markdown ou HTML pronto para PDF.
Practice it
The QA + Security Bug Hunt Lab gives you a self-contained storefront with intentional findings, reporting templates, scoring and an answer key.
Open the QA Lab on Gumroad ↗