Make network fixture management optional.

Whilst developing the integration tests for the vcloud-disk_launcher tool, I discovered that I would need to reference the 'network_1' and 'network_2' parameters, even though I did not need them for my tests.

This PR aims to fix that - so that the network fixtures will only be compared and created by vcloud-tools-tester if they are specified in the expected_user_params array passed into TestSetup.

This also means that this logic can be triggered on a per-integration-test basis too -- I have previously been bitten by this when writing the vCloud Core IndependentDisk class integration tests.
I just wanted to document (& of course test) the change in behaviour. Happy
to remove though.


On Mon, Oct 6, 2014 at 11:11 AM, Matt Bostock <notifications@github.com>
wrote:

> In spec/vcloud/tools/tester/test_parameters_spec.rb:
>
> > @@ -50,8 +50,8 @@
> >
> >      context "no fixture parameters passed in" do
> >        let(:fixture_params) {{}}
> > -      it "raises an error if it receives no fixture parameters" do
> > -        expect{ parameters }.to raise_error("No fixture parameters received")
> > +      it "does not raise an error if it receives no fixture parameters" do
> > +        expect{ parameters }.not_to raise_error
>
> It there value in retaining this test? It might be confusing to someone
> new to the project so I'm not sure if it's worth keeping (though it would
> have been useful during development).
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/gds-operations/vcloud-tools-tester/pull/27/files#r18449127>
> .
>