Purpose
The purpose of this deliverable is to outline the business scenarios being tested / clarify the scope, assign the responsible parties for testing each component of the test scenarios, and reconcile the approval process.
It is critical to define the following:
· Technical test environment (legacy systems, interface systems,...)
· Test controlling process
· Tools to support the test e.g. SAP Test Workbench
· Error-message handling and error categories
· KPIs - how to measure the success of the test
· Format of the test documents and the deadline for creation
How should it be produced
The functional / scenario scope must be defined by the application and technical project teams in an overall test plan. The test plan, the approval process and most of the additional planning activities should be confirmed by the customer of the project before the commencement of testing. A documented test scenario needs to be prepared, which outlines the steps and transactions involved, expected results, and a section to record the actual results.
What if it is not done
· Integration testing cannot be executed without proper planning.
· Integration results are not comparable with expectations
· A status is not measurable
· A go live without an integration test based on a test plan will have high risk for failure
Source of Input
(Deliverable/Other) |
Input
|
MySAP.com Solution Business Blueprint |
· Detailed Transactional Scope |
Configured and Confirmed Baseline |
· Baseline Scenarios |
Confirmed Final Configuration |
· Final Confirmation Scenarios |
Approved Development Work |
· Development List |
<Customer Input> |
· Prioritization |
Outputs
Refer to the breakdown of the deliverable in the roadmap structure.
Testing is one of the major activities during a project. Plan enough time for preparation, execution and correction.