If tester is asked to test a Build within short period, After Testing, How will you (Tester) react if the Developers says that you have missed the bugs?
Total Answers and Comments: 4
Last Update: September 23, 2009 Asked by: mathan_vel
Every Build Note comes with the List of defects are going to deployed Testing Team should test all the defects and change/new functionality listed on that build manifesto. Ideally a Test Manger should do a impact and effort analysis before approving the build. Test Manger/Sr Test Analyst should analyze the functional and business changes in the application/product to choose the test cases to cover all the defects change/new requests on that build. This will assure the complete test. If a developer says "you Missed Bugs" in this build Then Tester need to verify the below before answering
1. Check the bugs or defects developer mentioned are there in the build manifesto
2. Check the bugs or defects developer mentioned are covered in the test cases planned for this build Test Analyst can say its development issue if point one is False or it s a Test team issue if point 2 is False.
These situations raise due to miscommunication between Dev Test and deployment Teams.
First thing as a Senior Test Analyst Prepare the detailed analysis report consulting both Test team (self) and dev team stating the amount of Effort required to fix each defect in terms of Business/Functional and System changes required to fix these defects. If both the team have bandwidth to complete Development and Testing on the time frame specified by the client the go head and complete it If you don t have bandwidth to complete all the defects then try to complete all 5 high severity defects first and if time permits some of low severity and make the client understand the difficulties and explain that what are all defects can be pushed in this build on time and what defects can be pushed in next build and go ahead with the work as planned. In short you should do detailed analysis of the defects and consult the effort required for Dev team and have a internal plan first and let the client know your outcome.
This type situation will definitely occured in any of the company and every one must face this as testing is the final formality so altimately pressure is on testers only.
But while closing the testing make a note of what was the test coverage in the testing this is a best solution even who ever shouted on us because that is the only proof for us so dont hesitate to add the test coverage.
Testers need to finalize and communicate the scope of testing as well as depth of testing clearly before testing the build under pressure. This should be communicated both to developers as well as manager.
After doing this if we testers missed any bug we need to see whether it is due to -the area / depth is not under scope -due to mistake of our test strategy
If formal is the case we can defend us. If later is the case we need to accept developer's accusal.
