Attributes (SAP Library - CATT: Enhanced Mode (BC-CAT-TOL))

Attributes

Use

The test case attributes contain organizational (e.g. tested components) and technical (e.g. test case type) information. All attributes can be used as test case selection criteria (e.g. in the Test Workbench).

Functions

There are four groups of test case attributes:

Management data

Test case
Name of the current test case.

Title (required field)
Enter a short description of the test case.

Note

It should start with the transaction code of the transaction to be tested for test modules (transaction test case). This helps you to find test modules to use in test procedures (business process test case).

Type:
Test case type

Person responsible
The creator of the test case is automatically entered in this field. You can change the entry if the creator is not the person responsible for this test case.

Development class
A dialog box prompts you for the development class when you save.

Component
SAP application hierarchy component name.

Status
The status (active or inactive) is set automatically when you save.

Release

General data

Test case
Only for test cases of type ' Referring'. Specifies the test case in the target system.

Time
Estimated test case time.

Priority
Test case priority.

Test objects
Test objects can be transactions (type T), reports (type R) and function modules (type F). Enter the name of the test object in the Name field.
If the test tests several test objects, you can specify several test objects.

Restrictions

Release
If the test case is only valid for certain releases, you can specify a validity interval. If you try to run the test case in a Release which is not in the specified interval, it does not run and an error appears in the log.
When the test case is created, the current Release is entered as the lower limit. If you have made changes to the test case which are not backwards-compatible, replace this value with the last Release for which the test case runs.

Language
Flags a test case as language-dependent.
Enter the language to which the test procedure or module applies. If the test case runs in another language, it is flagged as an error in the log and it is canceled immediately.

Country
Flags test cases as country-specific.
Enter the country to which the test case applies. This flag is not checked at runtime.

Customizing
If the test case is customizing-dependent, specify the customizing required.

Database
If the test case is database-dependent, specify the database for which it was created.

Platform
If the test case is platform-dependent, specify the platform for which it was created.

Frontend
If the test case is frontend-dependent, specify the frontend for which it was created.

Use:
Areas of use of the test case.

CATT-specific

Test module
The object being created is a test module.

Termination flag
The test case terminates upon the occurrence of the first error. Otherwise it continues despite errors.
The termination flag is only effective in directly called test cases. The termination flag of the calling test case applies to referred test cases.

Context
The context-dependent definition of test procedures is relevant for collective tests ( See: Collective execution )
Set this flag if you want to specify a sequence when you call several test procedures. Enter a sequence value (1 - 4 for leaders or 6 - 9 for trailers).