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

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.

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,

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.

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.

Answer / swapna

reproduce the same bug and send him the steps to reproduce
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

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

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.

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.

What r the different testing techniques other than BVA and EQP?

6 Answers   HCL,

What are two types of Metrics ?

1 Answers  

What are the techniques you follow to write test cases?

8 Answers   AZTEC,

Explain the sub-genres of performance testing?

0 Answers  

7. Would you return to this Web site on your own in the future? Why/why not?

0 Answers  

How to conduct Regression Testing Manually?

9 Answers   FIC,

What are the advantages of manual testing other than "Low cost", "Where automation fails".......?

6 Answers   Satyam,

what is traceability matricks

7 Answers   Synergy,

What is XML Testing? Do we have any tools to test the XML? Please let me know.

0 Answers  

How do we develop test scripts for manual testing?Can anyone explain me with an example . Thanks, Prasanna

8 Answers  

how u can do integration testing and what r the approaches u need to follow?

5 Answers   MBT,

What is the template used for informing clients regarding known issues when u near to release?

2 Answers