When a defect is marked REJECTED by a dveloper, what should we do it.
-
Close the defect without verifying developer comments.
-
Check developers comments and simply close the bug
-
Reopen the bug.
-
Check the developer comments and reopen the bug if you do not agree with it.
When a developer rejects a defect, the tester should review the rejection reason, verify if it's justified, and reopen if they disagree with the developer's assessment. Simply closing without review, or always reopening, are both incorrect approaches.
Correct: when a developer rejects a defect, the tester should review the developer's comments/evidence and reopen the bug only if they disagree with the rejection (e.g., they can still reproduce it, or the rejection reasoning is flawed) — otherwise the defect stays closed/rejected. Blindly closing without reading the comments is negligent QA practice. Simply closing 'after checking comments' without judgment skips the tester's responsibility to validate the rejection. Reopening unconditionally, without even checking the developer's reasoning, is equally wrong — it ignores information the developer provided and wastes cycles re-litigating valid rejections. The correct workflow requires reviewing first, then deciding.