A bug is raised by the tester and it was told that it is not...

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

[ Home | FAQ-Related Q&As | General Q&As | Answered Questions ]

Question by chunduri
Submitted on 12/17/2003
Related FAQ: comp.software.testing Frequently Asked Questions (FAQ)
Rating:	Rate this question:
A bug is raised by the tester and it was told that it is not a bug by the programmer. What to do?

Answer by cccc
Submitted on 1/14/2004
Rating:	Rate this answer:
these programmers do not accept it when a tester finds a bug try to discuss with the manager then proceed

Answer by Sridhar
Submitted on 2/1/2004
Rating:	Rate this answer:
Testers are not supposed to discuss with the programmers.go ahead and raise a tracker if it is consistent.

Answer by Gomes
Submitted on 3/15/2004
Rating:	Rate this answer:
Its a tester who has to say if that is a bug..a programmer would never accept it a bug though in all probability he would sneakily fix it. The tester needs to take a call. If there is a disagreement by the programmer after posting the bug, then he should discuss it through the manager

Answer by jayabugs
Submitted on 4/13/2004
Rating:	Rate this answer:
Let the programmer see how the bug would affect the users. Convince him with realtime situation. Programmers would own the bug if they are convinced. It is the responsibility of the testers to convince them

Answer by Suhas Nagane
Submitted on 4/21/2004
Rating:	Rate this answer:
It comes under Bug cycle open-Tester Reject-Developer close-Tester Tester have to close the bug and keep the proof that it has been rejected by developer that's why closed.

Answer by ashok
Submitted on 4/26/2004
Rating:	Rate this answer:
Never i heard developer accepts a bug. Make supporting douments or proof of bug like screen shots. Take this to meeting with baseline documents. politily say them they cannt quit ,they should solve the bug as per these documents

Answer by sangi
Submitted on 3/4/2005
Rating: Not yet rated	Rate this answer:
try to convince the devloper by explaining the consequences of defect if not fixed. If he still disagrees ,discuss with QA Manager

Answer by Balaji
Submitted on 12/13/2006
Rating: Not yet rated	Rate this answer:
Produce supporting documents or proof of bug like screen shots. And tell him the real time situation how it affects the end users.

Your name or nickname:
If you'd like to create a new account or access your existing account, put in your password here:
Your answer: