eCATT stands for extended Computer Aided Test Tool (eCATT) which is built is a testing tool to test SAP system. By using the testing tool we can test the entire business process, and we can also use this tool with a third party testing tool (I am not covering this topic). Execution of every test script ends with a log, which explains the results of the test script.
By using eCATT we can do following operations:
- Test transactions, reports, and scenarios
- Call BAPIs and function modules
- Test remote systems
- Check authorizations (user profiles)
- Test updates (database, applications, GUI)
- Test the effect of changes to customizing settings
- Check system messages
Download the document on ecatt with steps on working with Material master creation using Ecatt.
Allowing ECATT to run
In each client in which you want to run CATT procedures or ECaTT test scripts, you must indicate in the client parameters that should be allowed. To do this, start the table maintenance transaction SM31, enter table T000 name and choose Maintain. You will see a warning that this is independent of the client – it is OK to ignore.
The system displays a list of clients that have been established in the system. Double-click the one you want to allow or CATT ECaTT.
According to the release in which you work, you will see one of two screens. In older versions, the Restrictions group box contains a check box allows CATT process is launched. This must be checked.
In newer systems, you have more choices. You can control the type of functions that can be executed, and the manner of execution, by choosing one of the options listed in the box below:
As one of the main principles of ECaTT is to execute all test cases from a test system, RFC communication is necessary to connect to target systems. It is possible to restrict such communication RFC by using trusted RFC, making it impossible to have passwords to be stored in the RFC destinations and transmitted over the network.