1. Stop the Easy Access menu in the session in which you create the test configuration. Enter “/n” once or several times in the relevant session. The Easy Access menu has been stopped successfully if the screen with the Start SAP Easy Access button is displayed.
2. Record the test scripts to be used within the test configuration with GUI scripting.
In your local GUI (for example, SAP GUI for Windows), activate Enable Scripting but deactivate both Notify when… indicators in the Options menu (Alt F12 ® Options ® Scripting tab).
3. Maintain the test configurations in the central test system.
Make sure you define the RFC destinations where eCATT test configurations are supposed to run without load balancing (transaction SM59), as the performance figures created in a system that runs on multiple servers are server-specific.
4. Create an adequate quantity of data to serve as a basis for testing in each system. Create the data using client copy, extra eCATT scripts and/or reports to reset the data to a default.
5. To help differentiate between relevant and irrelevant measurement data in the statistical data list, use data correcting reports (prefix „Z_*“) within the eCATT test scripts.
6. Execute the eCATT test configuration in transaction SECATT to check whether it runs correctly.
You have set up an eCATT test configuration that can be used as a basis for performance testing in transaction ST30.