Kontakt

Ansicht
Dokumentation

RSSTARWC - CATT: Prepare collective test

RSSTARWC - CATT: Prepare collective test

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Description

You can execute CATT mass tests using this report. Only CATT procedures, not test modules, can be selected because the successful execution of test modules generally requires certain customizing settings which need not be present. If you want to execute the test modules on their own, you can do so in the CATT transaction SCAT.

The selection screen first offers you a list of CATT procedures by test procedure number, component, person responsible, context, language, country, and creator or changer.
The selection Component assignment combines the 4.0B selection fields Application, Subapplication and Component. The three values are now combined in one field, connected by '-'. If the selection is restricted to e.g Application and Subapplication, enter 'AP-SUB*' in the new component assignment selection field.

  • Use
If only the field No restrictions is marked in this group, test procedures are selected independently of the use specified in the 'Use' attribute.
The use in the attributes can be selected from the fields Individual test Application test and Platform test.

  • Test status
You can also choose only those CATT procedures which have or have not a test status, or select by Test period or Test system in which the selected test status was assigned.
If the test status was not assigned to a CATT procedure within the specified period, this CATT procedure is not selected.
If you want to select CATTs independently of their test status, you must enter "*" in the 'Test status' field and clear both test period fields. The test status is stored in the table CATQ.
You can call the program RSCATPRF, which lists the test status of a procedure, via the 'Test status' function in the test case attribute 'Extras' menu.
The status of a procedure can be PASS, FAIL or untested.
In this program, the test status "untested" is indicated by no test status entry. If you enter PAFA, all CATT procedures which passed or failed a test, but not untested ones, are selected.
Procedure variants also have a test status, which are taken into account when the with variant test status flag is set. The resulting global test status is determined as follows: If the default parameter set or an active variant has the status "untested", the whole procedure is "untested". If the procedure is not "untested", the procedure has the status "FAIL" if the default parameter set or at least one variant is a "FAIL". Only if the default parameter set and all variants are "PASS" is the global test status "PASS". The global test date is then the test date of the variant (or default parameter set) which determined the global test status. In the case of several such dates, the oldest is chosen. If the with variant test status flag is not set, the test status of the default parameter set and its test date apply.

  • Variants
If neither of the two flags is set, only the default parameter set is executed for the selected procedures. By marking the Execute all variants as well flag, all active variants of the selected procedures are executed, as well as the default parameter set. If the Only execute variant xx flag is set, only procedures for which variant xx is active (xx is a variant ID) are selected. In this case, only the selected variant is executed, not the default parameter set. Executing one selected variant for all selected procedures is useful if parameters represent classifications, e.g. by country or trade, and all selected procedures have this special parameter set in the same variant number.

  • Sequence control
If the user does not agree with the proposed sequence, he or she can enter a value between 1 and 4 in the CATT attribute field Context. 1 is the first header step, and 4 the last. For the trailer, values between 6 and 9 can be assigned. These CATT procedures are then executed before or after the selection respectively.
Only one of the 4 sequence controls offered should be selected. Otherwise an error message is issued.
  • If no sequence is chosen, all CATT procedures are chosen according to the selection made. If these include CATT procedures with a header or trailer, it is taken into account in the execution sequence.

  • If the Total heaer/Total trailer field is marked, all CATT procedures which have the header flag 1 or 2 or the trailer flag 8 or 9 are included additionally, regardless of the selection made.

If CATT procedures with header values 3 or 4 are to be selected, they must satisfy the selection conditions.
  • If the Without Header/Trailer field is marked, all CATT procedures with a header or trailer flag are removed from the selection. Only CATT procedures without context flags remain.

  • If the Only select header field is marked, only CATT procedures which satisfy the specified selection conditions, and have a header flag, are selected.

  • If the Only select trailer field is marked, only CATT procedures which satisfy the specified selection conditions, and have a trailer flag, are selected.

  • Processing
If the List processing desired field is marked, the user can still remove CATT procedures from the mass test execution selection made.
Marking the with run-time statistics button causes a minimum, average and maximum run-time to be output for each CATT procedure. These data result from timings made during previous executions of the CATT procedures in the current system. Variants are not taken into account in the run-time summation of all selected procedures. The same applies to procedures which have never, or not recently, been executed in the current system. They are classified as 'new'.
The with termination flag field specifies that the termination flag is always set, regardless of the values in the individual procedures. A procedure is terminated the first time that an error occurs, and all transactions run in the 'Background'.
The For archiving field specifies whether the logs created are flagged for archiving. Until 4.0B this was linked to the assignment of the test status, but is now independent. Check that 'Long log' is set, as the log type is also now independent of archiving.
In Log, you can choose between a "Long log", a "Short log" or no log.
A "Long log" is indicated by L, a short log S. The default value set by the system is S. If no log is to be output, the entry S must be removed.
Processing modes can be "Foreground", "Background" or "Background until first error message".
"Foreground" is A, "Background" N and "Background until first error message" E. Other possible entries are X for 'Asynchronous update' and Y for 'Synchronous but not local'.
You can make entries to find the log later in the log history in the Procedure and Short text fields.
You can specify in the Maximum run-time in minutes field, how many minutes run-time should be allowed for the execution of the chosen CATT procedures.
If the minute limit is reached, the current CATT procedure is completed normally and only then is the mass test ended. Subsequently scheduled CATT procedures are no longer executed.
The field is empty by default. This means that there is no run-time restriction.
Another R/3 System can be specified as remote call destination in the RFC destination field. It overwrites any destination in the user parameter RFC ID. To deactivate an RFC ID for the current run , i.e. run locally, enter the destination 'NONE'.

Requirements

Test statuses can be assigned, but require authorization.

Output

Example






BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 9662 Date: 20240601 Time: 211647     sap01-206 ( 177 ms )