A general Question: If there are two bugs one with high priority and one with high severity, which bug should be fixed first?

Answer Posted / kunal dudka

High Priority & Low Severity:
A spelling mistake in the name of the company on the home
page of the company’s web site is certainly a High Priority
issue. But it can be awarded a Low Severity just because it
is not going to affect the functionality of the Web site /
application.

On the other hand,
High Severity & Low Priority:
System crashes encountered during a roundabout scenario,
whose likelihood of detection by the client is minimal, will
have HIGH severity. In spite of its major affect on the
functionality of the product, it may be awarded a Low
Priority by the project manager since many other important
bugs are likely to gain more priority over it simply because
they are more visible to the client.

Is This Answer Correct ?    2 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

Give an example for pre testing and post testing ?

1549


What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?)

1666


Explain the defect life cycle.

629


What is the difference between stlc and sdlc?

618


What is baseline testing?

655






What is Test Design?

1753


What are the challenges you faced in your project (Testing) and in your company?

2599


tell me some major and minor defects in ur net banking project?

3162


what are the functional test cases for enter user name,enter pass word,click on ok(only functional test cases)

1951


Write a Test scenario for Outlook Search functionality.

2597


What is system level testing?

706


What is software review?

808


Q) Create Preffered customer: As a customer when i purchase more than $5000 in goods since my first purchase, I become a preffered customer so that i can receive the benefits associated with that status.

1999


write 5 critical test cases on product payment form on flipkart.com?

1508


How do test documents in a project span across the software development lifecycle?

1154