eCATT provides a environment for developing functional tests. Rather than create a single object that defines every aspect of a test, eCATT 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. The following graphic summarizes the development process and how the different eCATT objects fit into that process.
The process is as follows:
1. Define what you want to test within the scope of your project and make sure that the test system and the systems to be tested are prepared for use with eCATT.
2. Create a system data container in which you map out the system landscape for the project. Without a system data container, you cannot write test scripts that access other systems.
3. Create the test scripts themselves.
4. Consider the data that you will need to run the tests and arrange it in test data containers to allow the maximum degree of reuse and to eliminate as much redundancy as possible.
5. Assemble the test configurations from the other eCATT objects.
6. Test configurations can be assigned to test catalogs and test plans within the Test Workbench. The configurations can then be assigned to individual users for testing.
An executed test configuration produces its results in the form of a log. Not only does the log provide a simple pass or fail result for the complete test, it also provides a permanent and detailed record of the test.