1) Can you tell me the High severity and low priority bug,High
priority and low severity bug?
Answers were Sorted based on User's Feedback
Answer / jasbir ahlawat
High Severity And Low Priority
This means that the bug will have severe affects if not
resolved but since it is not blocking our testing or some
other functionality so there is no urgency to get this
resolved.
High Priority And Low Seveirty
I hope you can answer this now.
But these are like rare kind of sceanrios in real time
because any bug which is severe must be critical and should
have high or medium or Very High priority and not Low.
Hope it makes sense!!
Thanks,
Jasbir Ahlawat
Accenture
| Is This Answer Correct ? | 7 Yes | 0 No |
Answer / selia
Example of high severity and low priority bug:
If you fill a form, and on clicking on the Submit button,
the user information is not getting stored in the database
and is lost. We will give it a high severity. But since the
delivery for this module is two weeks from now, the bug can
be fixed later on, so we give it a low priority.
Example of low severity and high priority bug:
There is a spelling mistake in the text, is a low severity
bug since it is not breaking any functionality. But this
module needs to be complted tomorrow, so we assign it a
high priority.
| Is This Answer Correct ? | 8 Yes | 2 No |
Answer / ashok
In Banking application the speling mistake marks a low
priority and also low severity. Where as in e-learning that
marks a low severity but high priority. It all depends on
the AUT.
| Is This Answer Correct ? | 1 Yes | 1 No |
Test Director is use only for bug tracking or another purpose.
Can a Tester test any application without Specifications/Requirements?
When we perform Smoke & Sanity testing?
Is Beta Testing done by devolopers or testers?
Explain the End Goals of Usability Testing?
Tell me the Test cases for the Fan?
what reesponsibility of system administrator?
what is the format of traceability matrix u prepared in ur company?
What is smoke testing?
If a bug has high severity then usually that is treated as high priority,then why do priority given by test engineers/project managers and severity given by testers?
How to prepare Test data?
How do you decide when you have 'tested enough?'