SAP ASAP Methodology - Implementing SAP CRM - page 389

To make the testing effort easier, ASAP recommends the formation of a series of
integration-testing cycles consisting of a selected set of business processes depending on
the degree of their importance. These are the integration-testing Cycles L1 and L2 that
were mentioned in Section 13.2.2.5.2 “Prepare Business Blueprint.” The cycles are tested
sequentially till all issues are resolved and the tested system is ready to be delivered for final
preparation before going into productive phase.
Cycle represents an iterative process that systematizes the final testing effort. The cycles
are defined based on the following guidelines:
− Cycle 1 : The purpose of this cycle is to tune the testing of the business processes for the
master data and high-priority transactions, followed by testing the running of high-
priority business processes.
− Cycle 2 : The purpose of this cycle is to tune the testing by running the business processes
that include exceptions transactions, reports, and user profiles.
The final integration process is similar to that adopted for the final configuration except that
in the BPML, only those processes are selected that were set to indicate integration-testing
Cycle 1 or 2.
If one cannot schedule to test everything, the test cases can be prioritized based on
− The frequency of the process
− Failure impact of the process or dependencies of the process
− The probability of occurrence of the test case
ASAP provides a formula to calculate the test priority for test cases; as the test priority
increases, the greater is the need to include the test case in the integration testing.
2. Prepare Final Integration Test Plan.
The purpose of this task is to prepare a detailed integration test plan that must include all
processes and components like
− Business processes
− Reports
− Interfaces
− Conversions
− Enhancements
− Printer/fax outputs
The scope of the test is based on the process design for the business area and their business
processes as defined in the Business Blueprint. The test plan identifies necessary dependen-
cies and ensures that everything in the blueprint is tested.
Again, ASAP provides a list of predefined Test Procedures to help in accelerating this
step.
3. Transport All Objects to QA and Freeze System.
The purpose of this task is to freeze the system settings to protect the completed system from
changes till the full cycle of integration testing is completed.
This includes
− Configuration Settings
− Client Settings
− Application Data
− Repository Objects
4. Conduct Final Integration Tests.
The purpose of this task is to conduct the final integration test based on the final integration
test plan involving usual steps like entering initial setup data, running test cases, recording