This process describes the basic procedure for conducting automated performance tests using ST30.
? Required profiles in the systems under test:
0 S_TOOLS_EX (to use statistical records, STAD)
0 S_ADMI_FCD (values ST0M, ST0R, SM21)
0 S_ADMI_FCD (to use SQL Trace, ST05)
? Required profile in the central test system:
0 S_TABU_ALL (to use table maintenance views; for editing log IDs)
? Required authorizations to run function groups in the systems under test:
? Required authorizations in the central test system:
0 Authorization to execute RFCs
0 To enter ST30 customizing data, make sure that you have the required authorizations to maintain views of database tables (similar to SE16 authorization).
? The scenarios to be tested must be available as eCATT test configurations in the central test system.
Test configurations must be executed repeatedly to obtain reliable results. Therefore, make sure that data created or modified during a test run does not influence subsequent test runs.
? The systems to be tested must be enabled to work with eCATTs. GUI scripting is strongly recommended but it cannot be used in all cases.
? To enable the eCATT function for the client use transaction SCC4. To enable scripting, use transaction RZ11 to set system parameter sapgui/user_scripting to TRUE.
Automated performance testing involves the following steps: