...
| Code Block | ||
|---|---|---|
| ||
when:
job: KeyGeneratorExample # The DataStage Job with which this test spec is associated
parameters:
DSJobStartDate: 2012-01-15 # Run the test using this value for the DSJobStartDate macro
DSJobStartTime: 11:05:01 # Run the test using this value for the DSJobStartTime macro
paramStartKey: 100 # Run the test using this value for the paramStartKey Job parameter
|
From Unit Testing Surrogate Key Generator Stages - MettleCI Documentation - Confluence (atlassian.net) …
Then
The then section associates unit test data files with each of your Job’s input links.
...
Job Run Mode | Test Specification ‘Given’ section | Test Specification 'When' section | Test Specification ‘Then’ section | Description |
|---|---|---|---|---|
Normal | ||||
Ignored | Job is executed normally with MettleCI no test harness intervention. | |||
Unit Test Interception | ||||
✅ Specified | ✅ Specified | ✅ Specified | ||
? Empty | ✅ Specified | ✅ Specified | Fail? | |
⛔️ Specifies non-existent files | ✅ Specified | ✅ Specified | ||
✅ Specified | ✅ Specified | ? Empty | Fail? | |
✅ Specified | ✅ Specified | ⛔️ Specifies non-existent files | Re-baseline’s expected test output. See Capturing a Baseline Test Result. | |
Unit Test Execution | ||||
✅ Supplied | ✅ Supplied | ✅ Supplied | ||
⛔️ Empty | ✅ Supplied | ✅ Supplied | No input test data specified so the Job’s normal input operations are permitted to read from upstream data sources. Output is compared to an expected output test data file. See an example here. | |
✅ Supplied | ✅ Supplied | ⛔️ Empty | Input test data is injected into your jobs but no output test data is supplied for comparison so the Job’s normal output operations are permitted to write to downstream data stores. No output comparison is performed. | |
Test specification. patterns
| Include Page | ||||
|---|---|---|---|---|
|