IF the developer rejects the bug then I will anylise that
bug when he rejected is resionable the I will keep the
stauts of the bug as rejected and If it is not resionable
then will have a meetting and I will explane how i found
that bug to him
In such cases first we once again check whether it is
reproducable or no if it is reproducable we are goint to
explain to developer in detail if still he is not accepting
the bug then we will have a small meeting and we will
discuess in that and solve the situvation.
Normally Developer Rejects the bug in two ways 1. Tester's
Error 2.As per design
1.Tester's Error :This status is given by the Developer
when the tester dont have the functional knowledge and kept
the bug.In such case we will verify the functionality and
it is as per the requirements we will conduct the meeting
and verify that.
2.As per Design:when the requirements are changed and they
are not updated to the testers, in such case he test the
module according to the previous requirements and
encountered with the bug in such case the status is As per
design
Thanks bala....for your valuable suggestion,i will go for it
in future because i also had same problem with our develoffer,
so i definitely try this....thanks again for you
If dev rejects the bug, tester will explain all the steps
by reproducing the bug. If still Dev is not accepting the
bug, then we will have a meeting where we will check
whether this is as per the functionality, requirement. If
yes, then Dev has to accept as a bug.
If not, then we will check how much this bug affects on the
Application, does it breaks the functionality or affects on
other pages. If it doesn't affect much more, then tester
will mark as "Cancel By Reporter".
If the developer rejects that its not a bug then you have
options like you go through design documents.
1)Show that this requirement comes under this module.
So fix the bug & revert other wise it will go to next level.
2)As per
in employe details form, we are entering First name as
manjunath and Last name as sastry. but when we retriving
the data in reports form, it shows as first name as sastry
and last name as manjunath. here bug may be in employee
details form or reports form. how you check in manual?
1. Test granularity refers to:
a. Any way of determining the expected result for a
test case.
b. A quality improvement idea common in software
development.
c. The fineness or coarseness of a test’s focus.
d. The impact of a bug on the system under
Suppose product is to be delivered on urgent basis.There is
no time to test on all OS and Browseres.We have time to
execute atlest in one combination of OS and browser.Which
one do you prefer and why?