SAP Testing Phases/Methodology

Three phases in SAP methodology are

1.Test Preparation:
1) Identification of business process
2)Development of manual test cases and automated cases.
3) Creation of test plans & review
4)Set up of test system(Dev,Quality,Pre production system)
5)Creation of test data.

2.Test execution Phase:
1)Test execution using test tools such as Solution Manager,HP Quality Center ,HP ALM.
2)Test status reporting & defect handling.

3.Test Evaluation Phase:
1) Detailed assessment of all test plans
2) Defect Analysis
2) Documentation of the testing process

Types Of Testing In a Sap HR Implementation Project

Sap recommends 3 system Landscapes
-DEV
-QAS
-PRE PRD-Optional
-PRN

Following are types of SAP R/3 testing

1. Development Unit Testing
2. Configuration testing
3. Interface Testing
4. Batch Testing
5. Security Testing
6. Regression Testing
7. Integration Testing
8. Parallel Testing
9. Performance and Load Testing
10. User Acceptance Testing(UAT)

1.Development Unit Testing
This is done by developer .Unit test is executed in development system. This tests alone pieces of
functionality. For example PA40 Actions,PA30 Maintain master data ,Infotypes, reports .

2.Configuration testing
To check if the configuration is correct . This testing is to make sure that all the business requirements are
properly configured and verified.


3.Interface Testing
It includes the testing of the SAP interface program, testing of middleware settings, data transfer requirements
between the system.
Ex: If you have two development systems SAP ECC & Non SAP system . Run SAP interface program to sent
data to Non SAP system & can use it.
In interface testing system triggering file to other system ,data transfer is successful, and the receiver is able
to accept & process the data received from SAP.

4. Batch Testing
Batch test includes testing of all batch scheduled jobs .It also test the performance of batch schedules jobs
.Tivoli Workload scheduler(TWS) is used to schedule the jobs of multiple platforms.

5. Security Testing
Security testing ensures the SAP security roles and authorization roles provided based on the requirements.
Test IDs will be created of different job roles and used to both confirm what a user can do and what a user
cannot do.
The tester will perform both Positive and Negative testing of the of job roles that are assigned to user test ids.

5.Regression Testing
Regression testing ensures that new introduced /configured changes will not adversely affect by the existing
system. Test will test all existing T codes ,report s etc to make sure that nothing is impacted.

6. Integration Testing
In a multiple plat form environment integration testing is mandatory .All integrated areas need to test by a
tester. It is testing of SAP transactions (for example hire-to- termination- to rehire) , data conversion
,security roles and workflow.

7.Parallel Testing
During parallel testing all the existing data in the legacy system will transfer to SAP system & perform same
process in both systems. A successful Parallel test shows identical results when both the legacy system and
new system results are compared.
Tester will run the programs / transaction repeatedly in both system , resolve issues with the help of other
team if any issues, continue perform tests till gets the identical results in both.
Example : Parallel payroll process. Run payrolls in SAP & legacy system for 2-3 months & analyze the
payroll results

9.Performance and Load Testing
Performance testing is to find out the performance of various programs/reports . The objective is to validate the
reaction time of the transactions under different conditions.
If there a program to upload files contains some records .During performance test , the tester will note down
the time taken to complete the process & compare with previous results.

10.User Acceptance Testing(UAT)
User Acceptance testing is conducted in by a group of business end users to validate that the new developed
SAP system meets all requirements. During User acceptance testing the system end users separately execute
test cases & find out the results are as expected. The test team will guide the UAT team in their testing
activities.
UAT will ensure that the system is acceptable from the users perspective, performing as per the requirement &
if the users are satisfied they provide a sign off.