maran

• May 18th, 2006

 

If a bug is raised by the Tester and Developer is not accepting that as a bug. The tester should be able to reproduce the bug. If he is able to reproduce the bug and he has to take the screen shot of the bug. So the tester give the clear picture to the developer and he can prove it as a bug.

Srinivas

• May 18th, 2006

 

Test Cases are prepared with reference to Use Cases which are client requirements.  If a particular Test Case Actual Result vary with the Expected Result, then definetely it is a bug.  If the programmer dont accept it as a bug, it should be reported to Test Lead for verfiication and investigation to solve the issue.

Srinivas Belkeri

leena saraf

 Profile Answers by leena saraf 

• May 23rd, 2006

 

1)Everytime when tester acknowledge it is a bug,he/she has to take snap-shot of this on safer side .

2)If you are sure,its a bug,Try to reproduce and to  in front of your test lead .

3)Mail to respective devloper keeping your testlead and PL (project lead)in cc,and try to get his comment in written that why he is saying its not a bug.

4)anyways if you are sure it is a bug,Logged it in TTPro,Littlebuggy (defect tracking tool)and assign the defect to respective Developer/programmer

shrinivas

• May 24th, 2006

 

If developer naming the bug as a pending Reject. Tester can reopen it, provide instances of the Bug. Bug seviourity & dependability should be  mentioned while reporting it

Bug seviority& dependability will also decide, programer should accept or reject.