eCATT (extended Computer Aided Test Tool) is an SAP Testing Tool used to automate & test business scenarios in SAP R/3. Each test that was executed on. eCATT Tutorial submitted by Sumeet Kaul. eCATT- An With SAP eCATT, users are also able to test business processes that cross system boundaries. SECATT is used in similar way as used by other SAP tool like LSMW/BDC in From administrative point of view, system should be allowed with eCATT and.
|Published (Last):||17 May 2004|
|PDF File Size:||19.79 Mb|
|ePub File Size:||5.17 Mb|
|Price:||Free* [*Free Regsitration Required]|
This tutorial is intended for test developers new to eCATT.
By the end, you should be able to use eCATT to create reusable test cases for testing remote systems. Scripting has been enabled. The graphic below shows how the different eCATT objects fit into the test development process.
The first step is to define what you want to test within the scope of your project. Having done this, you 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. The third step is to create the test scripts themselves.
You then need to consider the data that you will need to run the tutorisl. The data should be arranged in test data containers to allow the maximum degree of reuse and to eliminate as much redundancy as possible.
Finally, you assemble the test configurations from the other eCATT objects.
Introduction to SAP eCATT run by SECATT
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.
The Test Workbench is not part of this tutorial. Background When you design an automated test, you need to answer the following questions: What applications am I going to test?
eCATT Tutorial and Step-by-Step Guide
What does my system landscape look like? How can I best create an automated test for my applications?
What data do I need to feed into the tests? How do I build executable test cases? How can I organize my test cases?