Answer Posted / mahantesh
S1 need not always be P1 though S1 happens to be P1 more often.
Marking S1 bugs as P1 depends on the following factors:
1. Impact on the business needs
2. Is it a showstopper or test-stopper ? If not, it could be
set to medium priority in the initial phases of project.
3. Probability of customer coming across(executing) that
scenario
4. In case bug is reproducible in previous releases, has
customer reported that bug?
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
What were the major challenges u faced while testing
Can anyone tell me about banking project? abt the transactions? the flow?
. Is any graph is used for code coverage analysis?
what is traceability matrix and its usefulness
what are your thoughts on SPRINT duration
value momentum
Why Equivalence Partitioning is called equivalence or what is the significance of equivalence term in ECP?
How would you test a service oriented architecture (soa) web application?
test cases for Insurance Processing System ?
What is software review?
What are the basic forms of variations?
What is desk checking and control flow analysis
what r u r responsibilities in current project
Risk Analysis a) 2 step, b)3 step, c) 4 step, d) 6 step
what is acid testing?