Give an example of high severity and high priority bug, and
low severity and low priority bug.
Answers were Sorted based on User's Feedback
Answer / eshwar
Although you have answered correctly,
U have not read the question properly.
I.E Question was for High Severity,Priority Low Severity,
Q.High Severity High Priority
Ans:-If there is a functionality of Calculator Pressing 2+2=7
then severity is high at the same time priority is also high.
Q.Low Severity Low Priority
Ans:-If the Font Size of the text from one page to another
page is varying slightly then we can say it as Low Severity
and Low Priority.
|Is This Answer Correct ?||23 Yes||0 No|
Answer / sriharsha
1]High Severity And Low Priority----If there is an
application , if that application crashes after mulple use
of any functionality (exa--save Button use 200 times then
that application will crash)
Means High Severity because application chrashed but Low
Priority because no need to debug right now you can debug
it after some days.
2]High Priority And Low Severity---- If any Web site
say "Yahoo" now if the logo of site "Yahoo" spell s "Yho" -
---Than Priority is high but severity is low.
Because it effect the name of site so important to do
but it is not going to crash because of spell chage so
1. Bug causes system crash or data loss.
2. Bug causes major functionality or other severe problems;
product crashes in obscure cases.
3. Bug causes minor functionality problems, may affect "fit
4. Bug contains typos, unclear wording or error messages in
low visibility fields.
1. Must fix as soon as possible. Bug is blocking further
progress in this area.
2. Should fix soon, before product release.
3. Fix if time; somewhat trivial. May be postponed.
|Is This Answer Correct ?||11 Yes||2 No|
How to test and to get the difference between two images which is in the same window?
What are the test artifacts involved in qa?
What are the challenges faced with the 1+ years experience team.
Is there any other tool like QC which we can get as open source. the software should be able to write test cases, store documentation, dashboard and bug report. If anyone can suggest me it would be helpful.
What are all the possible Risks and it's Management Technics in Software Testing?
what are the contents in Test plan?
What is workflow testing?
Web 2.0 Style Software Testing Management System- any suggestions?
What is test execution/efficiency metrics?
How Google apps can be considered ? Either they are product or Project
What are the dimensions of the risks?
How do you audit configuration management