|
|
|
|
|
by awj
5005 days ago
|
|
I typically go one step further in the "mocking http requests" and write a simple class that does nothing but make the http call and translate input/output. From there you can stub/mock that object as appropriate. That way you have a very simple interface to mock/stub against and don't have to worry about things like webmock. Well, at least until you start testing your http service interaction classes, but at least those are simpler and have relatively clearly defined uses. |
|