7/30/2019 SAP_Testing

1/3

In any SAP Project testing can be happen in 3 phases.

Unit testing happens in Dev server.

Integration and User Acceptace Test happens in Quality Server.These all are done manually step

by step.

We have got standard SAP Test Scripts/prepares based on the Client/company/Project.

Unit Testing: it can be tested in bits and pieces (Ex: Sales order Creation).

Integration Testing: OTC Flow (Create Sales order to Invoice).

User Acceptace done by the Client in "Q", if they are satisifed with the result they will give

Sign-off for the project.

There is another sort of testing so called Automated Regression Testing. that can be done byeCATT/IBM Rational Tools.

# 2 Unit Testing:When you test every single document is called unit testing.

Integration Testing :It is purely with other modules and we have to check whether the FI testing

is working with other related modules or not.

UAT :When we test any particular document with the user and if it is ok immediately we have totake the signature on the document, which is signed off and can be forwarded to the immediate

boss. There are some steps to be followed when we go for user acceptance testing.

What kind of testings that are carried out in testing server?

1. Individual Testing ( Individually which we've created)

2. Regressive Testing ( Entire Process)3. Integration Testing ( Along with other integrated modules)

The 3 types of testing is as follows:-

1. Unit testing (where an individual process relevant to a SD or MM etc is tested)

2. Integration testing (where a process is tested that cuts across all areas of SAP).

3. Stress testing (where lots of transactions are run to see if the system can handle the data)

Testing mathologies and types: there are 6 types of testings:1. Unit Testing

2. System Testing

7/30/2019 SAP_Testing

2/3

3. System Integration security Testing4. Performance Testing

5. User Acceptance testing6. Regression Testing

Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-createorder, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will betesting 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be

looking and checking/testing any integration between order and delivery; delivery and TO; TOand PGI and then invoice.

Whrereas System testing you will be testing the full cycle with it's integration, and you will be

testing using test cases which give a full cyclic test from order to invoice.

Security testing you will be testing different roles and functionalities and will check and signoff.

Performance testing is refered to as how much time / second will take to perform some actions,like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6second. Usually it is done using software.

Regression testing is reffered to a test which verfies that some new configuration doesnot

adversly impact existing functionality. This will be done on each phase of testing.

User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the

execution of predefined business scenarios, which combine various business processes. The usertest model is comprised of a sub-set of system integration test cases.

We use different software during testing. Most commonly use are

Test Director: which is used to record requirement, preparing test plan and then recording the

progress. We will be incorporating defects that are coming during these testings using differenttest cases.

Mercury Load Runner: is used for performance testing. This is an automatic tool.

What does the following terms means :

- Technical Unit Testing

- Functional Unit Testing

- IntegrationTesting- Volume Testing- Parallel Testing?

Technical Unit Testing= Test of some technical development such as a user exit, custom

program, or interface. the test usually consists of a test data set that is processed according to thenew program. A successful test only proves the developed code works and that it performed the

process as as designed.

7/30/2019 SAP_Testing

3/3

Functional Unit Testing= Test of configuration, system settings or a custom development (it mayfollow the technical unit testing) These usually use actual data or data that is masked but

essentially the same as a real data set. A successful test shows that the development orconfiguration works as designed and the data is accurate as a result.

IntegrationTesting= Testing a process, development or configuration within the context of anyother functions that the process, development or functionality will touch or integrate . The testshould examine all data involved across all modules and any data indirectly affected. A

successful test indicates that the processes work as designed and integrate with other functionswithout causing any problems in any integrated areas.

Volume Testing= testing a full data set that is either actual or masked to insure that the entire

volume does cause system problems such as network transmission problems, system resourcesissues, or any systemic problem, A successful test indicates that the processes will not slow or

crash the system due to a full data set being utilized.

Parallel Testing= Testing the new system or processes with a complete data set while running thesame processes in the legacy system. A successful test will show identical results when both thelegacy system and new system results are compared.

I would also note that when a new implementation is being done you will want to conduct at

least one cut over test from the old system to the new and you should probably do several.