Your bug is rejected. What would you do? September 19, 2015 / Thanh Huynh / 2 Comments Regardless of how good you are as tester, you will have your bug rejected some days by your developer. This is unpleasant situation but it happens time to time in tester's life. What would you do if your bug is rejected? Sharing is caring:Click to share on Facebook (Opens in new window)Click to share on Twitter (Opens in new window)Click to share on LinkedIn (Opens in new window) Question Previous post What skills / approach need to follow so any team can give the services in software testing? Next post Can we make test plan without finalizing SRS. 2 Comments Rita Hasan Chowdhury September 20, 2015 at 4:27 pm I have the same question Tri Nguyen September 21, 2015 at 9:15 pm There are some different cases here: 1. Bug is invalid. You are opening an invalid bug by mistake or error when doing testing like wrong pre-condition, wrong configuration on environment or other kind of mistake. In this case, accept it and put comment this is your mistake and inform developer dont look at it anymore. 2. Bug is valid. In this case you need to have an acceptable reason from the person who rejects that bug. As for the reason. If there is no reason given, re-open that bug, put your comment, give the expected result and actual result, consult BA if needed to show that is a valid bug. 3. Bug is valid but out of scope of that release. In this case, put proper comment and close it but take note and move it to next release, sprint… I also have many cases, my bug was getting rejected, but it depends on the case we have a different action. Happy to share to all of you 🙂 Leave a Reply Cancel replyYour email address will not be published.Comment Name Email Website Save my name, email, and website in this browser for the next time I comment.