-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for an error response #6
Comments
yep exactly. Maybe first steps would be to at least expose the server instance so you could use it('should have heading', function(done) {
forceRouteError('get', '/contact/:id', {errors: data}, [optional error code]);
...
}); |
2887721 closes |
This is in master, and I'll push out a new release soon. I was thinking of coming up with a new api but the existing route api is good enough, because you'll need to be able to customize the error response. Check out Acceptance-testing#verb in the wiki for an example. |
Thanks heaps @samselikoff |
Is there a way to handle testing and error response from the server.
Adding an api that could be used in a test that returns an error for an api resource would be helpful.
I see that you are have this as a todo.
The text was updated successfully, but these errors were encountered: