JSON-Schema-Test-Suite
JSON-Schema-Test-Suite copied to clipboard
A language agnostic test suite for the JSON Schema specifications
Hi. I'm working on a schema validator for C using json-c. It's called jsonc-daccord. Currently I'm running my test runner on the Test Suite [tests/draft2020-12/patternProperties.json](https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/main/tests/draft2020-12/patternProperties.json), I noticed that it does...
This adds tests using the meta-schema as a schema. This does not test things that cannot currently be guaranteed to be represented in a schema, for example, normalized URL requirements...
This is a little vague in the spec, as discussed in https://github.com/json-schema-org/json-schema-spec/issues/810, but will be clarified in a bug fix and we should go ahead and test for it from...
[§4.2.2 of the specification](https://json-schema.org/draft/2020-12/json-schema-core.html#name-instance-equality) says, for string equality, that it is defined by: > [...] both are strings, and are the same codepoint-for-codepoint; [...] We should add some tests to...
For example, the first test in the `const` file is ```json { "description": "const validation", "schema": {"const": 2}, "tests": [ { "description": "same value is valid", "data": 2, "valid": true...
They should probably include analogues of all of the absolute JSON Pointer tests from the JSON Pointer spec test case list. And there may be some other specific relative pointer...
`unevaluatedItems` should apply to instance items past the end of the `items` tuple the same way as `additionalItems`, except that it works with `items` across a reference or `allOf` or...
The draft-next folder contains tests for in-development next versions of the specification. It allows us to get ahead of testing before the spec is complete. At the minute in order...
Per discussion at https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/360 and https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/509#discussion_r700744243 The test suite sanity checker should collects all the $ids used in tests and verify they're unique, to make it easier on implementers whose...
Tests for format should make better use of vocabularies and optional/ is too overloaded with meaning
The draft2019-09 and draft2020-12 directories contain various tests for 'format'. The ones located in format.json document the results of everything (even bad formats) as valid: true. This is because of...