Rules for creating and maintaining test cases (SAP Library

Rules for creating and maintaining test cases

Using parameters in application-independent test cases

Note:

Constants can only be assigned to standard delivery customizing objects (never to date fields or master record or document numbers).
When test cases are changed, the parameter set can be extended, but not moved or reduced, to retain upwards-compatibility. The change is made by the person responsible.

Language-independence

To minimize the number of test cases required, they must be created without language-dependent elements (Fast Path, language-dependent function codes). Text variables must be used for language-dependent fields ( See also: Text variables).

The text variable table is connected to the translation tool.

To ensure the language-independence of measurement units, use constants, variables or a parameter as input values.

Do not use text variables &Txx for measurement units.

The value must always be specified in the test case original language. If a test case does not run in its original language, the conversion exit CUNIT translates language-dependent measurement units input in screens into a language-independent internal format and then back into the execution language. CUNIT uses standard SAP conversion function modules.

Test case documentation

Describe the test case (use of variables, data passing) in the function part, using the TXT function.

You can create a long text for more detailed documentation:

Go to the CATT maintenance transaction. Go to change mode. Choose Goto ® Long text in the attribute, function and parameter maintenance screens.

You go to the documentation editor with standard header variables. (They are replaced by logon language texts for display.)

Enter header texts. Get empty lines for input with Insert (F5). Leave insert mode with End insert or F5.

Save your entries.