Show TOC

Maintaining AttributesLocate this document in the navigation structure

Use

The test case attributes contain organizational and technical information. Many of the attributes are optional. Attributes can be used as test case selection criteria.

General Data

  • Header Data

    • Title (required field). A short description of the test script.

    • Package (required field). You assign the test script to a package when you save the test script for the first time.

    • Person Responsible (required field). The creator of the test case is automatically entered in this field. You can change the entry, for example, if the creator is not the person responsible for this test case.

    • Component (required field). SAP application hierarchy component name.

  • Search Terms. These can be used to find the test script.

  • Maintenance System

    • System data container. Enter the name of a system data container. This will be used as the default system data container when the test script is executed.

    • Target system. If you have specified a system data container, you can also specify a target system. This is the default target system for eCATT commands for which a target system has not been specified. This system is accessed during script development for recording, and for execution within the eCATT script development environment. If no maintenance system is specified, the development system (NONE) itself is used. The maintenance system is not relevant to the execution of test configurations.

Versioning Data

eCATT uses this data to specify the version that is to be executed if the test script is referenced by a test configuration or an REF command. First, eCATT checks the target system during replay and saves the software component, the release, and the patch level of the target system in the log. It then compares the target system data with all the versioning data of the test script and selects the version that matches.

You can also change the versioning data by using version management . We recommend this option because you can view the versioning data for all versions of a script at the same time.

For more information, see the Versioning Data section.

Addition

  • Planning Data. You can enter an estimate of the time needed for the test and also assign a priority.

  • Administrative Data. This is automatically entered.

Constraints

On this tab, you can document the restrictions on where and how the test script is used. Most of the entries here have no effect on the execution of a test script. Exceptions are:

  • Status : Only active scripts are included in automatic tests.

  • Command BCSET in Script Allowed: The BCSET command will only be executed if this is selected.