The difference between Severity and priority
2015-06-24
There is both key things in defects of the software testing. They is:
What's the difference between Severity and priority?
Severity: It's the extent to which the defect can affect the software. In and words it defines the impact that a given defect have on the system.
Severity can be of following types:
- Critical:the defect that results in the termination of the complete system or one or more component of the system and CAU Ses extensive corruption of the data. The failed function is unusable and there are no acceptable alternative method to achieve the required results then the SEV Erity'll be stated as critical.
- Major:the defect that results in the termination of the complete system or one or more component of the system and causes Extensive corruption of the data. The failed function is unusable but there exists a acceptable alternative method to achieve the required results then the Severity'll be stated as Major.
- Moderate:the defect that does no result in the termination, but causes the system to produce incorrect, incomplete or in Consistent results then the severity would be stated as moderate.
- Minor:the defect that does not result in the termination and does not damage the usability of the system and the desired Results can easily obtained by working around the defects and the severity is stated as minor.
- Cosmetic:the defect that's related to the enhancement of the system where the changes be related to the look and field Of the application then the severity is stated as cosmetic.
Priority: Priority defines the order in which we should resolve a defect. Should we fix it now, or can it wait? This "is" set by "the tester to the developer mentioning the" time frame to fix the defect. If the mentioned then the developer have to fix it at the earliest.
Priority can is of following types:
- Low:the defect is a irritant which should be repaired, but repair can being deferred until after more serious defect has B Een fixed.
- Medium:the defect should is resolved in the normal course of development activities. It can wait until a new build or version is created.
- High:the defect must be resolved as soon as possible because the defect is affecting the application or the product sever Ely. The system cannot be used until the repair have been done.
Severity and priority is not always one-to-one
- High priority & High Severity:an error which occurs on the basic functionality of the application and won't allow The user to use the system. (Eg. A site Maintaining the student details, on saving record if it, doesn ' t allow to save the record and this is the high Priorit Y and high severity bugs.)
- High priority & Low severity:the spelling Mistakes This happens on the cover page or heading or title of a Applicati On.
- High Severity & Priority:an error which occurs on the functionality of the application (for which there are no wor Karound) and won't allow the user for the system but on the click of link which are rarely used by the end user.
- Low precedence and low severity:any cosmetic or spelling issues which are within a paragraph or in the report (not on cover Page, heading, title).
The difference between Severity and priority
