At the moment the config file location is hard-coded to a location under spec/integration with no override which would make it easy to accidentally clobber it, e.g. with a git reset --hard.

alphagov/vcloud-launcher@c51acf9#commitcomment-6319859

At the very least an override should be allowed.

If the location is changed, the Jenkins scripts will have to be updated as well.

This is not a vCloud Tools Tester issue, as that just takes a config file. The issue is one in each of the integration tests and the integration test instructions. However, raising it here it is to do with use of this tool, to avoid unnecessary duplication.

While upgrading vCloud Tools Tester to use vCloud Core's new ApiInterface.rb rather than Vcloud::Core::Fog::ModelInterface directly, we found that the fixture_parameters_spec.rb was hard to update because it uses stub_chain. It looks like to use the API interface we'd have to work out the order of methods called and stub those in order, thus defeating the purpose of having an API interface.

We have left it as is for now, but would like to find a way to test this without tying the test so closely to the exact implementation of vCloud Core fog code and fog code itself.

#16 means that the integration tests now fail fast if a required test parameter has not been supplied.

It would be useful if the documentation could somehow link to the parameters so that we have 'living' documentation.

Ideally without referring to line numbers in files, which would be very brittle.

Hi all,

I need the v0.3.0 release of this for the vcloud-disk_launcher PR i'm putting together.

Is there any reason why is hasn't been tagged and published as a Gem?

Cheers!