I may have missed it but I didn’t see an integration spec actually hitting the spreedly test server? 
I am concerned about everything living in a mocked world and the API changing. The spreedly gem should ideally isolate API changes (we didn’t lock the gem version though), what if something is deprecated. Managing these helper methods is not only cumbersome but error-prone, I’d rather see something like VCR that can record actual responses and use those for speed test while still doing a true integration test when needed locally and always by removing the cassettes on the CI server.