Skip to content
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

Enable logging of expected failure cases (JSON Parseable 400s) #19

Closed
twohlix opened this issue May 24, 2017 · 1 comment
Closed

Enable logging of expected failure cases (JSON Parseable 400s) #19

twohlix opened this issue May 24, 2017 · 1 comment

Comments

@twohlix
Copy link

twohlix commented May 24, 2017

It would be useful to document expected failure cases, 400 errors, and their response bodies.

Maybe with a required (in rspec for example) document: true declaration on the test.

@twohlix
Copy link
Author

twohlix commented May 24, 2017

Just figured out that this isn't happening in my project because the error body isn't constructed in the controller action under test, its constructed by a responder and the body is blank for avocado during its json? check so it will never document.

@twohlix twohlix closed this as completed May 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant