
In Release 4.6C, mainly ergonomic changes have been made to the Test Workbench. Some urgently-required new functions have been added.
You can make the execution of CATT functions
dependent on the value of a variable in extended CATT mode by defining a
condition. The CATT functions between IF and ENDIF are only executed if the
condition is satisfied.
In Release 4.6C you can make the execution of functions dependent on
alternative values of the variable with ELSEIF.
You can specify the execution of CATT functions for the case that the value of
the variable satisfies no condition, with ELSE.
The CATT test plan log now indicates which
screens were actually processed in the test. They are printed in black, those
not processed are in blue/gray. You can now see how far the test got, or
whether any screens were missed.
This new function is particularly for error messages such as 'Data not found
for screen XX'.
In CATT Easy Mode (SCEM) a message screen with
the transaction result is created at the end of a transaction.
This message screen SAPMSCEM 0001 is now also the last screen in recording in
Extended CATT (SCAT). It contains the last message in the transaction. You can
define checks against these messages beyond the previous CATT function CHEERR
(check error).
The Favorites are now in Extended CATT as well as in CATT, so you no longer need to select subobjects such as parameters or text variables directly. The Attributes and Change/Display pushbuttons are now in the application toolbar in the initial screen.
You now also go to the attributes in CATT Easy Mode with the Attributes pushbutton in the application toolbar.
RSCATDELETE is a report to delete test cases in Extended CATT. It is within limits release-independent. It is called with the transaction SE38. All selected test cases are listed. You can delete all deletable selected test cases together.
RSCATCOPY copies test cases in Extended CATT. It can be called with SE38. You select test cases which are then copied. You can change the names of copied test cases.
You can process several CATT test plan logs at the same time. You select some or all logs to be processed in the Extended CATT overview list. You can also deselect all. All selected logs can be processed together, e.g. they can be given an expiry date, flagged for archiving or deleted.
The CATT test plan log overview list in Extended CATT now has a column B which indicates which CATT test cases ran in the background. They can be used for validation because they cannot have been changed during the test.
You should now also check messages in the R/2
System with the screen SAPSCEM0001, particularly if the expected message
numbers are between 001 and 010 because these numbers are also used for system
errors with the message ID (work area) TT. In such cases a transaction with
errors could be passed as 'OK' if the numbers are checked without message
ID.
You should put the message screen SAPMSCEM 0001 at the end of the screen list.
Define the check for message number and work area in this screen. This
replaces Check Error, which only checked the message number, with a combined
check of message number and work area.
You can analyze Several test plans together in
the test plan organizer. The reults are displayed in the ABAP List Viewer
(ALV) since Release 4.6A. The result of the latest status analysis is
displayed. More recent test package processing is not taken into account.
The status info system list has a new field 'Result obsolete'. An exclamation
mark in this field for a test plan indicates that the status analysis is based
on obsolete results. The flag is created by the tester when the status is
set.
To refresh the analysis, the test organizer chooses Refresh. Each new analysis
is also a refresh.
The tester worklist is displayed as an ABAP List Viewer (ALV) list. The user can define his or her own worklist display format, showing and hiding fields in the list.
When the test organizer assigns a test package
to a tester in the test package management, a green flag in the test package
tells the test organizer that the test package has been assigned to a tester
and released. The test package is visible in the tester's worklist.
The release can be withdrawn without deleting the assignment. The tester no
longer sees it in his or her worklist until the test organizer releases it
again. The lock is indicated by a Stop sign in the test package
management.