eCATT provides a environment for developing functional tests. eCATT creates a single object that defines every aspect of a test, has four separate object types. The first three form the building blocks of a test, and the fourth combines the others into a complete test case.
Test Script: Set of commands that form the test
Test Data Container:Reusable sets of parameters that can be used to run tests
System Data Container:A list of systems that are addressed during the execution of a test script
Test Configuration:A Test Script, plus data from one or more Test Data Containers, plus a System Data Container that describes the system landscape.
Ways Of Doing Testing In eCATT
eCATT enables to test all SAP applications. There are four different drivers available in eCATT for this testing purpose as follows
Non-User Interface: Suitable for testing backend R/3 specific modules like function modules & BAPIs, Interfaces testing in mySAP environment, load testing.
TCD: Suitable for testing transactions (especially who don’t involve activex controls), load testing. Doesn’t require GUI for playback, so offers maximum speed for testing.
SAPGUI Scripting: Suitable for testing transactions, who involve activex controls. Requires GUI for playback & hence very slow. Not
suitable for load testing.
Interface To External Tools:External products, which are certified against BC-eCATT Interface, can be tested who run under GUIs (Other than SAP GUI for Windows & SAP GUI for JAVA) using eCATT.
Main focus of this document is to test the business process by recording the set of transaction code through TCD.