Plz explain with example about 1. hight severity and hight priority
2. low severity and low priority
3. low severity and high priority
4. high severity and low priority
Plz explain with example about 1. hight severity and hight priority
2. low severity and low priority
3. low severity and high priority
4. high severity and low priority
Priority determines the urgency or order of importance of the bug.
Severity determines the state or quality of being severe,how severly it affects the system.
Severity is a technical issue where as priority is a business issue.
This is also Based on the Business Rule. Team leader or QA person gives priority.
Hi, Sunny
I will give you an example like "If a system is going to crash and an alert comes saying do u want that action to be perfformed or not?" If no is clicked and even then system crashes it severe one but priority is low bcos if we change action of no button to yes ...it will be fine working..
Hi,
It is very essential to know about severity and priority since this only determines about how fast and how important the bug or error is and needs attention. It is based on this the developer or tester prioritize their work schedule. Severity tells us how bad the defect is. Priority tells us how soon it is desired to fix the problem.
Regards,
Fred
To add more to this let me tell about the values severity can take like Major, Minor or
Trivial and similarly priority can take values like 1, 2 or 3 etc where 1 is usually used to denote error with high priority defect.
The above values are needed because if the severity is major then it denotes more attention like instances of system crash or error message forcing to close the window so on. If the severity is minor then it represents low attention like instances of error only in certain parts of the application or error only during certain times.
seviority describes how serious the defect is. classified into 4 types
fatal, major,minor,suggestions
priority describes the sequence in which the defects have to be described
classified into 4 types
critical,high,medium,low
eg:there was an bus accident few members injured
seviority / priority
one went into coma fatal / critical
one lost more blood major / high
one unable to walk minor / meduim
one is talking had small injuries minor / low
one is ok suggestions / low
if any doubts ask
madhav_sus@yahoo.co.in
Last edited by msusmitha; 12-01-2006 at 06:18 AM. Reason: understandability
If a detected bug effects the system or s/w under testing and is crucial, then its severity would be high. But if it effects our business process, then its priority is high. In some cases, a low priority bug may be given a high priority sequence if it is believed that it takes long time to resolve the issue and the time in hand would not be sufficient.
Eg.
1. high severity and high priority - Database connectivity cannot be established by multiple users.
2. low severity and low priority - Small issues like, incorrect number of decimal digits in the output.
3. low severity and high priority - Images not updated.
4. high severity and low priority - In a module of say 2 interfaces, the link between them is broken or is not functioning.
Here are some of the examples ...
High severity
high prority : database not getting connected., internal server error for webpages
low priority : price field taking $,. And numeric data... But also saving other special characters like @# etc.,
medium severity
high priority : help messages missing..
Low priority : help message is displayed but too complex to understand
low severity
high priority : spelling mistakes, logo or image not updated
low priority : improper allignment, grouping of objects
anyone of u find anything wrong pls do indicate...
Can anybody tell me examples of
1. High severity and High Proirity bugs
2. High severity and low proirity bugs
3. Medium severity and High Proirity
4. Medium severity and Low Proirity
5. Low severity and High Proirity
6. Low severity and LowProirity
and in what basis we will give prority?
Bharathi refer to "difference between severity and priority" posted in Software Testing
http://www.geekinterview.com/talk/18...-priority.html
Eg.
1. high severity and high priority - Database connectivity cannot be established by multiple users.
2. low severity and low priority - Small issues like, incorrect number of decimal digits in the output.
3. low severity and high priority - Images not updated.
4. high severity and low priority - In a module of say 2 interfaces, the link between them is broken or is not functioning.
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.
-sutnarcha-
Hii Friend.........Originally Posted by bharathi_ark
My personal view about this is. If u r saying High Priority or Sevirity u must hav the reason to satisfy othrs tht why u saying so or why u assigned.U must have proper reason to say tht, so tht u can prove why it is so.
Now wht I think abt these terms
Priority:-
How quickly u need to fix tht bug.
Severity:-
How critically it wil affect the system as a whole
E.g. :-
1.High P & Low S.
name speling of organisation on site.
Reason-> It's High priority coz ur client pay u tht much cost & u given tht mistake even the name of org is wrong on site.Although it will not affect the organisation system in any way.So u can c it as high priority.
Note-> Friends Still the application under Testing when we discovered that defect.
2. High S & Low P:
(i) Any module added in the system goes to affect the whole working of
the system.
(ii) System delivered neds to done some critical changes tht only done by
org. person , simple person can't do it cause it wil shut off the whole
system.
(Reason behind High sevirity systems mainly or 99% is that it wil daimage
or affect the systems particular module or component but still can be recoered from that but
rigriously.so I given that as High Severity.)
3. Low P & Low S:
Logo of Org. Shown in left top corner but as client requirments or
discussions he/she want it in Right Top Corner.
(Reason-->Any Bug discovered in the system at later stage tht dosn't
hav as such affect on system can sy just like tht if not corrected thn
no effect on systm it's working properly. But as requirment it should not
b thr in the system.)
4. High Severity & High Priority
Suppose any Button on the interface through which personal/ secerate
record of org. get accessed & tht button is available only for the top MGT
ppls. But aas defect in the system it's also made available to all ppls.
So just think about it it's have high severity coz org. secerates can be theft frm thr & tht wil definity affect the org. as a whole if they loose thr secerates to thir enimies. High priority bcoz it's dangerious if in hands of all so need to fix as soon as or can say as early as possible.
So dear friends I think Now u got the concept of these minute differences.
Plz correct me If I m wrong, I wil b thank full to u.
.......Wishing U happy new Year.......
Thnx & regards
Rajeev Sharma
91-9818004180
Last edited by Rajeev Kant Sharma; 02-03-2007 at 06:46 AM.
Hi All,
I am working as testing engineer, still im in confustion what is severioty and what is priority. Who gives the severioty and who gives the priority.
I think tester gives the severiry and developers gives the priority..is it right?
Hi,
Severity defines impact of the defect. Priority defines the urgency of the defect to get fixed.
In my company the method we follow is,
Severity is given by Testers and Priority is given by PM's(Project Managers).
I think developers wont give priority... because the chance of giving high priority is less in that case...
Thanks
Manoj
hi,
i will try to put in simple words:
Severity: Its the impact or importance of bug with respect to application. (i.e. how much that bug will be hampering the application process.)
Priority: its the importance of the bug with respect to all the bugs. (u can say it gives an idea which bug has to be fixed first.
regards,
RSY
Sorry guys, there is already a thread for this.
http://www.geekinterview.com/talk/182-difference-between-severity-and-priority.html?highlight=priority
I can merge these posts into that thread. In fact that is the only thing I can do. While starting a thread please check if the question/topic is already posted or not by running simple search in the forum.
Thanks. Hope to see some great post from you guys.
Cheers!
Kalayama
[COLOR="Blue"][SIZE="2"]"If you are not living on the edge of your life, you are wasting space"[/SIZE][/COLOR]
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
Severity is how severe the bug is and Priority is the importance of the bug with respect to other bugs to be fixed.
Severity of the bugs is given by Testers
Priority of the bugs is decided by Project Managers.
HI,
Severity is nothing but the impact of a bug interms of application.
priority is nothing but the impact of a bug interms of client requirements.
GEnerally severity is set by testers and priority is set by Tl or PL.
A brief explanation of priority and severity. Priority is how a bug affects the customer. For example, if the main feature of the application isn't working, it has a high priority. If a rarely used feature of the application isn't working, this is a low priority. Severity is how bad the bug itself is. If there is an obvious workaround for the user, this is a low severity. If the application throws an exception and shuts down, this is a high severity. It is possible to have a high priority, low severity bug or a low priority, high severity bug. To make matters more interesting, some companies have a third field, impact, that is a function of priority and severity. Impact is used to make final decisions about which bugs will get fixed, and which will not. We will not use that here.
Example
Here's a sample for a bug in a calculator:
Title: Multiplying 3 numbers does not work
Reproduction steps:
Start application
Click a number
Click *
Click another number
Click *
Click a third number
Click =
Expected output: The multiplication of all three numbers
Actual output: The multiplication of the last two numbers only
Priority: 1
Severity: 2
The priority was 1 since this is a main feature of a calculator. The severity is 2 because users do have a workaround of multiplying separately, annoying as it is. A less annoying workaround would cause the severity to go down.
Turn in your list of manual bug reports in manual.html. Notice that bugs listed here must also be in bugs.html.
HINT: Some bugs are obvious errors in the feature. Others are subtle in that the user interface is misleading for the user. All of these are bugs!
HINT: Remember that different users will accomplish the same task in a different way. Don't go about your normal application usage. Test all possibilities!
When we come across a bug, it is given both priority and seviority. Now on what basis bug is cleared? Which is given first preference priority or seviority? In my view seviority is given first prefarence.
See priority decides on the basis of severity and time schedule.So, by default more stress goes to severity, but if it has been assigned any priority then that will followed.
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Priority is a normal status which we assign for any bug.
Consider one small example which has Priorities P1,P2,P3,P4,P5.
Here P1 is the highest priority bug and the P5 is the least and u can consider as cosmetic bug which is not so important.
In this situation, when the release date appears and the build demands that any of the above Priority bugs to be fixed then we treat that particular bug on seviority and fix that bug immediately. This will be predicted well in advance while logging the issue / bug. So that it will be taken up for fix to push the same in consequtive builds based on Priority set for Release.
Hope you got the Answer.
Thanks & Regards
Arun
Hi,
Look into "Geeks Talk > Software Testing > Testing Issues> difference between severity and priority" asked by sunny_love on 6/1/2006. You can easily understand and get the right answer from that discussion.
**********
with Thanks and Regards,
[B][I][COLOR="DarkRed"]Anushya.G[/COLOR][/I][/B]:)
**********
Re: Which is given first preference priority or seviority
the answer given by tarun is quite right....there is a try from both the sides i.e developers to match the priorities with the severity given by the testers based on the knowledge, interpretation, experience, requirements and the discussions with the designated BA...If the bug has been considered as open after testers raise it...then they are fixed according to the prority decided by the development team and most of the times testers have to conform to the given priority....and make some adjustments in their execution plan or LRD (but only if the priority assigned by the develpers is correct accoding to the discussions held till now)...
thanks
Hello aardvax and smartarun ,
First read the question carefully...
When we come across a bug, it is given both priority and seviority. Now on what basis bug is cleared? Which is given first preference priority or seviority? In my view seviority is given first prefarence.
Now give to the point answers, ok.
Tester assigned the severity of the bug.Now tester works completed.Now it's the task of CCB to assign priority.And bug will fix according to that.So, who got the preference (as the question is?) for fixing bugs, of course priority.
One more thing to disclose is that severity once assigned never change, but priority can change during bug fixing process.I hope now it should clear to all and it is more than sufficient discussion on this question.
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Hi Jain
I really praise you for your explanation of the question which was asked...
and obviously it is the job of the developers to seek for the preference of fixing the bug according to the priority given..but we do not go ahead in development of a quality product if testers and developers are at logger heads...i just tried that a conformance is necessary in interpretaion of the terms used in every organisation...and priorities are assigned based on severiites...offcourse when priorities have been decided such that testers can tolerate the delay or whtsoever in case of a raised and opened bug...then prority is the first preference to fix the bug....like a straight mathematical question.....
thanks for your post
and you know the best thing
we alll are saying the same thing
Last edited by jainbrijesh; 05-08-2007 at 02:34 AM.
I happend to hear that my friend who is working in one of MNC to whom they don't have seviority while logging the bug (means the option is disabled in QC). So it would be based on the company and the process which they follow.
Do I know the name of that MNC?
Because as I know severity column can never left blank in bug reporting.It's very important as later decisions depend on it.
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Well, I am not too accustomed to bug reporting, but I tend to agree with jainbrijesh. Severity column is most important. I also know that the bugs are prioritized based on the severity level of the bug.
It is obvious that a bug with high severity will have high priority. So, at the end of it all it doesn't really matter. If a bug has high priority, it also means that it rather severe(Except for timeline based bugs like, if the bug is not rectified within a period of time, then it might have severe business impacts though it is of less severity now).
So, at the end of the day, bugs are fixed on priority basis. And how the prioritites are fixed? Based on severity -in most of the cases.
So, aardvax is right. We are all telling the same thing
Hope this helped settling the issue.
Cheers!
Kalayama
[COLOR="Blue"][SIZE="2"]"If you are not living on the edge of your life, you are wasting space"[/SIZE][/COLOR]
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
I totally disagree My Friend !!!
QC Administrator has all the rights to disable few columns as well as setting mandatory fields to the existing columns in QC. So in this case Severity can be left blank if it’s not a mandatory :-) as set by the QC Admin
Hello varmakub,
I am not saying that it can't be done.
What I am saying is that it's not looking right logically.
If we don't have the severity, It means all bugs will be fixed and all bugs are equal severe, which is not possible in real scenario.
That's it.Otherwise, nothing is impossible, because impossible itself says "I M Possible".
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
My Friend !!!
They are categorizing the defects only based on the Priority !!!
Ok,
Then will you tell me, how they priorities the bugs?
I mean they are not using severity then what's the base for priority of fixing bugs?
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Dear friend let me close this issues !!!
The priority which inherit the severity here my friend. It works as same as severity but as we give Sev 1, in the same way they give priority, but the thing here severity is not visible.
Ok,
May be I got you right.
You mean to say, tester gives the priority directly, no any severity and that priority is followed by developers to fix the bug.
Am I right?
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Re: Which is given first preference priority or seviority
YES :-) tester gives the priority directly. !!!
Then you should say this earlier in the post.
Still it's a good discussion with you.
Ya, it is possible, even in some companies tester himself assigns both severity and priority, but of course priority may change.
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Hi all,
can anybody give me some practical examples for priority and severity.
1. high priority and low severity
2. low priority and high severity
3. high priority and high severity
vikas goyal
1. Cosmetic issuesHi all,
can anybody give me some practical examples for priority and severity.
1. high priority and low severity
2. low priority and high severity
3. high priority and high severity
vikas goyal
3. Blockers and Functional Defects
Posting Permissions
Reply With Quote