Follow these 11 tips to avoid errors when you use extended Computer Aided Test Tool to test your end-to-end business scenario transactions.
SAP extended Computer Aided Test Tool (eCATT) caters to the testing of SAPGUI-based transactions. You use another tool for testing Web-based SAP transactions. There is an easy interface in eCATT and test cases are ready as reusable automated scripts. If changes in the transaction behavior in an SAP system lead to an error during automated test case execution, you must reautomate. Possible errors include a test script recording error, invalid test data, changes in configuration, a master data error, an SAPGUI-based tester user ID settings error, custom development as a part of user exit or Business Add-In, or custom development involved in changes to a standard SAP program. Reautomation is the process of recording the SAP transaction again due to an error that occurred in the original automated transaction.
SAP extended Computer Aided Test Tool (eCATT) is a cost-efficient automation tool for business testing. However, automated tests can fail even if the test data is correct, leading to the need to reautomate the test case. The main reason for failure is an incorrect sequence of dependent test cases during execution. It is my experience that you can reduce reautomation by 60% by following my tips. If you are not familiar with eCATT, see the sidebar “What is eCATT and When Do You Use It?”