Merge pull request #656 from s0undt3ch/develop

Handle provider entries in the configuration which are just used as data holders
And we now have a working test suite to start testing salt-cloud. Still lots to do!!!
I don't imagine getting that many and/or different `cli` tests.
Hurray for tests!!! These weren't exclusive options anymore.
Compare against the default instead.
Let's start making Travis-CI test salt-cloud!!!
Create a master and cloud temporary configuration at runtime.
Add tests for mutually exclusive options.
Execute the tests suite on the checkout directory.
We need `swig` to build M2Crypto which is needed for Salt.
Add `tests_require` if setup tools is being used.

Changed how tests are executed from setup to see if coverage reports show relative filenames.
Use the defined `SALTCLOUD_ROOT` as the source parameter for the coverage call.
We don't want the tests in the coverage report.
The salt-testing project changed ownership. Update references.
Fix the tests require entry in setup.
Merge pull request #663 from s0undt3ch/features/unittesting

And now salt-cloud has unittesting. Let's create some more tests shall we!!!