Severity vs Priority
// Definition
Severity describes how broken the system is (set by QA, technical impact). Priority describes how urgently it should be fixed (set by Product, business impact). The two are independent — a typo can be Trivial / P0.
// Related terms
Bug Lifecycle
The stages a defect passes through from discovery to closure: New → Assigned → In Progress → Fixed → Verified → Closed (with possible Reopened, Deferred, or Rejected branches).
Test Strategy
The high-level, organisation-wide approach to testing — what gets tested, by whom, with what tools, at what stage. Broader and more permanent than a test plan.
UAT (User Acceptance Testing)
Verification by end users or business stakeholders that the system meets their real-world needs. The final validation gate before release.
Learn more · Software Testing Fundamentals
Chapter 5 · Lesson 4: Bug Severity vs Priority