‘Given’ section

'When' section

‘Then’ section

Normal

Ignored

Job is executed normally with no MettleCI no test harness intervention.

Unit Test Interception

✅ Specified

✅ Specified

✅ Specified

Interception is executed normally:

• expected output is captured to the specified output files

• source data references are irrelevant in this Job run mode.

∅ Unspecified

✅ Specified

✅ Specified

Sources are accessed without change and Job output is compared to specified Expected result.

⛔️ Specifies non-existent files

✅ Specified

✅ Specified

Causes test execution failure.

✅ Specified

✅ Specified

? Empty

∅ Unspecified

Causes test execution failure as there are no value Expected results to test against, so this is not a valid test.

✅ 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

Test is executed normally.

∅ Unspecified

✅ 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.

⛔️ Specifies non-existent files

✅ Specified

✅ Specified

Test fails to execute and Job aborts.

✅ Supplied

✅ Supplied

⛔️ Empty∅ Unspecified

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.

✅ Specified

✅ Specified

⛔️ Specifies non-existent files

Test fails to execute and Job aborts.