Skip to main content

Priority and Severity : Expanded

 

Levels of Priority with Examples


  1. Critical Priority
    These are non-negotiable tests—if these fail, the whole system or application may be unusable or face severe consequences.
    Example: In a hospital management system, a test case that verifies the emergency patient's data is correctly saved and retrievable is critical. Failure could directly impact patient safety.
  2. High Priority
    These test essential features required for primary business operations.
    Example: In an e-commerce site, processing a payment or placing an order is high priority—customers can't use the system effectively without it.
  3. Medium Priority
    These relate to important but non-essential functionality.
    Example: In the same e-commerce platform, applying a coupon code is useful, but users can still complete purchases without it.
  4. Low Priority
    These test optional or cosmetic features.
    Example: Animations or theme customizations on the homepage—nice to have, but won’t interrupt the main workflow if broken.

This structure helps QA teams focus on the most impactful areas first—especially during tight release schedules or rapid development cycles.

While priority determines when a test should be executed, severity reflects how bad a defect or failure is from a functional or business perspective. Think of severity as the impact on the system, regardless of whether the issue needs to be fixed urgently or not.

Levels of Severity with Examples


  1. Critical Severity
    A defect that causes a system crash or complete failure, with no workaround.
    Example: In an airline booking system, if the server crashes while processing bookings, stopping all operations—that’s critical.
  2. High Severity
    Major functionality is broken, but the system still runs. No workaround exists.
    Example: On a banking app, users can’t log in, but the app loads and displays the login page—it just never accepts credentials.
  3. Medium Severity
    A defect causes some functionality to behave incorrectly, but a workaround exists.
    Example: In a shopping website, the "Add to Wishlist" button doesn’t work, but users can still add items to their cart and purchase them.
  4. Low Severity
    Minor defects that don't affect the main functionality—usually cosmetic or UI glitches.
    Example: A typo in a success message like "Your payment was successful."

👥 Summary

  • Severity = Impact (How much it breaks)
  • Priority = Urgency (How soon we fix it)

A low severity bug (like that typo) might still have high priority if it's customer-facing and affects brand image. Likewise, a critical severity bug in a rarely used feature could be low priority if it doesn’t impact current release goals.

Follow on LinkedIn
Labels:

Comments

Post a Comment

Popular posts from this blog

Understanding Mistakes in Software Development: Errors, Defects, and Bugs

  Every software team uses the words “error,” “defect,” and “bug,” often interchangeably. But there’s real power in knowing exactly what each term means—and when it applies   1. Mistakes by Phase Phase What You Find What It’s Called Requirements & Design A mistake in the design or plan that doesn’t meet what stakeholders want. Defect Coding A coding or logic mistake in source code Error Testing & Execution An observable malfunction occurring during software execution or testing. Bug  🐞 1.1 Defect A defect is any flaw or mismatch in your requirements or design artifacts. It exists before any code runs. Example: You document “Users must enter a 4-digit PIN,” but stakeholders actually needed 6 digits. That spec mismatch is a defect . 1.2 Error An error is a mistake made while coding —a typo, wrong opera...
Post a Comment
Read more

Keys.RETURN vs Keys.ENTER in Selenium: Are They Really the Same?

When you're automating keyboard interactions with Selenium WebDriver, you're bound to encounter both Keys.RETURN and Keys.ENTER . At a glance, they might seem identical—and in many cases, they behave that way too. But under the hood, there’s a subtle, nerdy distinction that can make all the difference when fine-tuning your test scripts. In this post, we’ll break down these two key constants, when to use which, and why understanding the difference (even if minor) might give you an edge in crafting more accurate and resilient automation. 🎹 The Subtle Difference On a standard physical keyboard, there are typically two keys that look like Enter: Enter key on the numeric keypad. Return key on the main keyboard (near the letters). Historically: Keys.RETURN refers to the Return key . Keys.ENTER refers to the Enter key . That’s right—the distinction comes from old-school typewriters and legacy keyboard design. Return meant returning the carriage to the beginning ...
Post a Comment
Read more

What Is a Feature Flag?

  A feature flag (also known as a feature toggle) is a powerful software development technique that allows developers to enable or disable specific functionality in an application without changing the code or redeploying the software. 🧠 Core Concept Feature flags act like switches embedded in your codebase. They control whether a feature is active or inactive at runtime. This lets teams test, release, or hide features dynamically. 🚀 Benefits Safe Deployments : Deploy code with features turned off, then activate them when ready. A/B Testing : Roll out features to a subset of users to gather feedback. Quick Rollbacks : If something breaks, just flip the flag off—no need to revert code. Continuous Delivery : Decouple feature releases from code deployments for smoother CI/CD pipelines. User Segmentation : Tailor experiences for different user groups. 🧩 Types of Feature Flags Type...
2 comments
Read more