Articles to grow your career
Priority and Severity are the two most critical attributes that can be allocated to a bug during the software testing life cycle. Attributes such as defect description, defect details, application version, steps to reproduce, test data, created by, and created date may also be assigned when a bug is logged. Still, Severity and Priority are the most frequently used.
These attributes help teams fix bugs efficiently and navigate the release scheduling process to prevent critical issues from being overlooked. In this article, Spin Career, helps you understand the difference between severity and priority to increase your knowledge.
The severity of a bug/defect on the application is referred to as its impact, including how it affects the system’s functionality and blocker defects. Testers are responsible for setting the severity parameter when reporting a bug/defect and maintaining control over it.
The four types of severity include:
Critical: A defect that entirely prevents testing a product/feature is critical. For example, should an application crash or become unusable and unable to continue, it would fall under the critical severity classification. As an illustration, in a provider of email services like Yahoo or Gmail, if the system crashes or generates an error message upon attempting to log in with the correct username and password, this defect is critical because it renders the entire application unproductive.
Major: Any feature of significant importance that fails to meet the client’s needs or intended use and deviates from the expected behavior can be categorized as a Major Severity issue. For instance, Gmail classifies a defect as Major Severity when it prohibits adding multiple recipients in the CC section, as this flaw impacts the application’s primary function.
Minor: A defect of medium severity occurs when a product or application fails to meet certain criteria or displays unusual behavior, but it does not affect the overall functionality and can be categorized as Minor Severity. For instance, if one of the links in the “Terms and Conditions” section of Gmail is not functioning correctly, it is considered a minor issue that only affects a small part of the website/application’s functionality and does not significantly impact its usability.
Low: Defects such as alignment issues, spelling mistakes, or font casing can be categorized as Low Severity. In Gmail, for instance, errors on the “License page,” like misalignment or misspellings, would fall under this category.
The order in which we address a defect is determined by its priority. The tester informs the developer of the priority status and timeframe for resolving the issue. If the priority is high, the developer must fix it promptly. The priority status is established according to the customer’s needs.
There are three types of priority, and they include:
High: The impact on the customer application is significant, requiring prompt resolution due to its adverse effect on the system’s usability.
Medium: The current version in development must have the defect resolved before release as part of standard development procedures.
Low: If there is adequate time, the flow should be remedied; otherwise, it may be postponed until the subsequent release. While the flaw is a problem, it can be addressed after resolving a more significant defect.
Four combinations of priority and severity determine which defects require immediate attention and which can be addressed later. Real-time examples illustrate this concept more clearly.
Leave an application and get a free consultation from our manager.
Understanding the difference between bug priority and severity is just as vital as comprehending other testing elements. Whether you are performing Manual QA or Automation QA, identifying the type of bug is necessary to log them properly. To learn more about software testing, you can contact Spin Career.