Defect severity vs. priority in Agile testing...
First I will define the actual definition of severity and priority,
Severity - Causing pain, difficulty, anxiety, damage.
Priority - Something that is very important and must be dealt with before other things.
Once u read the actual definition u can able to understand and define it. Mostly or u can say that 90 percent priority and severity are same. Many older bug tracking systems had two fields, priority and severity. Like most modern bug tracking systems, FogBugz only stores the priority. severity and priority is defined in High severity, low priority and medium priority,or u can say that depend on bug tracking tools like test trace pro,priority and severity is defined on A,B,C,D.
Priority” is associated with scheduling, and “severity” is associated with standards. “Priority” means something is afforded or deserves prior attention; precedence established by order of importance (or urgency). “Severity” is the state or quality of being severe.
Severity is associate with user and priority is associate with Stakeholder.
The severity to the testers is the impact of the defect on the application and their ability to continue testing. The priority is the domain of the business and should be entered by them against each defect raised to reflect the importance of the change to them.
Take an example:
For instance, a spelling mistake would be deemed as a low severity by the tester, but if this mistake occurs in the company name or address, this would be classed as high priority by the business. An inability to access a rarely used menu option may be of low priority to the business, but the severity is high as a series of tests cannot be executed, all dependent on access to the option.
In this example severity is low but priority is high...
Priority = Business = Order of Fixing
Severity = Tester = Failure of Application
Severity - Causing pain, difficulty, anxiety, damage.
Priority - Something that is very important and must be dealt with before other things.
Once u read the actual definition u can able to understand and define it. Mostly or u can say that 90 percent priority and severity are same. Many older bug tracking systems had two fields, priority and severity. Like most modern bug tracking systems, FogBugz only stores the priority. severity and priority is defined in High severity, low priority and medium priority,or u can say that depend on bug tracking tools like test trace pro,priority and severity is defined on A,B,C,D.
Priority” is associated with scheduling, and “severity” is associated with standards. “Priority” means something is afforded or deserves prior attention; precedence established by order of importance (or urgency). “Severity” is the state or quality of being severe.
Severity is associate with user and priority is associate with Stakeholder.
The severity to the testers is the impact of the defect on the application and their ability to continue testing. The priority is the domain of the business and should be entered by them against each defect raised to reflect the importance of the change to them.
Take an example:
For instance, a spelling mistake would be deemed as a low severity by the tester, but if this mistake occurs in the company name or address, this would be classed as high priority by the business. An inability to access a rarely used menu option may be of low priority to the business, but the severity is high as a series of tests cannot be executed, all dependent on access to the option.
In this example severity is low but priority is high...
Priority = Business = Order of Fixing
Severity = Tester = Failure of Application
Comments
Post a Comment