News for hackers. Stuff that matters.
Re:Mock your HTTP responses to test your REST API by untog on Friday May 03, 2013 @12:33PM (#5650966)
It's a nice idea, but relying on a remote service for testing makes me worry. I tend to mock HTTP responses locally, so that the tests can run when there isn't even an internet connection available.
Re:Mock your HTTP responses to test your REST API by jrochkind1 on Friday May 03, 2013 @12:38PM (#5650995)
I use ruby [vcr](https://github.com/vcr/vcr) to mock responses. But ordinarily it 'records' an actual HTTP interaction, to play it back latter mock. If you want to mock something you don't currently have conveniently 'live' to record, you can try to write up the serialized recorded request by hand -- but it'd be a lot easier to use this service to mock up a request, then record it with VCR so subsequent test runs don't go out to the network.

I plan to do some of that, as needed. Convenient.

Re:Mock your HTTP responses to test your REST API by yotsumi on Friday May 03, 2013 @12:42PM (#5651014)
Yes, you are absolutely right. But sometimes is a good idea to test somes WS requests across all the network, in addition of your locally mocked tests.
Re:Mock your HTTP responses to test your REST API by johns on Friday May 03, 2013 @12:46PM (#5651040)
What do you use for your local testing?
Re:Mock your HTTP responses to test your REST API by fein on Friday May 03, 2013 @02:46PM (#5651831)
Telnet when I'm lazy or its quick, curl when I actually want to write a full harness.