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.
All these changes should now be made @mattbostock :)


On Tue, Oct 7, 2014 at 9:44 AM, Matt Bostock <notifications@github.com>
wrote:

> In spec/vcloud/tools/tester/test_setup_spec.rb:
>
> > @@ -33,7 +33,7 @@
> >
> >    it "calls the appropriate methods" do
> >      expect(Vcloud::Tools::Tester::UserParameters).to receive(:new).with(example_filename, expected_user_params)
> > -    expect(Vcloud::Tools::Tester::FixtureParameters).to receive(:new).with({})
> > +    expect(Vcloud::Tools::Tester::FixtureParameters).to receive(:new).with({}, expected_user_params)
>
> Should this read expected_params?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/gds-operations/vcloud-tools-tester/pull/27/files#r18506976>
> .
>