Schema check crashland #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds jsonschema tests to all test cases, without bringing these checks into the normal server or client code at runtime. It works by creating a MITM proxy server that inspects all JSON and CBOR traffic on the way past, validating against either a request or response schema. The schema check needs a little more work: * Requests/response inspection is only skin deep - it does not check, for example, metadata descriptions * Error returns when schema checks fail are piped through the proxy's HTTP response to the server - which is fairly cheeseball
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds jsonschema tests to all test cases, without bringing these checks into the normal server or client code at runtime. It works by creating a MITM proxy server that inspects all JSON and CBOR traffic on the way past, validating against either a request or response schema.
The schema check needs a little more work:
Requests/response inspection is only skin deep - it does not check, for example, metadata descriptions
Error returns when schema checks fail are piped through the proxy's HTTP response to the server - which is fairly cheeseball