If the developer rejects that its not abug means then whats
the next step we follow?
- 8 Answers
- 7456 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / anita
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".
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / sssss
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
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / srinu
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
| Is This Answer Correct ? | 0 Yes | 0 No |
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / rinu
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
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / sushant sinha
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
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / thala
Simple....you do one thing...shutdown your system and go home.
| Is This Answer Correct ? | 0 Yes | 2 No |
Answer / bala
then you directly go to that develoffer and ask him why??
and give him one dichhee...onwards he will not dare to
rejects your bug.
| Is This Answer Correct ? | 1 Yes | 3 No |
List the considerations in developing testing methodology
4. A software error can be described as: a. A description of the relationship between two or more variables or set members in which the value of one does not influence the values of others. b. Any ill-advised, substandard, or temporary fix applied to an urgent problem in the (often misguided) belief that doing so will keep a project moving forward. c. The process in which developers determine the root cause of a bug and identify possible fixes. d. A mismatch between the program and its specification. 5. Select a reason that does not agree with the fact that complete testing is impossible: a. The domain of possible inputs is too large to test. b. Limited financial resources. c. There are too many possible paths through the program to test. d. The user interface issues (and thus the design issues) are too complex to completely test.
can any one tell me what is the difference between Integration testing and End-End testing? plz dont tell me Integration is whitebox testing and done by developers, where as End-End is blockbox testing and done by testers.
Very Important Note for all the Testers!!! As the S/w Boom is getting considerably decreased...
when developer will found bug they will store that bug in Dts 1- yes 2 - sometimes 3 - No 4 - none of these
When should you begin test planning?
Mention critical bugs in hospital management system i.e. project has 4 modules like appoint, patient chart, reports, pharmacy
I faced following questions in Polaris Interview. 1. Tell me about u r current organization 2. what is Black box testing? 3. what is white box testing? 4. What is Functional Testing? 5. What is difference between Black box & functional ? 6. what is test plan? 7. what is test strategy? 8. what is difference between Test plan & test strategy? 9. What is smoke testing ? 10 what is sanity testing? 11. who will perform smoke testing? 12. Explain about Agile process? 13. How much you know about QTP? ( I mentioned in my resume as Exposure on QTP) 14. Explain about u r current project? 15. What is the Requirement Traceability Matrix? 16. Can u draw the template for Requirement Traceability Matrix? 17. What is Ad-hoc Testing? 18. What is difference between ReTesting and Regression Testing. 19. Can u explain about Bug life cycle? 20. How can u make sure whether all requirements are covered or not? 21. Can u explain biggest complexity in current project? 22. what is difference between bug severity and priority? 23. Which bug tracking tool is u r using? 24. can u give one example for High severity and low priority bug? 25. can u give one example for High priority and low severity bug? 26. What is security Testing?
difference between stress testing and loadtesting
how to reduce bugs in e-learning projects? for reducing bugs which type of SDLC we have to use
what are the general problems in web testing?
How is testing affected by object-oriented designs?
Automation Testing 
