Maintaining Attributes 
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. 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.
Versioning Data
This data is used by eCATT to determine which version is to be executed when the test script is referenced by a test configuration or a REF command. eCATT inspects the target system at replay time and stores the software component, release, and 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.
- Software Components. For example,
SAP_BASIS.
- You can list several software components. However, only one is used to determine which version is to be executed. If you list several software components, use
to specify the one that is to be used.
- The software components are identical in all versions of the script.
Releases. You can specify the releases (for example, 620) and patch levels for which the test script is valid.
- You need not specify the patch level.
- If you specify a particular combination of release and patch in one version, that combination cannot be specified in another version. Backup versions are the exception to this rule.
- In one version only, you can enter an asterisk (*) in the Release field. This version will be used if no other version has release data that matches that of the target system.
Backup. To exclude a version from the version search, select Backup. This prevents the version from being executed by a test configuration or REF command. It can only be executed from the test script editor.
Extra
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.
Restrictions
On this tab, you can document the restrictions on where and how the test script is used. You can enter information in the following categories:
- Technical Information
- Dependencies
- Use as