Show TOC

Background documentationComponents of Automated Test Cases Locate this document in the navigation structure


The systems under test usually change over the time. For example, you start by testing a certain release of a system under test. Once you have developed your test cases, you may want to use them again to test later releases of the system under test, or you want to reuse a test case in the test system which you created in the development system.

By using the information which SAP Solution Manager provides about the system landscape, you can upgrade or even exchange the systems under test without modifying your test objects.

Therefore, a test case (either eCATT or created with a third party tool) is actually a test configuration of reusable objects. A test configuration comprises the following object types:

  • The test script represents the steps of a business process which is performed by the automated test case, for example:

    1. A purchase order is entered on the CRM system.

    2. The order is passed to the ERP system where production is scheduled.

    3. The ERP system passes information to the SCM system where a table is updated.

  • The system data container defines the systems on which these steps are performed. A system is defined as follows:

    • Operational function (CRM, ERP system, for example)

    • Technical role (system roles such as development, test, evaluation, production system, for example)

    The systems are represented by logical components. Relevant parameters of the respective system landscape (target systems and RFC destinations) are retrieved automatically from the Solution Manager project or the solution which is assigned to the test configuration. When you execute a test case you can switch the system role (from development system to test system, for example) without having to adjust any system parameters.

  • The test data container is a reusable data object with a set of user-defined parameters which can be maintained independently from the test script.

    For more information, see Organizing Test Data.