Skip to Content

 Atin Shee


Different types of testing in a SAP Implementation project:


·          Configuration testing  –  The configuration testing ensures that all the requirements supported by standard SAP are properly configured and verified.  

The main objective of the testing is to test the functioning of the individual SAP transactions after baseline configuration is completed and to identify any configuration related defects.


·          Development Unit Testing – Development Unit Testing is performed for all the identified GAPs in requirements.

The objective of the Development Unit Testing is to ensure that the development objects are performing as per the requirement and design specifications.  


·          Interface Testing – The Interface testing includes the testing of the SAP interface programs, external interface programs and all related middleware settings. 

The objective of interface testing is that the interface meets the technical and functional requirements and the data transfer requirements between the applications.


 ·          Batch Testing – Batch testing tests that all the batch processes required are performing as per expectation and the scheduler is working as expected.


 ·          Conversion Testing – Conversion testing includes the testing of the SAP data migration programs and all related middleware settings which will load the data from the existing system to the SAP system. 

The objective of this testing is to check that all the developed conversion programs are performing as expected.  


·           Security Testing – Security testing ensures the SAP security roles and authorization based on the defined requirements.  


·          Regression Testing – Each time any new patch comes in or any fix has been applied in any of the system components, regression testing needs to be done to ensure that any changes applied to the system does not impact any of the existing functionalities or cause any undesirable results from the system. During multiple releases, regression testing needs to be done whenever a new release is installed to ensure that the new functionality does not impact any of the existing functionalities.  


·          Integration Testing – Functional Integration testing is performed to verify proper execution of the entire application including interfaces to external applications. This ensures that the integrated components of the configured transactions and the development objects for the GAPs are functioning properly according to the requirements and specifications. 

The objective is to perform the end to end process integration between all the SAP components and all external application systems are functioning properly. Functional Integration Testing ensures that all the business scenarios have been tested prior to the User Acceptance Testing.


 ·          User Acceptance Testing – User Acceptance testing is conducted in by a group of business end users in order to validate that the system meets requirements relevant to their functional areas.  This testing will ensure that the system is acceptable from the user’s perspective and is performing as per the requirement as well as the expectation from the users. 


·          Performance and Load Testing – The performance testing is performed to verify whether the performance of each operation is as per expectation.   The objective is to verify the response time of the transactions under different conditions. 


·          Backup and Recovery testing – This is to test the system backup processes. Also the restoration process is verified here. 


·          Cutover Testing – This testing is performed to ensure that all the required activities (Data Migration, quality check, manual update and data synchronization) can be completed prior to go live within identified cut over window. The objective of this testing is to ensure that the data conversion, dependencies of cutover activities and timing match with the cutover plan.


·          Pre Production Testing – Pre-production testing is to verify that the application and its interfaces can operate in the production environment. Its focus is on the operational aspects of the system but not a thorough functional test but a subset of it.  

This testing is generally the final part of a testing exercise prior to go live.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

Leave a Reply