Quality Testing

Quality is delighting customers

What are the steps to be taken by a tester, when a development team rejects the defect?

I feel a tester should provide the screen shot of the defect and he/she needs to explain why it is a bug/defect.

Views: 257

Reply to This

Replies to This Discussion

this requires bug advocacy skills in order to make the dev team to fix it.

still it also depends on business requirements most of the time and the time/cost factors to fix it!

if it hampers the purpose of end user then, you may convey this to dev team using bug advocacy skills , producing right artifacts.
Tell your high management in case reject the defect.
The tester should provide not only the screen shot(s) but the steps to reproduce the defect and the environment on which he is testing the application.
Also the tester should provide the screen shots of the requirements document which depicts the defect.
Provide different type of scenarios for reproducing the bug with screen shots.
Hi krishna,

If tester has sufficient data during submitting bug & If it is important to fix it then noboday can reject it.
But for that you should have clear mind . why this bug is important?

In addition , also practice to attach screenshot of the bug.it will decrease some level of communication gap.

Still if anybody reject it , then ask for a reason to reject a bug.atleast you will know reason & try to accept it if it is valid.

Thanks & regards,
Vishal Shah
The best thing is to report the defect with all the details like the Environment on which tested, Browser details, DB details, Build number along with the test data.

When a defect is rejected

1. Go back and retest again to make sure that the defect is still existing.
2. If the Developer is in the same location show them how can he reproduce the issue
3. If the developer is in a different location, Capture the reproduction steps along with the screen shot (of UI and DB entries, XML request /response) and send the same to the developer so that the developer can reverify and fix the issue.
4. Some times issue can only be reproduced on the QA environment. In that case developer should be given access to QA env. so that they can see the log files for analysis.
At first it depends on a reason why developer rejected this deffect. And, of cource, on the processes :) I mean how the development process is organized.
Any way to avoid unnecessary questions, false rejects and not to loose the time I recommend:
1) When you post a bug provide the build version and environment where it was found;
2) Provide short description of a bug;
3) Then provide detailed steps how to reproduce it to be sure developer will be able to repeat them correctly.
If developer rejected a bug - then ask him by which reasons he rejected it and which build and environment he used for this.
If you cannot reproduce it yourself on the same build and env - close with a mark "retested, not reproduced".
If it reproduced - talk with developer, then reopen the issue and provide additional comment.
If it's not a bug - so close it with a mark "closed, not a bug".
Tester should provide the screen shot and he/she is able to reproduce the issue in the developer system(desktop) also
The reproducibiltiy steps should be mentioned properly and the bug repro percentage should be mentioned exactly
Click on this: http://www.kaner.com/pdfs/bugadvoc.pdf : Kem Caner's paper (as a Professor of Computer Science and a Professor of Law) on "Bug Advocacy".
1. Why the defect was rejected, due to poor documentation or could not able to reproduce. If not able to reproduce but it happened why was the log files were not verified. I should say defect raised will always has occurrence unless and until tester him self knows that defect was not valid

2. On what criteria defect was rejected.

3. Defect raised was due to out of box thinking, rational or logical thinking but still not mentioned on requirements.

4. Does BA joined discussion or issue was prior discussed then with some good information discussed with Dev team.

5. What were the comments provided when defects was rejected, does comments provide reasonable information.

And the list will go on, I would say if defect rejected where is the problem in tester or dev. Then we need to start digging to support issue reported.

Please mention the bug in detailed, as in steps with the help of screen shots which environment(OS,Browser Specifications etc.) and you are able to reproduce the bug.


TTWT Magazine





© 2020   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service