Scribd
Upload
40 views

Seven Types of SAP R/3 Testing

This document describes 7 types of SAP testing: 1) Unit testing tests transactions at the lowest level; 2) Development testing tests reports, interfaces, workflows developed with SAP code; 3) Scenario testing tests chains of transactions within a module using roles and data; 4) Integration testing tests end-to-end processes across modules with external systems; 5) Performance testing determines system bottlenecks and degradation points; 6) User acceptance testing allows end users to test from their perspective; 7) Regression testing ensures previously working functionality is not affected by new changes.

Uploaded by

Rahul Ravi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
40 views

Seven Types of SAP R/3 Testing

This document describes 7 types of SAP testing: 1) Unit testing tests transactions at the lowest level; 2) Development testing tests reports, interfaces, workflows developed with SAP code; 3) Scenario testing tests chains of transactions within a module using roles and data; 4) Integration testing tests end-to-end processes across modules with external systems; 5) Performance testing determines system bottlenecks and degradation points; 6) User acceptance testing allows end users to test from their perspective; 7) Regression testing ensures previously working functionality is not affected by new changes.

Uploaded by

Rahul Ravi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Seven types of SAP R/3 testing

Traditionally, the main types of SAP tests include unit, development, scenario, integration, performance, and regression testing. These tests are further described below to provide greater granularity into what each type of test entails. 1. Unit Testing This is the lowest level of testing at the SAP transaction level. Unit testing includes boundary testing for positive and negative testing. Negative testing should be performed for custom fields and transactions to ensure that the system only allows valid input and can adequately perform e ception handling. An e ample of a negative test for a process would be attempting to process an order with the wrong status. 2. Development Testing This is the testing for reports, interfaces, conversions, enhancements, wor! flows, and forms "#$%&'() development ob*ects developed primarily with A+AP code. Testing of development ob*ects includes testing for security authori,ations, performance, e tracts, data transfer rules, reconciliations, and batch scheduling *obs. $n many SAP pro*ects, third-party tools such as %ontrol-. and AutoSys are acquired to schedule reports and interfaces with dependencies, and these scheduled *obs need to be tested prior to releasing the system into the production environment. /evelopment testing should also ensure that data can be tested through the intended target system. 3. Scenario Testing The equivalent of a string test, scenario testing is the testing of chains of SAP transactions that ma!e up a process within a single area or module. Scenario testing includes testing of a process with data from e ternal systems and applicable SAP roles0profiles. Scenario testing is primarily a manual effort but can include some partial automation with test tools for processes that are stable, fro,en, and proven to have wor!ed manually. The scenario testing is owned by the configuration teams but includes participation from S.&s and members of the test team and development team. 4. Integration Testing $ntegration testing is the testing of chains of SAP transactions that ma!e up an end-to-end process that cuts across multiple modules, for instance, order-to-cash, purchase-to-pay, and hireto-retire with e ternal data and converted data. $ntegration testing includes testing through the e ternal systems and SAP bolt-ons with security roles and wor!flow. $ntegration testing consists of multiple iterations. . Performance Testing Performance testing encompasses load, volume, and stress testing to determine system bottlenec!s and degradation points. A performance test helps to determine the optimal system settings to meet and fulfill the established S1As. !. User Acceptance Testing User acceptance testing allows the system2s end users to independently e ecute test cases from

the perspective of how the end users plan to perform tas!s in the production environment. The owners of the user acceptance testing are the end users, and the configuration and test team members resolve defects identified during the user acceptance test. The test team and change management team members help train end users and prepare them for the user acceptance test. ". Regression Testing #egression testing ensures that previously wor!ing system functionality is not adversely affected by the introduction of new system changes. System changes targeted for the production environment need to be analy,ed for impact and cascading effects on other processes.

You might also like