What is unit testing in SAP R/3
SAP unit testing 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 exception handling. An example of a negative test for a process would be attempting to process an order with the wrong status.
Unit testing includes testing security roles. The configuration team owns the unit-testing effort and is responsible for planning and execution of unit testing. The main focuses for unit testing are:
- Master data
- Negative-positive testing
- Transaction functionality
- Security roles and profiles
Negative testing is performed on security roles and profiles, custom fields, objects, and processes. Each test in negative testing needs two elements:
1. Intentionally specify conditions that will cause the software to generate an error.
2. Ensure that the generated error is handled in a specified manner.
An example of a negative test condition would be: Attempting to post a material to an invalid profit center should produce an error message. Another negative testing example for security roles and segregation of duties would be “An inventory clerk attempts to approve a million-dollar purchase order when he is only permitted to approve purchase orders for a maximum of $500,000″
Negative testing will be designed to address the following situations:
- Check exception handling and error message.
- Prove that the system will deal with program exceptions and erroneous data.
- Limit or prevent an end user from trying to do something he should not.
- Demonstrate that the system does not do anything that it is not supposed to do.
- Users are permitted to perform only actions based on their authorizations, position roles, and permissions.
Popularity: 14% [?]
