أنشئ حسابًا أو سجّل الدخول للانضمام إلى مجتمعك المهني.
Check the project specification to see if it is in fact a defect.
Prove to the developer why this is a bug and how it is supposed to work.
If the developer still does not accept that this is a bug, you should speak to someone higher up like the team leader or project manager to ask for their opinion on resolving the issue.
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.
1) You have to prove your point by using documented resources, such emails, bussiness doucemnt, system docuemnt, ..
2) if you don't have somthing documented, you have to ask the team leader
3) if the team leader is not aprove that this issue is BUG, you have to ask the project manger to approve if this issue is bug or not
4) if you dont have a project manger, so any upper mangment level should approve or reject the bug
Check the project Requirements and validate the defect against them , then validate the defect
As test Engineer we provided screen shot of that bug and send it to Developer if again the problem araise we have to check the system enviroinment of both the tester and developer system.....
1) Attach all the evidences like screenshots and step by step procedure to reproduct the defect.
2) Point out the SRS and BRS details where they need to refer.
3) Still your developer is not convinced, capture / record your findings using a special tools like camtesia (video recording tool)
4) If still he/she is not convinced please escalte your higher level.