Page Comparison

...

Here’s an example of a fully qualified stage name:

Job MyJob Image RemovedImage Added	Unit Test Specification Code Block language yaml given: - stage: sqAccounts link: inAccounts path: GivenAccounts.csv when: ... then: - stage: ContainerC1.sqAccounts link: out path: ExpectedAccounts.csv
Shared Container scWriteAccounts Image RemovedImage Added

Since the output sqAccounts stage is within ContainerC1 its full qualified stage name is ContainerC1.sqAccounts (line 8) and the Unit Test Spec is no longer ambiguous. When working with Shared Containers the <container name> within a fully qualified stage name refers to the stage name in the parent Job (ContainerC1) rather than the Shared Container itself (scWriteAccounts).

...

Once a MettleCI Unit Test Spec is adequately configured (with correct Shared Container references, if required) then the MettleCi MettleCI Unit Test Harness can correctly handle input and output stages within Local and Shared Containers.

...