why is it necessary to give a priority to the test cases or/and requirements.

why is it necessary to give a priority to the test cases
or/and requirements.

why does the Test case ID is not sufficient to identify the
test cases to be executed first.

Question Posted / vijaya

2 Answers
13027 Views
I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

why is it necessary to give a priority to the test cases or/and requirements. why does the Test..

Answer / ratnakar

Assigning a priority to test case is very much different
from assigning a priority to a bug.

When it comes to why we need to assign a priority to test
case, let me take you through a scenario. For example take
the yahoo login page. This has 4 generic combinations

1. Correct Username, correct password - P0
2. Correct Username, wrong password - P1
3. Wrong Username, correct password - P1
4. Wrong, username, wrong password - P2

If you see, I have assigned a priority to each case above.
P0 being highest priority and P2 being the least priority.
While preparing the test cases, we need to consider all
different inputs that an application can take and from
randomised sources. Some cases, you may feel are very basic
and need not test, but as tester, it is our responsibility
to list them. During this, for any such scenario we assign
a low priority. So depending on the time frame and the
quality bar defined to us, we start executing the test
cases based on their priority. If time does not permit, we
may leave side the low priority test cases.

Most of the release criterias would be to execute and fix
100% of the P0 and P1 testcases and bugs.

Is This Answer Correct ?

24 Yes

1 No

why is it necessary to give a priority to the test cases or/and requirements. why does the Test..

Answer / vidya

why is it necessary to give a priority to the test cases
or/and requirements?

Issue priority is the order in which issues are addressed
by developers.

In Companies, issues are triaged by supervisory personnel,
who may adjust the severity level and who will then assign
the issue a priority and dispatch it to a developer for
remediation.

Developers are expected to remediate issues in priority
order.

We don't always fix issues in order of severity. I may
assign less-experienced developers a medium or low issue,
even though outstanding showstopper issues still remain. I
may do this because they have no experience with the sub-
system where the showstopper resides,

Issue severity gives management a good impression of the
current state of the software being developed. It also
serves as a foundation for establishing issue priority.
Issue prioritization gives developers a clear understanding
of the order in which they should work on their defects.

Is This Answer Correct ?

4 Yes

9 No

Post New Answer