-
Notifications
You must be signed in to change notification settings - Fork 66
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
Response matching needs to support default
responses
#86
Comments
@harrisj thanks for reporting this. This does seem like a bug. Beyond the @jreece1567, @gwshaw any thoughts on this issue. |
having the same problem as well, hard to round out a test suite without support for default! |
"Response matching needs to support 'default' responses"; see: westfieldlabs/apivore#86
Currently, explicit spec validation using the
expect(subject).to validate
method will not work withdefault
response types because the validator converts the argument to an int and then the checker converts back to a string (so'default'
becomes0
becomes'0'
)The text was updated successfully, but these errors were encountered: