Defect Rejection

What will you do when developer rejects your defect?

Questions by tester582

Showing Answers 1 - 9 of 9 Answers

Ravi raj

  • Feb 11th, 2011

When devloper Reject the difect fisrt we need to know cause of the rejection.

In Quality Center or Test Director Developer will update his comments with proper justification,if you found there is a gap from devloper  to tester then you need to provide the Valid screen prints of the defect.

Even if devteam team is not accepting then you can involve the SA and BA team and take the confirmation on the defect.

  Was this answer useful?  Yes


  • Feb 21st, 2011

When a developer rejects a defect then we (testers) have to check on which reason he rejected the defect.

The developer may reject the bug if it is "Non Repro" or  "Known issue"  or "Duplicate "
or if it is according to requirements or if it is not a valid bug.
1. If status he mention is  "Non Repro" , then we have to add sufficient repro steps about that defect in defect tracking tool.

In case he doesnot satisfied we have to repro in presence of developer in test machine.

Even though he not satisfied then we have move the issue to our Lead.

  Was this answer useful?  Yes


  • Nov 2nd, 2011

1.if the T.E understand the req wrongly and have this issue is communicated with

ex:the req is 1+1=2 but the t.e understand 1+1=11.

2. if the dev understand the req(defect) wrongly and have this issue is communicated to T.E

in these situations the T.E provide the following details

1.the t.e need to provide BUILD DETAILS.

2.the t.e need to provide envi.detials

3.he provide screen shots
4.he provide log files

5.the appropriate testing data need to provide.

6.the t.e try with another comp.and he report to developer.

7.web conference/video conference

  Was this answer useful?  Yes

Anila Philip

  • Oct 3rd, 2012

-> Shows the defect directly and ask the reason for rejection, If we get satisfied reply the testers can close the bug other wise will Reopen and Reassign the bug to corresponding Project leader

  Was this answer useful?  Yes


  • Nov 26th, 2013

Developer generally reject a bug,when,he find that,the bug is not genuine.

  Was this answer useful?  Yes


  • Jan 28th, 2014

Bug is a deviation from the expected result
Defect is is the problem with internal core of the application and requires full attention

  Was this answer useful?  Yes

Prabhu Prasad Mishra

  • Apr 14th, 2014

As a tester I would try to replicate the issue (and if issue still exists), then, take screen shots, give reference to the software requirement specification document to the bug, give a unique ID to the bug, give a detailed description of the bug, and write the test steps for the scenario for which the issue raised.

  Was this answer useful?  Yes

B reddy

  • Jul 23rd, 2014

If the raised defect is not related to that developer he will reject the defect.

  Was this answer useful?  Yes

Piyush Patwa

  • Nov 20th, 2017

If developer rejects the Bug. Follow the same steps with which the Bug was reproduced earlier. The bug verification should always be performed once before closing the Bug and if you come across the same bug again Reopen the bug and assign the Bug to dev so that the Bug is fixed on some later day as per the priority and Severity
There might be a cases as if the bug might not exist actually.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions