New functions in Release 4.0, 4.5 and 4.6 

New Maintenance Mode (4.6)

The new Maintenance mode apurl_link_0029_0001_0015 is a further development of the Release 4.5 Easy Mode. This maintenance mode provides CATT functionality in an environment which requires little or no training.

The user can create test cases by recording the transactions to be tested. If a transaction chain has been recorded in a test case, the user can chain the transactions together. This means that the result of a transaction can be passed to subsequent transactions.

You can also create variants. A variant is a set of runtime transaction input field values.

Field contents and error messages can also be checked against constants or parameters.

Rationalization of Variants (4.6)

The distinction between "internal" and "external" variants has been dropped in 4.6.

Extended System Message Checks (4.6)

Whereas you could previously only check the message number, you can now check all information in a message. You can specify up to three messages, of which at least one must be sent at runtime for the test to be successful, as expected system messages.

Check Field Values (4.6)

The check function checks whether the runtime value of a field is the expected value, at the end of the transaction. The check value can be a constant or a parameter (see Define field check in Maintain screen).

Read Field Values (4.6)

You define a parameter in the test case detail screen maintenance for the field which is to be read, into which the field value is put after the transaction run (see Read field value in Maintain screen).

Simulation of Controls (4.6)

The use of Custom Controls in applications requires a CATT functionality enhancement if they are to be tested with CATT. The data flows to and from Custom Controls are now recorded as well as screen input values when test cases are recorded. The data flows are those of the Data Provider and the Automation Queue.

When the test case runs, the Custom Controls are deactivated and the user actions are simulated by reading the recorded data flows.

Namespace Extension (4.0)

CATT test case names are being lengthened as part of the Basis namespace extension. At the same time CATT will switch from internal number assignment to external name assignment.

CATT test case upgrade change management (4.5B)

CATT test cases navigate through transactions in a fixed screen sequence. If the screen sequence is changed, test cases must be modified accordingly. The Change Management function has been implemented to make this easier.

Screen simulation mode (4.5)

Parameters can be maintained in screens in screen simulation mode. It allows the maintenance of nested subscreens, Table Controls and TabStrips.

Function module test (4.0)

Function modules can be tested using type F test cases. These test cases can be managed in the Test Workbench.

Waiting times in test cases (4.5B and 4.6)

You can control whether the transactions in a transaction chain run directly after one another (within a work process), or are separated by a specified waiting time (work process is released during waiting), in a parameter.

In 4.6 you can define a waiting time between screens. The waiting time applies to all background transactions. The system waits for the specified time between each screen. The waiting time depends on the number of fields transferred and the characters which they contain.

CATT mode without COMMIT WORK termination (4.0)

CATT has previously considered a transaction to be finished when COMMIT WORK was called. Transactions which contained several COMMIT WORKs could not be tested with CATT. The new CATT mode allows transactions which contain several COMMIT WORKs to be tested.

The previous mode is still supported.

Release-independent test module call (4.0)

Test cases usually use the screen definition for the transactions tested in the R/3 System which called them. This can cause problems when testing transactions in various test systems from a central System, if transactions are tested which have different screen definitions in the central System. The release-independent call function has been implemented for this case.

Making test modules and test procedures more similar (4.5)

In Release 4.5A test modules and test procedures are made more similar.

For this reason, the term test case is used in the documentation to include both test modules and test procedures. These terms are now only used where the distinction between test module and test procedure needs to be made.

Retest from the Log (4.0)

To ease the creation of complex test cases, individual test cases can be retested from the log.

When a test case is retested, its import interface has the same values as in the logged test. The retest is in a new session.

Test cases from systems with at least Release 4.5A must not be transported into systems previous to Release 4.5A.

Enhanced CATT – Initial screen with Favorites

The Favorites list is now also in Enhanced CATT as well as standard CATT: You no longer need to select subobjects such as parameters or attributes directly. . You go to the attributes with the attribute pushbutton in the application toolbar.
The Change/Display pushbuttons are now in the application toolbar in the initial screen.

Delete Test Cases

This function is under Utilities à Delete test cases in the CATT menu.

You can select test cases individually or together in the following screen. All selected test cases are listed. All deletable selected test cases can be deleted together.

The list can be longer than the screen display: Check by scrolling that only test plan logs which you want to process are selected.

 

The procedure is described in Delete test cases.

Copy test cases with references

This function is under Utilities à Copy test cases in the CATT menu.

You can select test cases individually or together in the following screen. All selected test cases are listed and they can be copied together. The names of copied test cases can be changed.

The procedure is described in Copy test cases.

Process CATT test plan logs in groups

You can now process several CATT test plan logs together. You can now select logs to be processed in the Enhanced CATT overview list. You can choose individual test cases or all of them. You can also deselect all. You can process all selected logs together, e.g. assign expiry date, flag for archiving or delete.

The list can be longer than the screen display: Check by scrolling that only test plan logs which you want to process are selected.

 

The Enhanced CATT test plan log list now contains a column B which shows which CATT test cases ran in the background: They can be used for validation because they were certainly not changed at runtime.

The procedure is described in Process logs in groups.