Severity and Priority in testing
In this section, we will learn about the severity and the Priority of a bug in software testing
The impact of the bug on the application is known as severity.
Blocker: if the severity of a bug is a blocker, which means we cannot proceed to the next module, and unnecessarily test engineer sits ideal.
There are two types of blocker bug, which are as follows:
A major feature is not working: Login to HDFC, amount transfer is not working
The major flow is not working: Login and signup itself not working in HDFC application.
Critical: if it is critical, that means the main functionality is not working, and the test engineer cannot continue testing.
Major: if it is major, which means that the supporting components and modules are not working fine, but test engineer can continue the testing.
Minor: if the severity of a bug is major, which means that all the U.I problems are not working fine, but testing can be processed without interruption.
Priority is important for fixing the bug or which bug to be fixed first or how soon the bug should be fixed.
It can be urgent, high, medium, and low.
High: it is a major impact on the customer application, and it has to be fixed first.
Medium: In this, the problem should be fixed before the release of the current version in development.
Low: The flow should be fixed if there is time, but it can be deferred with the next release.
Note: The test engineer decides the severity and Priority, and the developer can also change the severity with a proper reason and comments on the bug reports.