-
Notifications
You must be signed in to change notification settings - Fork 40
Default mocking breaks integration tests #52
Comments
@clemenshelm - hmm. My expectation is definitely that you would still have to opt-in to mocking, generally by passing |
@geemus No, not that I know. Actually your readme even says:
|
@clemenshelm - true, that is just meant to be for running the tests of this project itself though (not projects that include this). Similar to your earlier suggestion, this behavior is caused by our test_helper here: https://github.com/heroku/heroku.rb/blob/master/test/test_helper.rb#L9 |
Ok, thanks for the info! I’m still not sure what’s causing this, the problem just appeared when I updated from |
@clemenshelm - do let me know if you find it. A bug on my end is certainly possible, but I definitely didn't make it mock-by-default on purpose. |
I just updated to version 0.3.9 of your gem and after a debugging session I finally discovered that from now on you mock requests when running tests.
Could you at least output a warning saying that requests are mocked? It was really hard for me to figure out what’s actually happening.
In my opinion even better would be to make mocking optional. It shouldn’t be a problem for anyone to define that behavior in their
spec_helper.rb
or wherever they need it.Thanks a lot!
The text was updated successfully, but these errors were encountered: