Answer / dan

The requirements documentation is the source of truth. If
the application is not behaving as specified in the
requirements then it is a defect. If a requirements change
is necessary then the only the Business can approve this
change, not the developers or the testers

Answer / rafi

If thedeveloper says it is not a bug then we have to
1) take the screen shot and explain about the bug.
2) take the remote desktop and explain about the bug.

If still the developer says it's not a bug then
take the SRS document and explain the requirement.

if any mistakes correct me.
Thank you

Answer / shalini nigam

Wen you say its a bug but developer says its not a bug,
there could be a three reason->
1> Misunderstanding of feature as a bug
2> Still referring the old requirement
3> Extra Implementation

In order to Reproduce the bug to developer, you should give
the detailed information about the defect with navigation steps.

Answer / padmas

As a whole of the product if there is a bug and developer say it is not a bug, then will explain how it is a bug. Sometimes there will be team of developers where from units get developed. If there is a bug in one unit and developer says it is not a bug, may be the unit is not developed by him/her. While integrating two units if the stub work between these two units possible bug exists in stub than the units, though the working without any bug. will try to fix it than arguing about a bug if exists.

Answer / rohini

show the Test Report Or SRS to the developer

Answer / phani

just simply attach a screen shot to the related bug in order
to make sure that it is a bug

Answer / padmas

From the question, one can understand that the stage of the
testing is Unit
testing,because developer is involved.
in this scenario,Code reviews can be conducted.
Generally unit testing will be done by developers.Because
bugs found at unit
level,are raised by the developers.IF developer says it is
not a bug, then it
will be considered as issue in the code review.
Whatever raised during the testing will be considered as
defects later on, in
which developer will not be involved.
During the integration testing,if the units are reviewed and
unit tested only
then integrated if it does not create new issues or defects.
if developer says it is not a bug, then tester will say it
is a defect in later
phases of testing

What do you mean by iteration?

0 Answers  

what ar the challenges do we face while testing webbased applications using the automation tool qtp or any?

4 Answers   TCS,

how you update scripts in qtp?

1 Answers  

where did you automate in your project?(please tell me example senarios)

2 Answers  

i this is balaji from chennai i have 4 yrs exp in testing and my qualification is bsc computers i completed in correspondace in which companiies accept the correspondace plz let me know

1 Answers   Accenture,

what are the cases in which we use XML and accessibility check points.

2 Answers  

What is test object?

0 Answers  

how we implement share object repository in QTP 9.0 without using quality Centre , Explaine in brief

0 Answers   HCL,

Explain how qtp identifies objects?

0 Answers  

what are recovery management techiniques?

1 Answers  

write a script for allinterview-submit Question first we've to select Choose Category,second select Sub- Category(Which is comes in to runtime)third select Question Type.for that give some descriptive and vb script

0 Answers  

If we are record a same web page for 2 times.1st time it is showing 6 objects in the Object Repository and for the 2nd time it is showing like 7 Objects in the Object Repository why it is happening

4 Answers   Kanbay,