SAP ABAP Data Element TWB_TYP (Test case attributes: Type)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-TWB-ORG (Application Component) Test Organizer
     S_TWB (Package) Test Workbench
Basic Data
Data Element TWB_TYP
Short Description Test case attributes: Type  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type TWB_TYP    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Type 
Medium 15 Type 
Long 20 Attributes type 
Heading 15 Attributes type 
Documentation

Definition

Test case type:

C automatic CATT
F function module test
L referring test case
M manual test case
R remote test in an R/2 System
S training sytem test case
X external application test

Supplementary Documentation - TWB_TYP 0001

Use

Test function module using CATT

Use

You can create and run function module tests with type F. Function module execution dialogs can also be tested.
When you create a function module test, a parameter set for the parameters, structures and tables to be passed is created. Then the function module is executed. If it contains dialogs, they are recorded. When the function module has run, its result is added to the function module parameter set as comparison parameters. Parameters, structures and tables whose contents should be the same in future tests can then be selected from the comparison parameters.

Procedure

  1. Create a function module test.
  2. Parameterize the function module test case if it contains dialogs.
  3. Edit the list of compare parameters.
  4. Save the test case.
  5. Use the test case to automatically test function modules

Create function module test

Procedure

  • Create a type F test case:
    • Choose 'Record function module' in the CATT maintenance transaction initial screen.
    • Create a new type F test case in the Test Workbench and choose Record.
  • Enter the name of the function module in the dialog box and choose Copy.
  • Pass test execution values to the function module import, changing and table interface.
  • Execute the function module.
  • If the function module contains dialogs, perform them.
  • The result is returned at the end of the function module. You can choose which comparisons are to be performed for later function module tests by selecting thei entries. The current result is the reference value.

Function module test parameterization

You can only parameterize function modules which perform dialogs, and you can only parameterize the dialog entries.

Procedure

  • Go to the functions of the type 'F' test case.
  • Position on the name of the function module to be tested and choose Select.
    You go to the overview of the dialog screens.
  • Position on one screen and choose Select.
    The simulated screen is displayed.
  • Maintain parameters as described in screen maintenance.
  • Save your chabges.

Edit compare parameters

The tested function module returns a result via its interface (export, changing, tables) after the function module test. You can compare this result with a set of compare parameters. If there is a difference between compare parameters and the function module test result, the test is flagged as fail.
If you do not want to use all compare parameters for the result comparison, you can exclude some.

Procedure

  • Go to the type 'F' test case functions.
  • Choose Compare parameters.
    The compare parameters are listed.
  • Mark the result parameters (export, changing, tables) which are to be compared with the result of the function module test by positioning on the parameter name and choosing Select/Deselect.
  • Save the changes.

Supplementary Documentation - TWB_TYP 0002

CATT-Type L - Referring test case

The test case refers to another test case, which is generally not in the same system.

A referring test case can only be called from the Test Workbench. A direct call is not possible.

The test case which is to be assigned must be specified as referred object in the attributes of the referring test case in the general data.
The referring test case should have the same attributes as the referred one.

Central test management

Referring test cases are place holders in a test management system for test cases which are in another system, the CATT system, in which they are to run.
The CATT functions to be performed can run remotely in a third system, the test system.
Status management is performed in the test management system.

Test management system

The Test Workbench with all its functions is used in the test management system. Type L test cases are put in test catalogs, plans and packages as referring test cases, with all attributes.

The remote REF destination must identify the CATT system in a test plan or package attributes parameter

CATT system

The test cases whose names are in the test management system place holders are called in the CATT system, possibly with specified variants (incl. generic and external variants). The variants are identified in the test management system in placeholder variants with the same names.

Test system

The CATT functions in the calledtest case, in particular transactions, function modules and table checks, run in the test system. This is by default the CATT system.
The CATT system can use the standard remote functionality. The remote destination must be in the CATT system to access the test system. It can be specified in the test management system when the test plan or catalog runs, in the 'Remote' function in the dialog box.

Release restrictions

The test management system must be at least Release 4.5B.

The CATT system must be at least Release 3.1H.

To pass a variant, the CATT system must be at least Release 4.5A.

To use the internal remote destination, the CATT system and the test system must both have Release 3 or both have Release 4. From the application perspective, they should have the same Release.

Supplementary Documentation - TWB_TYP 0003

Use

Test case with long documentation

Procedure

Examples

Dependencies

Supplementary Documentation - TWB_TYP 0005

Use

System installation training test case. The additional maintainable attributes specify the installation environment, and are specially designed for the SAP training course.

Procedure

Examples

Dependencies

History
Last changed by/on SAP  20130604 
SAP Release Created in