How would you prioritise your test and why?

Questions by bugheads4sevy   answers by bugheads4sevy

Showing Answers 1 - 27 of 27 Answers

kumsan060

  • Dec 13th, 2007
 

Assigning priority in testing play vital role in testing because it gives the idea to the developer which i have to be fixed first in this module or what are the critical errors to be fixed now
Assigning priority
Priority 1 - Critical/Fatal -- It should be fixed immediately
Priority 2 - Major  - It should be fixed before delivering to the customer
priority 3 - Minor -- It should be fixed in the next module or omitted

  Was this answer useful?  Yes

srinivasulub1981

  • Feb 26th, 2009
 

Prioritising the tasks is the duty of Team lead, if at all team lead assigns you to tasks at the same time and given some time, in that case prioritise the tasks is team members duty.

For ex: If a team member having 2 tasks and need to start the testing at the same time,? first task for?complete testing and 2nd one is just retesting only one issue, in this case i can choose retesting as first task and go for 2nd task

So finally i can say one thing, prioritising the tasks is completely depends on experience and date of delivery.

Srinivas

  Was this answer useful?  Yes

kurtz182

  • Dec 2nd, 2009
 

A priority classification of a software defect is based on the importance and urgency of resolving the error.  A common priority classification is as follows:

Priority 1 (Immediate): The bug should be resolved immediately.
Priority 2 (High): This bug should be resolved as soon as possible in the normal course of development activity, before the software is released.
Priority 3 (Medium): This bug should be repaired after serious bugs have been fixed.
Priority 4 (Low): It can be resolved in a future major system revision or not be resolved at all.

  Was this answer useful?  Yes

  • Nov 1st, 2011
 

All the above answers are vague with lot of open ended questions like how does a QA decided know if a particular requirements forms the core functionality; how will a QA know missing a particular requirement will prove fatal to the application? The second question sort sounds like a bug instead of a test cases.

I disagree with all the above answers. Sorry guys you all have the wrong answers!

Here is the best practice tip and the answer interviewer is looking for.
Every project does have a BRD - business requirements document - where the high-level business requirements requested by the client are listed.

grr..I know functional requirements but what are these business requirements..? Let's attack that then!
"what" client wants forms the business requirements. "how" do we implement those "what" needs within the best interest of the client forms 'functional' requirements.

Now the real juice..
Since QA has the list of business requirements, QA can go look for the functionality/features attached to those business requirements. Business requirements may include high-level features, in that case its all the more easy for QA to prioritize test cases - decide which test cases are more important over the others. All the test cases that can eventually be traced back to a business requirement form the core functionality test cases. Therefore, the core functionality test case has higher priority over the rest of the test cases.

In case formal BRD is absent and client gives a small project to work on, there will at least be an email or some document that will list the high-level requirements. Even in this case you can still apply the above tip - any test case that can be tracked back to the business requirement has higher priority.

what if the application is already in production and your company is just maintaining it. In that case QA manager/lead whoever is managing the QA team needs to ask client what features have high priority. Client might come back and say "anything on home page is high priority as I want to attract more users to my site. Ads being functional is least bit to worry about." So now you know that home page UI, elements on home page, etc all come under high priority test cases umbrella.

Why is it important to prioritize test cases??
Simple : to make sure the core functionality is bug free, and the high-level business requirements comply with high quality standards.

mithr17

  • Nov 2nd, 2011
 

sorry forgot to add..

..all the test cases with P1 AKA high priority will be smoke tests. Sanity tests will include some of these P1 test cases based on the affected features.

  Was this answer useful?  Yes

mithr17

  • Nov 3rd, 2011
 

@ kurtz182

The question is about "test" priorities and not "bug" priorities. Many of the organizations that have high quality gates set have started the trend of prioritizing the test cases. Your answer would be great if the question was"bug priorities." Just a reminder: please read the question before hurriedly posting an answer

  Was this answer useful?  Yes

Rohit

  • Sep 2nd, 2015
 

@mithr17
Interviewer will sleep after listening the answer that you give it is dam big you should give extract of all points this answer is also incorrect and except that all answers are right

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions