You are on page 1of 2

1. Identify all the platforms on which application will be run. 2.

Improve requirements management process – business & functional requirements should be well documented. Involve testing team in requirement gathering phase. 3. Create a document / list of all possible scenarios before writing test cases. Include it into test planning. 4. Measure testing effort on periodical basis – New Bug Rate, Effort Variance, Schedule Variance, Test Case Effectiveness, Residual defect density etc. 5. Keep developers away from test environments. 6. Post mortem meetings must be planned after every release. Both testing & development teams should participate in these meetings. 7. Keep track of bug fixing time taken by development team. Keep informed about the time remaining for regression testing to relevant stack holders. Tracking of this point by relevant stack holders is very critical as it may result in low quality releases. 1. Try to understand the logic behind the screen and try to break that logic. Understand the internal workings of code from developers during lunch time or tea breaks. 2. Analyse test results thoroughly. Try to identify root cause from functional perspective. 3. Break the application into smaller functional modules. 4. First write test cases for valid conditions, then cover invalid conditions. 5. While writing test cases, refer design documents as well. 6. As soon as you complete the test case writing, share test case with development team. It could result in time saving. 7. During test case writing phase, group test cases using impact analysis. It will help in effective regression testing in less time. 8. If you are new tester for a old development team, have a look on old bug reports of modules / project where development worked previously. Generally developers, repeat similar mistakes. 9. Test the application for both implicit as well as explicit requirements. 10. Never communicate bugs verbally. For any critical / show stopper bugs, have an immediate discussion & then document via mail and share it to relevant stack holders. Below is a sample Test Readiness Review Checklist: 2. Are all problems / defects translated into Defect Reports ? 3. Are all the Defect Reports satisfactorily resolved ? 4. Is the log of the tests conducted available? 13. Is the user manual ready? 14. Is the installation procedure documented ? 15. Are all the product requirements implemented? 16. Is the list of known problems available? Is there any "workaround" procedure for the known bugs ? 17. Are test environment needs met for Hardware, code, procedures, scripts, test tools etc.?

List of exceptions in test software and test procedures and their work around if any? 19. is the interface between quality assurance and the development organization. which is handled by the test manager. Is the source code freezed for testing? There are two areas of responsibility in testing: 1. Is any standard methodology / tool used and is appropriate to the type of the project? 22.18. Are the designers educated on Test reporting tool? 21. Testing the application. The overall testing processes. which is the responsibility of the test team 2. Responsibilities include: • Setting up the test objectives • Defining test resources • Creating test procedures • Developing and maintaining the test plan • Designing test cases • Test case development • Providing test status • Writing reports • Defining the roles of the team members • Managing the test resources • Defining standards and procedures • Ensuring quality of the test process • Maintaining test statistics and metrics The test team must be a set of team players and have the following responsibilities: • Execute test cases according to the plan • Evaluate the test results • Report errors • Design and execute automated testing tool scripts • Recommend application improvements • Record defects . The test manager directs one or more testers. and manages the overall testing effort. Is the criteria for regression testing defined? Has the regression testing been done accordingly? 23. Is the test reporting tool is available? 20. Is the source code available from the client for performing regression testing complete in all respects? 24.