Bug Tracking - Severity and Priority for bugs

GeekInterview.com > Interview Questions > Testing > Bug Tracking

Go To First | Previous Question | Next Question

Bug Tracking | Question 80 of 94

Severity and Priority for bugs

Give me example for BUG that has HIGH SERVERITY and LOW PRIORITY and SAME BUG in other case should be LOW SEVERITY and HIGH PRIORITY.
Note : It should be SAME BUG NOT TWO DIFFERENT BUGS

Total Answers and Comments: 5

Last Update: December 09, 2008 Asked by: rk_pradheep

Sponsored Links

Best Rated Answer

—

Submitted by: rsreddy

Low severity: Application crasher from only one customer in 1000 customer that to for wrong use case.

High severity: Where as application crashes ,but prority is very less to fix the bug and will effect only one custoer

High prority & Low severity: Suppose you are having a bug that there is a spelling in the name of the project/product.Here the severity is less as it does not effect any thing,but the prority it should fix why bcoz this bug is very high prority,if any one catch it the image of the project or prodct will effect and get bad impression.so this is high prority.

Above answer was rated as good by the following members:
charub

February 17, 2008 05:59:50

snigdha_agrawal

Member Since: February 2008 Contribution: 2

RE: Severity and Priority for bugs

Generally There are 3 kinds of severity of bug:

High---These bugs are the ones which are the most serious ones and has to be resolved immediately.As they do not allow us to proceed further in running the application.They can also be called as show stoppers.
So these bugs has highest priority to get resolved.

Medium--- Are of medium importance.Medium Priority

Low -- UI related issues comes under this. Lowest in priority in fixing it.

Is this answer useful? Yes | No

February 25, 2008 09:28:58

vinu.doniv

Member Since: February 2008 Contribution: 1

RE: Severity and Priority for bugs

In terms of Severity and Priority for bugs

Sevrity Would Remain Constant ...
Since the impact is on the application whereas
Priority Would Change according to the situations..
Since the importance is given to the application... in order to fix

Is this answer useful? Yes | No

May 19, 2008 02:59:55

rsreddy

Member Since: May 2008 Contribution: 2

RE: Severity and Priority for bugs

Low severity: Application crasher from only one customer in 1000 customer that to for wrong use case.

High severity: Where as application crashes but prority is very less to fix the bug and will effect only one custoer

High prority & Low severity: Suppose you are having a bug that there is a spelling in the name of the project/product.Here the severity is less as it does not effect any thing but the prority it should fix why bcoz this bug is very high prority if any one catch it the image of the project or prodct will effect and get bad impression.so this is high prority.

Is this answer useful? Yes | No

1 0

Overall Rating: +1

October 03, 2008 06:00:53

kaushal3858

Member Since: October 2008 Contribution: 2

RE: Severity and Priority for bugs

Simple Example of Severity and Priority for bugs

If you are doing webtesting for any Company wesite and in that if you found the company logo different then for webdeveloper its easy to change means severity is low but from comany point of view its logo is in proper way so that time priority is high.

If you are doing testing for UK client and if you found the date format MM/dd/yyyy(in UK its dd/mm/yyyy) then for develor its change the format of date is not big issue that time from developer point of Priority is low and severity id high.

Is this answer useful? Yes | No

December 09, 2008 05:55:49

srinivasulub1981

Member Since: December 2005 Contribution: 381

RE: Severity and Priority for bugs

Before answering this question i would like to say some thing abt my project mine is a project it contains both US and UK clients... but both are using same files...

Desc about some functionality: A user can do volunteering to any of the charity with some hours say for example he has volunteered 40 hours for a charity then he can elible to apply for some grant from his company again this grant will goes to charity.

HIGH SERVERITY and LOW PRIORITY

Issue: Now the issue is out of all users applications works perfectly but not worked only for one user who done his volunteering in last year other than this year in this case we can consider this as High sev and low priority if the release time is over for testing team perspective.

LOW SEVERITY and HIGH PRIORITY.

The same issue will considered as Low severity and high priority in client perspective as he has so many clients.

Let me know if i am wrong

Srinivas

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank