Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-TWB-TST-ECA (Application Component) eCATT Extended Computer Aided Test Tool⤷
SECATT_DDIC (Package) eCATT ABAP Dictionary Objects
Basic Data
| Data Element | ETSHORTLOG_MODE |
| Short Description | eCATT - Mode for Short Log |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ETSHORTLOG_MODE | |
| 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 | LogDetails |
| Medium | 20 | Log Details |
| Long | 30 | Mode for Log Details |
| Heading | 40 | Mode for Log Details |
Documentation
Log Mode
Settings for the eCATT log for test execution.
Use
This setting defines which test execution data is written in the eCATT log.
The option "Complete Log" is required for a comprehensive and easy to follow automated test.
A complete logging can require increased storage space if there is a high number of automated tests and frequent test execution. Use simplified log versions to avoid unnecessarily logged details in eCATT logs. These options cause a logging skip for many eCATT commands; as long as the test result is positive. If the test result is negative, the affected test is automatically switched to "Complete Log".
Tests with positive results are possibly no longer comprehensible with the eCATT log because of simplified logs in their test procedure.
Possible settings:
[SPACE] - Complete Log
All executed eCATT commands are logged completely with all details.
S - Short Log
Only block commands and further selected commands are written in the log. The eCATT log data for the current test variants is buffered during the test execution in the transaction memory SECATT. In the case of the test result FAILED, the entire log of the affected variant is written up to the error.
The following types are logged:
- Test configurations with system data and start options
- Test script with variants and IMPORT/EXPORT
- FILL_RDC
- REF / REFCATT / REMOTECATT / REFEXT / VALIDATE each with IMPORT / EXPORT / RDC
- MESSAGE / ENDMESSAGE
- PERF
- IF / ELSE / ELSEIF
- DO / LOOP
- STORE / RETRIEVE / DELSTORE
- LOG / LOGMSG / LOGTEXT
T - High-Level layout
Only the highest level of the eCATT log is written.
In the case of a test result FAILED, the entire log of the affected variant is written up the error.
The following types are logged:
- Test configurations with system data and start options
- Test script with variants and IMPORT/EXPORT
X - Short log without error option (as S)
In the case of a positive test result, this option works like option S.
Unlike with option S, the eCATT log data is not buffered in the transaction SECATT at runtime, therefore it is not possible to write a complete log in the case of an error.
Y - High-Level Log without error option (like T)
In the case of a positive test result, this option works like option T.
Unlike with option T, the eCATT log data is not buffered in the transaction SECATT at runtime, therefore it is not possible to write a complete log in the case of an error.
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 711 |
