You say it is a bug but developer say it is not a bug then
what will you do?
Answers were Sorted based on User's Feedback
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
| Is This Answer Correct ? | 17 Yes | 3 No |
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
| Is This Answer Correct ? | 10 Yes | 2 No |
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.
| Is This Answer Correct ? | 1 Yes | 1 No |
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / phani
just simply attach a screen shot to the related bug in order
to make sure that it is a bug
| Is This Answer Correct ? | 0 Yes | 3 No |
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
| Is This Answer Correct ? | 0 Yes | 5 No |
What is checkpoints for qtp?
how you will do cookie testing using QTP?
Can I compare two DataBases using QTP ?
Write a user defined function to count the no. of buttons existed in a webpage ? i dont want to use descriptive.create ()
how we implement share object repository in QTP 9.0 without using quality Centre , Explaine in brief
What are the two types of repositories available, explain them?
Explain different type of event trigger option.
what is mercury.clipboard in qtp.where we can get this in qtp tool i.e tabs
While spliting an action in QTP 10.0 getting an error : "This Line is a part of Script Block.You cannot split the action on this line." how to re-solve this and split the script into actions?
What’s the QTP testing process?
for example one window is there, the window contains how many edit box's i want script? i know the script but that is not exact answer.... The script is like this .......... set a=description.creation() a("Native class")="WinEdit" b=window("Flight Reservation").childobject(a).count msgbox b
How to compare 2 excel files using QTP? How to compare 2 PDF files using QTP?