Testing Completion Criteria

Testing Completion Criteria includes following things -
1. 100% Statement coverage,
2. 100% Requirement coverage,
3. All screens / dialogue boxes / error messages seen,
4. 100% of test cases have been run,
5. 100% of high severity fault fixed,
6. 80% of low and medium severity faults fixed,
7. Maximum of 50 known faults remain,
8. Maximum of 10 high severity faults predicted,
9. Time has run out,
10. Testing budget is used up.

Difference between Test Strategy and Test Plan

Test Strategy : It is a company level document and developed by QA category people like QA and PM.This document defines "Testing Approach" to achieve testing objective. Test strategy is the freezed part of BRS from which we get Test Policy and Test Strategy.
Test Plan : Test plan is the freezed document developed from SRS, FS, UC.After completion of testing team formation and risk analysis, Test Lead is preparing test plan document in term of what to test, how to test, who to test, and when to test. There is one Master Test Plan consists of reviewed Project Test Plan and Phase Test Plan. so there is general talk about Project Test Plan.

Test Strategy : Components in the Test Strategy are as follows:
Scope and objective,Business issues,Roles and responsibilities,Communication and status reporting,Test deliverability,Test approach,Test automation and tools,Testing measurements and metrices,Risks and mitigation,Defect reporting and tracking,Change and configuration management,Training plan.
Test Plan : Components in the Test Strategy are as follows:
Test Plan id,Introduction,Test items,Features to be tested,Features not to be tested,Approach,Testing tasks,Suspension criteria,Features pass or fail criteria,Test environment (Entry criteria, Exit criteria),Test delivarables,Staff and training needs,Responsibilities,Schedule,Risk and mitigation,Approach.

Test Strategy

The purpose of a test strategy is to clarify the major tasks and challenges of the test project.

Creating a Test Strategy :
The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.

Defining Test Strategy :
A solid testing strategy provides the framework necessary to implement your testing methodology. A separate strategy should be developed for each system being developed taking into account the development methodology being used and the specific application architecture.
The heart of any testing strategy is the master testing strategy document. It aggregates all the information from the requirements, system design and acceptance criteria into a detailed plan for testing. A detailed master strategy should cover the following:

1. Project Scope
2. Test Objectives
3. Features and Functions to be Tested
4. Testing Approach
5. Testing Process and Procedures
6. Test Compliance
7. Testing Tools
8. Defect Resolution
9. Roles and Responsibilities
10. Process Improvement
11. Deliverables
12. Schedule
13. Environmental Needs
14. Resource Management
15. Risk and Contingencies
16. Approvals and Workflow

What to include in the Testing Strategy

1. Project Overview
2. Business Risks
3. Testing Milestones
4. Testing Approach
5. Testing Environment