Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
>>First will discuss with the developer the reason he is not accepting the defect.
>> Attach all the evidences like screenshots and step by step procedure to reproduce the defect.
>>Still your developer is not convinced, capture / record your findings.
>>If still he/she is not convinced please escalate your higher level.
Elaborate the defect and attach the screenshot if it is UI related. If the requirement is clear enough to showcase the defect then direct conversation with developer would be the right choice.
If developer is still not accepting it as defect, then involve the techinical architect who worked on the userstory.
Always fight for the defects in a positive manner by providing ample amount of evidence like through requirement documents to prove your defect. Be positive not all the defects are accepted.
Provide all the relevant artifacts such as screenshots, Video recording, environment details etc while logging a defect which can further helpful.
we do one round of Triage meeting.
Sometimes the defect is rejected because developer tell that this is not as per requirement,this seems to be an case of missing requirement in this case if your defect is genuine and is related to the business functionality then it may be accepted, may be rejected if it does't make sense.This is decided by business or BA.
Will produce enough proof for the defect like reproduce test results and screen shot of that defect
I will try to convince him about the bug, by reproducing it to the developement machiene or i will make a video of the testing scenario , from which the bug was produced
Based on the priority of the fix and impact of it, the CCB will decide and give the devoloper enough time to fix it.
As a tester point of view we can give enough evidence regarding that defects .for example we can take screen shot of that defects and attach to bug reporting sheet.
After evaluating against the requirements, if it is a critical bug, then yes it needs to be fixed and if the developer doesn't accept escalate to project manager. If the bug is non critical/ occurs under rare circumstances, then this falls under risk management, categorizing the bug as probably low risk and then managing it and evaluating based on number of occurences when it will need a fix.
First of all bugs should be logged with proper reproducible steps, screen shots etc…If developer rejects the bug, then first thing to look out for is the reason or justification on why the bug was rejected. If the justification is valid I would agree for the rejection. However, if the reason is not justified then, I will go back and try to reproduce the bug with the steps I had provided earlier. If it is still reproducible, I shall reopen the bug with valid comments and will provide additional information if I found any. Then I would go back to the developer asking for justification on the rejection. At this point I shall include BA and technical lead also is to take confirmation on the defects
