Krishnamurthy

• Nov 19th, 2007

 

All testers undergo this basic problem during testing. Below given steps can be followed to resolve this issue. Such issues require joint effort from testing and development to resolve the same.
1) If development team members are in same location, bring them over to your testing place and reproduce the issue so that they can debug further.
2) If development members are not in same location, try to get the various logs during this process and see if you can send them all the logs along with the snap shot of failure.
3) You can also share the m/c details with login information for the developers to login and check various things on the testing machines.

Rajendra.Atm

 Profile Answers by Rajendra.Atm 

• Feb 4th, 2008

 

Exactly!!!

Good Reply

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Nov 13th, 2009

 

DEV RESOLVES AS NOT REPRO
This is a common scenario among testers and developers.  If the developer resolves the defect Not Repro, then I would

1) Reopen the defect and provide additional detail that will compel the developer to investigate further.  I would provide
   a) clear and concise description of the problem,
   b) screen shot showing where in the program the crash occurred
       as well as a screen shot of the page which demonstrates the crash,
   c) all of the environment details including computer OS, browser and versions
2) If possible, I would run through the test steps with the developer present.

DEV RESOLVES AS WON'T FIX
If the developer resolves the defect Won't Fix, then I would reopen the defect and submit compelling reasons why this defect needs to be fixed.  In this case, the developer realizes the defect exists but doesn't believe it is worth fixing.  If the developer feels that users will rarely if ever experience this issue (perhaps the tester discovered a edge case and this is not a Sev 1 Pri 1 issue), then the tester should strive to get the issue postponed until a future release.