As a part of our software testing series, we focus on one concept each time. Today, we will try to understand the difference between severity and priority. It often becomes confusing as far as these two terms are concerned. We will try to simplify them for you. For studying this subject in depth, one can take the help of software courses in Pune. Many software institutes in Pune conduct such courses.
Regarding the question, what is the difference between severity and priority?
Priority characterizes the request in which we ought to determine a defect. Would it be a good idea for to fix it right now, or can we wait for sometime? This priority status is told by the tester to the developer specifying the time period to resolve the defect. On the off chance that a high priority is set, then the developer needs to fix it as early as possible. The priority status is set in light of the customer prerequisites. For instance: If the organization name is incorrectly spelled on the landing page of the site, then the priority is high while severity is low to fix it.
Types of priorities:
The defect must be settled at the earliest opportunity in light of the fact that the defect is risking the application or the product on an extreme level. The system can’t be utilized until the repair work has been carried out.
The defect ought to be resolved in the typical course of development exercises. It can hold up until a new build or version is developed.
The defect is an aggravation which ought to be repaired, however repair can be conceded until after more genuine defect has been fixed.
Learn the other concepts related to software testing by joining software testing classes in Pune. Let’s get on with severity now.
It is the degree to which the defect can influence the software. At the end of the day it characterizes the effect that a given defect has on the deliverables. For instance: If an application or site page crashes when a remote link is clicked on, for this situation clicking the remote link by an user is rare yet the effect of application crashing is extreme. So the severity is high yet priority is low.
Types of severity:
The defect that leads to the termination of the total system or at least one segment of the system and causes broad corruption of the data. The fizzled function is unusable and there is no worthy option strategy to accomplish the required outcomes then the severity will be said to be critical.
The defect that leads to the shut down of the total system or at least one part of the system and causes extreme corruption of the data. The fizzled function is unusable yet there exists an adequate option strategy to accomplish the required outcomes then the severity will be assigned as major.
The defect that does not bring about the closure, but rather makes the system create erroneous, fragmented or conflicting outcomes then the severity will be expressed as moderate.
The defect that does not bring about the closure and does not harm the ease of use of the system and the coveted results can be effectively gotten by working around the defects then the severity is said to be as a minor one.
The defect that is identified with the upgrade of the system where the progressions are identified with the look and field of the application then the severity is expressed as a cosmetic one.
Thus we saw the points of differences between severity and priority. For more details on this, a software testing institute in Pune would be of great help.