Exactly. It is jclouds-core the one that throws the exception in the absence of a fallback. We shouldn't test that, as if at some point we change the default behavior we could end up having to update hundreds of tests in every provider. Let's avoid re-testing core behavior in concrete providers.
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/911#issuecomment-178551830
