Thursday, July 15, 2010

Test Strategy (Summary )

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.

In the test strategy is described how the product risks of the stakeholders are mitigated in the test levels, which test types are performed in the test levels, and which entry and exit criteria apply.
The test strategy is created based on development design documents. The system design document is the main one used and occasionally, the conceptual design document can be referred to. The design documents describe the functionalities of the software to be enabled in the upcoming release. For every set of development design, a corresponding test strategy should be created to test the new feature sets.

What to do?
- Identify the Scope of Testing
- Identify Types of Testing to be carried out
- Identify the Testing Tasks
- Identify whether any Testing Tools are required
- Identify whether any Frameworks need to be used
- Identify the Metrics to be collected
- Identify the Deliverables, Dashboard and Reports
- Identify the Factors affecting Quality of Deliverables
- Identify when to complete Testing

How to do?
- Identify the Test Requirements
- Define Target Test Environments
- Identify the Testing Activities to Complete Tasks
- Identify the ways to conduct the Testing Activities
- Identify the Test Cases for the Testing Activities
- Identify Resources for the Testing Activities
- Identify the ways to meet the deliverables
- Identify the ways to improve Quality

For detail analysis click below link

No comments: