The overall objective of performing a formal test is to ensure the the new sap module/object meets the business requirements as documented, configured and approved by implemented company. From an SAP implementation point of view this includes testing of SAP functionality, conversions, interfaces, enhancements, reports and integration with other systems, end user security, process controls, technical infrastructure, volume (production simulation), and stress testing.
Testing should focus on the areas that are critical to the operation of the system and/or which involve a large degree of complexity. The testing work stream encompasses the following broad categories of testing:
- Migration Testing – Testing of data conversion and configuration
- System and Interface Testing – Testing of data flow within and between applications
- Business Process Testing
- Infrastructure Testing
The following levels of testing could be performed:
- Unit Testing
- Conversion(Data Migration) Testing
- Integration Testing
- Volume & Stress Testing
- User Acceptance (UAT)
- Disaster Recovery Testing
- Testing of the backup approach
For each level of testing the following method could be adopted:
- Plan
- Prepare
- Execute
- Report
Unit Testing Scope:
It verifies that individual programs execute without error, perform within set standards and are of good quality.
Unit testing is an iterative process that occurs during the configuration and system development effort.
During the Realization Phase of SAP implementation, configuration of the standard system takes place based on the work completed during Blueprint and development related to reports, interfaces, conversions and enhancements (RICEF) is performed.
The Development Team needs to perform Technical Unit Testing for each development before it is handed over to the Functional Team. The Functional Business Process Owner, or applicable designee, needs to perform Functional Unit Testing on development objects when the Development Team delivers them.
As each configuration function is completed and/or development object is delivered, it needs to be also tested by the functional team.
This testing focuses on a unit of work in relative isolation and is referred to as Functional Unit Testing. The objective of the test will be to demonstrate the key elements of the solution online and to identify any significant omissions or misunderstandings.
Unit testing is mostly conducted for SAP ECC functions (transaction codes).
Common Entrance Criteria for Unit testing:
The following activities are necessary to enter unit testing:
· Definition of configuration values.
· Availability of the Development environment and the associated Clients noted above.
· Completed system configuration.
· Complete functional and technical specifications.
· Approved Unit Test Plans.
· Completed development of RICEF objects.
Common Exit Criteria for Unit testing:
The following criteria are necessary to exit unit testing:
· Successful results of the Unit Test Plans for Configuration.
· Successful results of the Unit Test Plans for RICEF objects.
Possible Deliverables of Unit testing:
The following deliverables will be produced as a result of the Unit Test Phase:
- Detailed Unit Test Plans for each RICEF object.
- Detailed Unit Test Plans for each T-code.
- Results of Unit Testing for each RICEF object.
- Results of Unit Testing for each T-code.
- Inputs necessary to complete Business Process Procedures.
Production System Readiness Testing (PSR)
Production System Readiness testing typically involves Volume / Stress Testing which represent the final major testing scenario to be completed after the system is functionally proven. The objective of PSR Testing is to simulate production activity in a simulated production environment to insure that the production environment will adequately process the production load.
PSR testing could be conducted in the actual production environment after completion of Integration Testing Cycle.