Using spec form is going to be the standard way to testing (but relying
on asserts). This update allows the test(s) to be picked up by the main
rake task again.
If you use the supported means to create services such as:
Fog::Service.new(:provider => "Example")
It already loads the contents of `~/.fog` and filters the values based
on if they are recognised or required.
That means in a number of services that are initialising based on
`options` or a value from `Fog.credentials` both are the same.
The `options` should have been loaded and merged from credentials in the
service "builder".
This isolates the tests from the values in `Fog.credentials` which is
based on the contents of `~/.fog`
Underlying problem is that the code (and many others) rely on the Fog
global making it too tightly coupled to the environment hence having to
stub.
Full issue: https://github.com/fog/fog/issues/1390
This will probably be a repeating pattern we need to work on to DRY up
so every test from every provider doesn't include this setup workaround.
