When a bug posted by QA is rejected by Dev and Dev says is
not a bug. How to convince Dev that it is a valid bug?

Answers were Sorted based on User's Feedback



When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / amit verma

Try to Reproduce the same bug by following the steps that v
used earlier.If it occurs again then take a screen shot(if
its reqr.) and send them back with Steps to Reproduce along
with att. screens shot.

If again he refuse to accept it as a bug then discuss it
with ur PM or send him a mail along with screen shot and
steps . But make sure that should be a bug o/w u r in prob.

That Really Works :-)

Amit Verma

Is This Answer Correct ?    7 Yes 0 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / amin

Give him reference of requirement specification or FR
document used to write that test cases and the expected
result. The developer and tester should have same
understanding about the requirement.

Is This Answer Correct ?    8 Yes 3 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / babu

Give him reference of requirement specification or FR
document used to write that test cases and the expected
result. The developer and tester should have same
understanding about the requirement.

Must attach the LOG file with the bug,

Is This Answer Correct ?    5 Yes 1 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / siri

firstly i will give him reference of requirement
specification and check we both are having the same requirement.
and if we both have the same requirement then
i will arrange a in person meeting with the dev.; explain
the defect; show the screen shots were the defect exactly
was found and also explain the test pattern i.e, enter and
exit points.

Is This Answer Correct ?    2 Yes 0 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / devina

1) Verify the requirements.
2) Reproduce the same defect again on the same environment.
3) Send the screen shot to the dev team.
4) Finally if Dev team still rejects it, hold a meeting with
the manager/ requirement manager to come on the same page.

Is This Answer Correct ?    2 Yes 0 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / swapna

reproduce the same bug and send him the steps to reproduce
it.

Is This Answer Correct ?    7 Yes 7 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / priti chandel

Suppose bug is related with functionality then will explain
to ref him requirement docs or if it is related with UI
then will show him wats the risk of that bug by user point
of view

Is This Answer Correct ?    3 Yes 3 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / naveen

Two ways which you can convience developer
1>Providing steps to reproduce the issue
2>Providing the function doc

If any req gap happens like ;
Some times requirement clarification/conversation may
happen b/t Tester and BA (Probably developers will also
include in those mails)so providing those mails to dev team
and to confirms a defect.
But these cases should not be in a last minute

Is This Answer Correct ?    0 Yes 0 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / asha

if developer fails to acccept it as a bug, tell him to test
in the client machine whether it is working fine or not.

it should work in the client machine or else he should
accept a bug and resolve the bug.

Is This Answer Correct ?    0 Yes 0 No

When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it ..

Answer / rajesht

case1: Requirement exists for the reported bug

If Dev says it is an invalid issue, then the tester need to
give him reference no of the requirement.

case2: Requirement not exists for the reported bug.

Sometimes we may encounter some issues while testing which
do not have requirements. In that case we still have right
to submit a bug with issue category as requirements. If the
developer says that it is an invalid issue then we have to
move that bug to business analyst asking his comments. Once
we receive the comments from business analyst we will move
back the bug to developers court.

Is This Answer Correct ?    1 Yes 1 No

Post New Answer

More Manual Testing Interview Questions

what is definition of functional and security testing

6 Answers   HCL,


how would one evaluate test effectiveness? if at all it is possible what type of metrics will be used to calculate effectiveness.

3 Answers  


Hi Friends, I have recently completed Testing course and planning to apply for jobs, I am Planning to put Banking Project in my resume but b4 that I need your help guys According to my knowledge in the banking project basically it contains 3 modules say 1. Banker 2. Admin 3. Customer Could you please explain me in terms of interview like how to explain each module and what exactly each module does and what type of testings we can do on banking project. Any help would be appreciated Thanks in advance Swapna

1 Answers  


what type of questions they asked in symphony company for manual testing?

1 Answers   Symphony, Symphony Teleca,


What a manual tester should know about web servers?what he tests in servers?

3 Answers   Mind Tree,






Please answer it:Your achivements as an manual tester? Dont answer :Ive found bugs? Bcoz it is your job.

0 Answers   JPMorgan Chase,


what is the difference between Test strategy and test plan?

25 Answers   EDS, IBM,


There are 2 clients for a server and that clients can access the data from the server only for 10 days. so how will you test this scenario manually? Can u pls help me?..

4 Answers   eMids, TCS,


why we develop Test plan for a project ?

4 Answers   Wipro,


Which are the standards for software test plans?

0 Answers  


There are 20 resources out of which 12 are manual testers, 5 automation testers and 3 performance testers. There are a bunch of projects to be tested in the organisation, the projects belong to various technologies, say 20% of projects in Java, 20% of projects in SAP, 30% of projects in .NET, 30% of projects in C# What is your approach as Test Manager in testing.

0 Answers  


difference between test strategy,test plan and test methodology. which will create first and who will create those and is there anyone optional in that

2 Answers   Pragma,


Categories