You reported a Bug.The developers are saying that it's not a
Bug even though it is..How you are going to prove that it's
a Bug?




Answers were Sorted based on User's Feedback



Answer / kannan.r

Tester should always keep a screenshot for proof in such
situations..

Is This Answer Correct ?    10 Yes 0 No

Answer / farzana

Ultimately the ball will remain in tester's court as he
should be able to attach screenshot along with detail
analysis of the requirement and how it can be reproduced.
Even after that dev is unable to reproduce in his
environment, then lead needs to show the bug in your own
environment. it could be possible that the bug is surfacing
in your machine because of wrong version of internet
explorer or other config issues.

Is This Answer Correct ?    4 Yes 0 No

Answer / raj

attatch the snapshot with bug

Is This Answer Correct ?    3 Yes 0 No




Answer / chandra shekhar bhattarai

Providing him a snapshot with bug.
providing him the test case ID.
providing him the user requirement specifications.
and a copy of actual and expected results of the test case.

Is This Answer Correct ?    3 Yes 0 No

Answer / arif

We will a triage meeting between a tester, test lead and
developer and development test lead with neccesasry
documents(SRS) and we finalize the bug.

Is This Answer Correct ?    2 Yes 0 No

Answer / raghava

firstly u show the snap shot of bug
and let him to see the brs and srs doc
what is expected and actual


Is This Answer Correct ?    2 Yes 0 No

Answer / dhesi

not exactly kannan,
The screen shot will be an secondary thing.. when the
developer says that it is not a bug we suppose to send the
'requirement ID', i guess its enough to identify where the
bug is if not then we can attach the 'screen shots' as the
proof of the bug.

regards,
Dhesi.

Is This Answer Correct ?    2 Yes 0 No

Answer / chandra sekhar

Here the problem is about confusion...At this time tester
should have idea about user requirements and should be able
to explain the bug analysis to the team lead/project
manager based on the requirements.

**A clear discussion will leads to conculsion.

** arguments leads to further problem's.

Is This Answer Correct ?    1 Yes 0 No

Answer / sandeep

If my bug is currect then i will show user requierment specification (URS) doccument, then i can prove my bug is currect. Because every one should follow the urs doccument.

Is This Answer Correct ?    1 Yes 0 No

Answer / mercurytsl

Hi Arif,
suppose the bug is not reproducing..

Is This Answer Correct ?    0 Yes 0 No

Post New Answer



More Manual Testing Interview Questions

What is Alpha and beta testing and What is the diffrence between Alpha and beta testing ?

4 Answers  


Write the 10 high test cases for making video call/face time?? Write the test cases for credit card accessing the money transfer?? Write the test cases for file transfer from one user to other from Google Drive/drop box?

0 Answers   PanTerra,


Being an Manual tester, what will be the role or activity in test plan ?

0 Answers  


What is the difference between Test Matrix and Test case

1 Answers  


What particiption a manual tester can do in documentation? Are there any tools available for only documentation?

4 Answers   Logica CMG,


Do u writing a separate testcase for Regression Testing? If it is Yes, Explain How to write the Testcase?

4 Answers  


1. What types of documents would you need for QA, QC, and Software Testing?

1 Answers  


Please give me any example of High severity and Low priority type of bug ?

7 Answers   TCS,


What is the Desktop Testing?

1 Answers  


How u can do regration testing/retesting testing, after assign bug to devloper, how to manage the test cycle number and built number, plz tell me....

6 Answers   SAS, Bosch,


what is ment by Requirement tracebility matrix?what is the use of it? what is the template of rtm?

1 Answers   Wipro, Suzuki,


what is equivalence class partition?

8 Answers   Steria,




Categories