USE:
The comparison of reference and the new document is based on table and field level. Finally, when tables are defined together with the way the definition contains tables and the logic of how rows from them the tables will be fetched, it is a time to specify fields from each table that will be compared.
PROCEDURE
...
For each step and corresponding table, the fields needs need to be specified
- Select row with a particular step
- Double click on Comparison Details
- Define a list of fields and the treatment when the difference is found. Please define for each database field following attributes:
| Description | Example | |||||||
|---|---|---|---|---|---|---|---|---|
| Line Number | Display order | 10 | ||||||
| Field name | Field of the document for which we want to define an assertion rule. | VBTYP | ||||||
Rule
| Assertion rule. Possible values: | |||||||
| The database fields are ignored while performing assertions. They are displayed in the results, but they are not marked with any color. | |||||||
| If Suppose the values within the compared database fields differ. In that case, the fields are marked with yellow color on the results screen, indicating "warning". If there are no values within compared database fields the , the fields are marked with red color indicating , meaning "error". | |||||||
| If Suppose the values within the compared database fields differ. In that case, the fields are marked with red color on the results screen, indicating "error". If there are no values within compared database fields, the fields are marked with yellow color indicating red, meaning "warning". | |||||||
| If the values within the compared database fields differ, the fields are always marked with yellow color indicating "warning". | |||||||
| always error when values are different | E | ||||||
| Mask Output | hide the field entry in test results | |||||||
| Short Description | optional description | item type |
...