Overview

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_dimp50/helpdata/en/6f/b1923fa5e93c17e10000000a114084/content.htm
Created on September 14, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 3

Table of content
1 Overview

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 3

!--a11y-->

1 Overview
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.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 3