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 ?    9 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 / 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 / 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 ?    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 the need of black box testing after completing white box tesing?

2 Answers   Cognizant,


what is the difference between test plan and test strategy?

2 Answers  


expalin integration tsting who will perform ths type of testing at what time will do

2 Answers   Aspire,


only one tester & one developer ,the product is released to be today night.if you found a critical bug then wat u do

6 Answers   IBM,


What is your framework of current project

2 Answers   Cap Gemini,


what is the steps for preparing scenario ?

3 Answers  


how can u do regression testing tell me procedure?

14 Answers   TCS,


what is difference between Sanity testing and Smoke testing?

15 Answers   IBM,


wirte the test cases for triangle

3 Answers   Intel, iGate, Oracle, Accenture, DGF,


on what basis low,medium,high,critical will be assigned to a bug.give m examples

2 Answers  


Which is the most important phase in SDLC

7 Answers   TCS,


How do you carry usability testing?

5 Answers   CTS, GrapeCity, Intel, ADITI,




Categories