...
Each link is specified using a combination of stage and link properties (to uniquely identify an incoming link which supplies data to your Job) and a path property node to identify the test data CSV file containing the test data that is to be injected on that incoming link.
...
Similar to the Given section, each link in the Then section is specified using a combination of stage and link properties (to uniquely identify an outgoing link which produces data from your Job) and a path property node to identify the test data CSV file containing the test data that is to be injected on that incoming link.
Cluster keys
The cluster property node is used to assist MettleCI’s resource management when using high volumes of test data. Setting a Cluster Key will prompt MettleCI to split the actual output and expected output using multiple, smaller subsets (based on the supplied keys) before the data is compared. Data is split such that each subset will only contain records that have the same values for all columns that make up the Cluster Key. In general, cluster keys should only be used when necessary rather then being , and not specified by default. Read more about the using the cluster property node in High Volume Unit Tests.
...
You can configure as test to only compare output row counts, rather than the content of those rows, by setting the checkRowCountOnly property node to true.
| Code Block | ||
|---|---|---|
| ||
then:
- stage: Output
link: Write1
path: Output-Write1.csv
checkRowCountOnly: true |
...
You can omit selected columns from the output comparison by listing those columns them under an ignore property node for the relevant output.
| Code Block | ||
|---|---|---|
| ||
then:
- stage: Transform
link: Output
path: Transform-Output.csv
ignore:
- CREATION_DATE
- LAST_UPDATED |
...