The Test Workbench contains the Computer Aided Test Tool (CATT) to create test cases. You can create both manual and automatic test cases.
Manual test cases are most useful for acceptance tests. They are descriptions of tests which a tester must perform manually on the system.
Automatic test cases are performed by the SAP system without user dialog, and are most useful for function tests. The result of an automatic test case is a detailed log which documents the test. The use of automatic tests can considerably reduce the test effort.
Test cases test individual transactions or whole business transactions. Test cases are constructed modularly, to minimize the creation and maintenance effort, above all for business transactions.
The procedure for testing one transaction or function is described in test modules. The creation of test modules is greatly simplified by the CATT recording functionality.
Test procedures can be constructed from the test modules. Test modules are referred to and linked in the test procedure.
In modular test procedures:
· test modules can be reused
· changes to test modules are immediately effective in the test procedures which use them.
The transaction test procedure is recorded with a transaction recorder for the test module. The creator runs the application as in normal dialog operation. At the end of the transaction, you go back to CATT.
You can make test cases flexible by subsequently replacing the values input when recording by parameters.
By creating variants you can store frequently needed parameter settings. When executing the test case, you can then access these settings.
This functionality has been available since 4.6 in an additional CATT maintenance mode which can be used by users without technical background knowledge.
Starting test cases in a SAP system is usually coupled to changes of database entries. For this reason, test cases should not be started in the production system. To control this centrally, the client table maintenance has a flag which allows tests to be run in the system.
Authorizations are also checked in CATT.
The ABAP Workbench infrastructure provides general functions such as correction and transport, the Repository information system, and multi-lingual applications.
In addition, it guarantees the correctness of a test run by updating synchronously, thereby explicitly refreshing the table buffer. This is especially important for transaction chains, where transactions use the results of previously executed transactions.
Besides, processes from a central SAP system can be tested in a different SAP system. The test procedure runs in the central SAP system and controls the transactions via Remote Function Call (RFC) in the satellite systems.
The CATT logs created contain all information relevant for the test run and are stored centrally in the database of the executing SAP system.
· test transactions
· check system messages
· check authorizations (user profiles)
· testing results and database updates
· setup customizing tables
· test the effect of customizing setting changes
These processes are less suited for CATT:
· lists and display results
· menu paths
· Online help (F1, F4)
· editor functions
You cannot use CATT for the following transaction types:
· Transactions that contain the statement LEAVE TO TRANSACTION