Testing Approach and Strategy
December 13, 2010Testing Approach and strategy helps you prepare the list of testing requirements and the testing strategy for supporting the new corporate procurement and application module.
Included are descriptions of the target audience, delivery method, and objectives. In addition, the testing approach and strategy identify:
The high level objectives and tasks of each testing phase
The human and physical resources required to support testing
The assumptions, dependencies and risks associated with the testing effort
The strategy for developing test scripts and executing the tests
Purpose
The purpose of the testing approach and strategy document is to provide a reference at any time for resources working on tasks within the Testing process of Corporate Procurement and Application implementation. This document is the source for the testing requirements, strategy, approaches, direction, risks, benefits and assumptions. The document also covers the delivery of project and support services to assist the organization in the completion of the project. All members of the team should understand and follow the same testing strategy.
The requirements will have a continuing influence on the scope and content of the testing work throughout the project’s life; therefore, it is important that the list of requirements be as complete as possible and agreed on early during the project. The testing team will need to keep the requirements in mind throughout the project and help create testing that is compatible with them. Furthermore, if the testing requirements alter mid-project, the changes should be noted and disseminated in a timely manner.
The project manager uses this document to understand how the team plans to conduct the testing work and how the testing effort may impact the overall project.
Related documents
Future Process Model
Business Requirements
Business Requirements Mapping
Unit Test Scripts
System Test Scripts
Integration Test Scripts
Audience
The audience for this document includes project management team, track team leads, Corporate Global Support Application Specialists, P2P Supper Users and Business Subject Matter Experts.
Roles and Responsibilities
Test lead: The test lead will be responsible for overall management of the test effort responsible of the test lead include
Development Test Approach
Manage Test Effort
Manage Issues
Coordinate Internal / External Dependencies
Technical Support: The technical support group will be responsible for supporting the global test execution. Global support assumes appropriate and agreed to coverage during the test windows to ensure technical issues are resolved to allow the test execution to continue. Responsibilities include:
Define migration processes between unit, system and UAT stages
Support testing tools
Support test environments
Test Planning: The test planners will be responsible for the overall preparation of a structured, well documents test plan which will serve as the input to test execution. Responsibilities include:
Review and supplement test conditions
Define test cycles
Prioritize and map conditions to cycles
Create test scripts
Define test scripts
Define test data
Define expected results
Test execution: The test execution group will be responsible for executing all test cycles. Responsibilities include:
Execute test scripts
Verify test results
Document actual results
Identify problems
Re-execute test
Test Coordinator: The test Coordinator will manage the test issue reporting process. Responsibilities include:
Verifying test issues for
Completeness
Prioritization
Severity
Assigned to Resources
Fit it coordinator: Fix it coordinator may be a role within the technical support team, as a point person for critical issues needing immediate resolution to continue. Responsibilities include:
Communicate issue resolution timeline and / or plan to resolve
Escalate “show stopper” issues to the project manager
Ensure appropriate resources assigned to issues