The document discusses different testing strategies that can be used for software development projects. It describes preventive and reactive approaches, with preventive being preferred when possible. Preventive approaches involve testers early in the development cycle through activities like design reviews and test specification. The document also contrasts analytical strategies, which are based on data analysis, and heuristic strategies, which rely more on experience. Specific strategies mentioned include model-based testing, statistical testing, risk-based testing, and checklist-based approaches. The goal of the testing strategy is to optimize the relationship between testing costs and defects.

1. Testing Strategies Presented by:- Satish S. Bhutawale (09) Joyson G. Fernandes (13) Guided by:- Prof. Praveen Gupta

2. Concept:- A test strategy is an outline that describes the testing portion of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process. This includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing environment.

3. A test Strategy defines the Project’s testing objectives and the means to achieve them. The test strategy therefore determines testing effort and cost. The goal is to choose a test approach that optimizes the relation between cost of testing and cost of defects.

5. The use of V-model with emphasis on design reviews, will contribute a lot to prevent defects.

7. One very successful strategy in such a situation is called as “exploratory testing”.

8. This is a heuristic approach in which the tester “explores” the test object and the test design, with execution and evaluation occurring simultaneously.

9. Preventive approach should be chosen whenever possible. The analysis of cost clearly shows that:-The testing process should start as early as possible in the project. Testing should continuously accompany all phases of the project.

12. Reasons might be that no data are available, mathematical modeling is too complicated, or because know-how is missing.

17. Uses information on project and product risks and directs testing to areas of greatest risk.

18. Process-or Standard Compliant Approaches:-

19. Use rules, recommendation, standards as a “cook book”.

20. Reuse-Oriented Approaches:-

22. Use failure and defects lists from earlier test cycles, lists of potential defects or risks, or prioritized quality criteria and other less formal methods.

23. Expert-Oriented Approaches:-