
- Forum
- Testing
- Software Testing
- testing
testing
This is a discussion on testing within the Software Testing forums, part of the Testing category; can anyone tell the difference between priority & severity?...
-
10-03-2006, 02:18 PM #1
- Join Date
- Sep 2006
- Answers
- 4
testing
can anyone tell the difference between priority & severity?
-
testing
The word "priority" is associated with scheduling, and the word "severity" is associated with standards. "Priority" means something is afforded or deserves prior attention; a precedence established by urgency or order of or importance.
Severity is the state or quality of being severe; severe implies adherence to rigorous standards or high principles and often suggests harshness; severe is marked by or requires strict adherence to rigorous standards or high principles. For example, a severe code of behavior.
The words priority and severity do come up in bug tracking. A variety of commercial, problem-tracking / management software tools are available. These tools, with the detailed input of software test engineers, give the team complete information so developers can understand the bug, get an idea of its severity, reproduce it and fix it. The fixes are based on project priorities and severity of bugs. The severity of a problem is defined in accordance to the end client's risk assessment, and recorded in their selected tracking tool. A buggy software can severely affect schedules, which, in turn can lead to a reassessment and renegotiation of priorities.
U can also find this information at following link.................................... What's the difference between priority and severity?
-
HI ,
Padmajasrinath,
Seviority:
seviority to the defect will be given by the tester only
we will give this seviority by how much this defect is affecting purticular application or functionality
Priority:
priority will be given by the testlead and technical lead people
here in pool of defects they will give priority to defects to which defect has to be fixed first
If u have any doubts regarding this please feel free to contact
Thanks&Regards
Bharath.P
-
10-18-2006, 03:02 PM #4
- Join Date
- Oct 2006
- Answers
- 1
-
02-01-2007, 01:33 PM #5
Seviority: Reflects seriousess of the bug.
How serious of the bug knows throuh severity.
Severity is nothing but impact of that bug on the application.
Priority: Is nothing but importance to resolve the bug.
Which one need to solve first knows through priority not with severity.
Thanks
Shiva
E-SoftSys
-
02-02-2007, 05:21 PM #6
- Join Date
- Dec 2006
- Answers
- 3
priority & severioty
Defect Severity - Another important aspect of defect tracking is to objectively define your defect severities. If this is subjective, team members will struggle classifying the severity. Below are severities that are objective:
1-Crash - Set when the defect causes the software to crash
2-Major Bug - Set when there is a major defect with NO workaround
3-Workaround - Set when there is a defect but it has a workaround
4-Trivial - Not a major bug, trivial (e.g. misspelling, etc)
Defect Priority - Similar to severity, the priority for resolving the defect should be objective, not subjective. Below are priorities that are objective:
1-Fix ASAP - Highest level of priority, must be fixed as soon as possible
2-Fix Soon - Fix once the priority 1 items are completed
3-Fix If Time - Fix if time allows, otherwise, fix in a future release
Severity tells us how bad the defect is. Priority tells us how soon it is desired to fix the problem
-
02-05-2007, 06:55 AM #7
- Join Date
- Feb 2007
- Answers
- 4
Priority tell about how soon the bug should fixed?
Severity tell about how bad the bug impact is?
-
Sponsored Ads
«
manual
|
regression
»

Reply With Quote






