By pre-defined fallbacks we mean implicit ones. For example, if you don't define a fallback, you don't need to add a test that verifies that an HTTPException is thrown, or a ResourceNotFoundException is thrown on a 404 response. jclouds already has a set of default fallbacks that throw the appropriate exception and we don't want to test that as it is already tested in jclouds-core.
However, when explicitly adding fallbacks to an API method, we need to test they're taking place. A `list` method could use the "empty list" fallback, but also the "empty paged iterable" if it is a paginated api call, so there is no real default here. If a fallback is explicitly defined (that means, the default one is overridden) then a test should be added. Makes sense? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/727#issuecomment-101798415
