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 | ETVO_NAME_DE |
| Short Description | Validation Object |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ETOBJ_NAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | Validation |
| Medium | 20 | Validation Object |
| Long | 30 | Validation Object |
| Heading | 30 | Validation Object |
Documentation
Definition
A validation object is a persistent eCATT object with a reference to a validation implementation. In the case of the implementation type eCATT, this implementation is a normal eCATT test script.
The point of a validation object is to give the tester a possibility to separate the coding for the validation of a test from the normal business test coding. This also gives the tester the possiblity to reuse this validation object flexibly whenever the corresponding validation is to be executed.
The parameters of the validation objects are taken from the parameters of the implementation of the validation object. Therefore, they are displayed in the validation object but cannot be changed there. They can only be changed in the implementation of the object itself.
The result of an execution of a validation object can be classified using business messages, that can be assigned to the three possible results of a validation object. These three results are PASS, FAIL and TECHNICAL ERROR.
Business Messages:
Generally a validation is carried out to verify a certain functionality of the tested application.
To assign a business context to the results of a validation object, you can bind these results to translatable business messages.
The execution of a validation object leads to the possible results PASS, FAIL, and TECHNICAL ERROR.
In the business message ALV grid, the appropriate business messages can be assigned to these technical results.
During play-back, the business message that corresponds to the status of the validation object is displayed in the eCATT execution log.
Types of Business Messages:
In validation objects, T100 and OTR messages can be used.
How do I assign business messages to the various statuses?
1. T100 Messages:
A T100 message is unambiguously identified using the message class and the message number. The message class is used to classify a group of messages. A message number unambiguously identifies a certain message in a message class.
Both these identifiers must be specified in the "Message Key" column, in the format <message class>: <message number>. The colon serves to divide the message class from the message number.
The creation of and navigation to T100 messages is supported by double- click on the corresponding ALV grid cell.
2. OTR Messages:
ORT messages that already exist can be assigned to a status by entering the unique ID of this message in the "Message Key" column. Navigation to an OTR message is supported by double-click on the corresponding ALV grid cell. The creation of OTR messages is not supported, existing messages can be edited however.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 710 |
