jsonschema - test summary
jsonschema failed tests
Some validators have deliberately chosen not to support parts of the spec. Go to the jsonschema homepage to learn if
that is the case for these tests.
| test failed | reason |
|---|---|
contains keyword validation, array without items matching schema is invalid |
Expected result: false but validator returned: true |
contains keyword validation, empty array is invalid |
Expected result: false but validator returned: true |
contains keyword with const keyword, array without item 5 is invalid |
Expected result: false but validator returned: true |
contains keyword with boolean schema true, empty array is invalid |
Expected result: false but validator returned: true |
contains keyword with boolean schema false, any non-empty array is invalid |
Expected result: false but validator returned: true |
contains keyword with boolean schema false, empty array is invalid |
Expected result: false but validator returned: true |
items + contains, matches items, does not match contains |
Expected result: false but validator returned: true |
items with boolean schema (false), any non-empty array is invalid |
Expected result: false but validator returned: true |
items with boolean schemas, array with two items is invalid |
Expected result: false but validator returned: true |
all integers are multiples of 0.5, if overflow is handled, valid if optional overflow handling is implemented |
Expected result: true but validator returned: false |
validation of date-time strings, a invalid day in date-time string |
Expected result: false but validator returned: true |
validation of date-time strings, an invalid offset in date-time string |
Expected result: false but validator returned: true |
validation of IPv6 addresses, leading whitespace is invalid |
Expected result: false but validator returned: true |
validation of IPv6 addresses, trailing whitespace is invalid |
Expected result: false but validator returned: true |
validation of IPv6 addresses, zone id is not a part of ipv6 address |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (~ not escaped) |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (URI Fragment Identifier) #1 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (URI Fragment Identifier) #2 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (URI Fragment Identifier) #3 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (some escaped, but not all) #1 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (some escaped, but not all) #2 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (wrong escape character) #1 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (wrong escape character) #2 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (multiple characters not escaped) |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (isn't empty nor starts with /) #1 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (isn't empty nor starts with /) #2 |
Expected result: false but validator returned: true |
validation of JSON-pointers (JSON String Representation), not a valid JSON-pointer (isn't empty nor starts with /) #3 |
Expected result: false but validator returned: true |
format: uri-template, an invalid uri-template |
Expected result: false but validator returned: true |
validation of URIs, an invalid URI with comma in scheme |
Expected result: false but validator returned: true |
base URI change - change folder, number is valid |
Expected result: true but validator returned: "no such schema <http://localhost:1234/folderInteger.json>" |
base URI change - change folder, string is invalid |
Expected result: false but validator returned: "no such schema <http://localhost:1234/folderInteger.json>" |
base URI change - change folder in subschema, number is valid |
Expected result: true but validator returned: "no such schema <http://localhost:1234/folderInteger.json>" |
base URI change - change folder in subschema, string is invalid |
Expected result: false but validator returned: "no such schema <http://localhost:1234/folderInteger.json>" |
All other tests passed.