What will you do if your developer doesnt agree with you on
the severity and priority that you assigned to a bug
Answers were Sorted based on User's Feedback
Answer / chandra
The Question here is not about the Developer accepting the
defect as a defect or not.. this is about the severity and
priority of the defect not been agreed by the SE..
To answer the question....
As you all know Severity and Priority are two different
measures of a Defect...
S : Technical Measure
P : Business need.... (in other words..Users urgency)
During the kick off.. A set of rules will be defined on
assigning the severity and Priority to the defects...
Severity : 1 - Cannot work further..(technically.. system
crash.. cannot login.. application not available... etc..)
2 - A major portion of the application testing is blocked
due to a failure.. (Say you are checking a reporting tool
which will send out notification email after the report
finish running... and the notification server has issue and
no notification is sent after the report completes running)
3 - Any functional Defect.. (cannot save a record. cannot
process a calculation etc)
4 - minor UI issues or spelling mistakes etc..
5 - suggestions or nice to have things...
on the other hand priority is purely user dependent..
A user can set a priority of a spelling mistake as P1. as
it is important for him.. so SE cannot argue at this
point..
So Defects whose levels are set as per the above
calculations will hardly see a rejection from SE..
If nothing workds .. there is always a DRB or Triage group
which decides the Sev/Pri of a defect..
Hope this answers the question....
Cheers
Chandra
| Is This Answer Correct ? | 12 Yes | 0 No |
Answer / aman
If developer does not agree , then I will firstly send the
snap shot to him for consideration of the bug.
If then also there are problem of not accepting then I will
include the senior member and architecture into this.
It will be learning Phase for me as well as the developer in
that case.
Aman
aman.testing@gmail.com
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / prasanna raghava
We will send snap shots of the bugs to the development team
and also we will inform to our Team Lead regarding the issue
and he will take care of it.
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / phani
Hi,
In my view,sevirity is given by TEs and priority is based
on the time to release if release date in near its high far
lowpriority respectivly.
priority is nothing but time taken to fix the bug by
adevolper based
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / ramprasad.s
Hi
Steps & procedures with attachments will be sent to the
developer .
It may not be reprodusable at the developer end
or
The Retested build may again cause bug whild doing
regression Test.
We have send the test scenario wise to the developer.
u got it.
sun_ramprasad@yahoo.com
| Is This Answer Correct ? | 0 Yes | 2 No |
What is back to back testing?
what kind of test cases we can automated.how to divide manual and automation test cases.
test cases for Insurance Processing System ?
How do test documents in a project span across the software development lifecycle?
what is the difference between smoke, sanity and dry run testing?
what is cause effect graph & exp its types?
Guys, can any one of u give the realtime example for Beta Testing
How important is Change Management in today's computing environments?
regression, functionaltesting, intergration testing, UAT, re- testing. what is order of testing. which one comes 1st,2nd,3rd. tell order
what is cyclomatic complexity
What are initial and end conditions?
what is increment testing approach?