Does we make documentation for all defects?
Answers were Sorted based on User's Feedback
Yes we make documentation of all the defects irrespective
of the Resolution.
Bugs that are accepted should be dosumented no doubt.
But there might be some bugs that are marked as Won't fix
which means that a problem exists but developers cannot fix
it. This could be extremely helpful in preparing the exit
report.
Also the bugs markes as Duplicate/Invalid... should be
recorded because with the help of these bugs severeal
metrics are prepared that can be used by the management to
evaluate testing process and testers as well.
Regards,
Saurabh garg
| Is This Answer Correct ? | 0 Yes | 0 No |
The above answer is correct but you dont need to prepare a
document for all the bugs u have raised if you are using
some test management tool like Quality Center or Test
Director. From these tools u can directly pull out the
reports which will give all the detailed listing of ur bugs.
| Is This Answer Correct ? | 0 Yes | 0 No |
What is lessons learnt document?Explain.
Phases of Software Testing Life Cycle?
what is means by feature to be tested in test plan
What do you think the role of test-group manager should be
What metrics will be collected during the Testing i.e from requirement Phase to Maintainance Phase
Does alpha testing follow beta testing or beta testing follow alpha testing and why?
State a generalized process for load test? Or explain how you did it previously.
what is the diff. between Test Case and Test Secenario ? give me one example ?
difference between regression testing and re testing?
Which is the better way to explain tipical bug life cycle?
For your testing you need 15 open accounts. A production data cut has been given to you. What will you do?
If there are so many bugs open and still the client want the s/w what will you do?