At present the The MettleCI automated unit test specification generator does not completely will handle input/output stages within local containers but not shared or local containers. The yaml specification it generates containers. Due to the design time information available for a job, test specifications generated for jobs using shared contains will have the inputs and outputs for the job modeled correctly but it will omit any inputs or outputs that are within shared containers. The unit test harness can handle inputs/outputs contained within containers, but we must modify the yaml by hand to include these inputs and outputs. They go in the usual place (given: for inputs and then:for outputs) but with names that disambiguate the links and stages referenced.
...
were added to the generated yaml. In each case the stage name has been prepended with OrderAddressC1. because that is the name of the container invocation. This ensures uniqueness across all container invocations in the job. (global uniqueness) The link names do not need this disambiguation as they are already scoped to the source/target stages. The path (name of the csv file) can be anything you like. We chose a name that shows the connection ( container-stage-link.csv ) but we did not have to.
Here is a successful test run
...
Note: this example is worked using uses shared containers but the process is exactly the same for local containers. The invocation name of the container is prepended to any stage names that need disambiguation, and everything else is done exactly the same way.
...