We require setting up MiniSpec and `fog` in each spec and this just
feels cleaner way of doing it.
Adding Coverage next and we don't want the code in EVERY spec.
Currently most providers used by the `fog` binary give themselves a top
level class. This has become the place a lookup table between services
and the classes which implement them.
This adds compatibility tests for the existing behaviour to allow
controlled extraction to modules.
This top level class behaviour is due to be deprecated and removed in
fog 2.0
Test for `AWS[]` was buggy and to prove it when fixed it revealed that
the `data_pipeline` service was not returning the class not an instance
of the class.
The abstraction modules e.g. `Fog::Compute` have a list of registered
providers. All of these providers should be loaded correctly when
accessed with `Fog::Service[:provider]`
These tests hit each endpoint expecting `ArgumentError` from each
provider caused by the lack of credentials.
Credentials are stubbed out to not cause false results when the test
environment does have credentials for a service.
Some services do not have requirements so do not raise the expected
error. These special cases are just asserted. If they are not loaded the
specs fail again.
Following v1.25.0, Rackspace support was extracted into a module however
it broke support to the original fog API.
The Rackspace module is currently disabled until a few key files are
replaced.
This adds tests that worked against v1.25.0 that checks that `rackspace`
is registered correctly. See https://github.com/fog/fog/pull/3326
This reverts commit 9717002fd3.
Tests were based on v1.25.0 which included Rackspace support. It was
extracted into a module and not correctly referenced so is no longer
present on master.
This commit should be reverted and the specs passing before the next
release.
