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

How should testers write the test cases without Specifications

3 Answers   Patni,


We can check many things in one test case, then Is it necessary to write separate test case for checking each functionality? Example : For Login Window --> Test Case is---> 1) Enter valid user id & password --> For this expected result --> 1) User should login. My question --> while executing above valid test case, we can expect more than one result such as "Visibility of password should be as ****" So Should I have to write separate test case for "Visibility of Password" OR Not? Please guide me properly.

5 Answers  


What is latent bug? the people who is know about this plz kindly give the ans.

1 Answers  


What types of testing will come under functionality testing and non functionality testing?Security testing is consider as functionality testing or non functionality?why its so?

10 Answers  


how u do database testing

4 Answers   Polaris,






Please let us know With out GUI features how to test the application

2 Answers   AppLabs,


How can a LOG for testcases be maitained which can give information about a TestCase that is it new one or has been occured in previous versions of the software.

0 Answers  


*) Internal review defect gets detected… 1) During peer review. 2) By the own stuff member onsite/offshore. 3) During Informal review process. 4) None of these 5) All of these

0 Answers  


How to check security of any browsers???

1 Answers   IBM,


Explain Alpha Testing and Beta Testing

5 Answers   Virtusa,


What is the difference between Functional requirement and business requirements?

2 Answers   Covansys,


what is the diff between webserver app & client server application...

2 Answers   3i Infotech, HCL, vSplash,


Categories