Skip to content

Update the JSON Schema Test Suite to version 2.0.0 #714

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

Conversation

niconoe-
Copy link
Contributor

Replay of the #582

Copy link

@dafeder dafeder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are new skipped tests, particularly ref.json. Is this because of a bug that needs to be documented?

@DannyvdSluijs
Copy link
Collaborator

From the original PR:

Update the JSON Schema Test Suite to version 2.0.0 to fetch test suites on Draft 06 and Draft 07.
Updated validation on draft 04 since changes have been done on the test suites.

Regarding some discussions on #581 I wanted to have access to the official test-suite for draft 07. This is possible by upgrading the JSON-Schema-Test-Suite in version 2.0.0, on which Draft 04 has been upgraded too.

I required to upgrade some snippet and make evolved some tests to make pass the Draft 04 validation.

@DannyvdSluijs
Copy link
Collaborator

I'll close this PR for now as time has progresses and version 23.1.0 of the JSON Schem test suite is already out. I've been working on bumping the test suite on my local machine as well.
But more importantly I've been working on fixing the issues from the test and simultaniously been working on a proper test harness for http://bowtie.report which runs the JSON Schema test suite.

@niconoe- this doesn't mean you've been of great help. Thanks you for all your help in the project. 👍🏼

@niconoe- niconoe- deleted the update-json-schema-test-suite-2.0.0 branch April 11, 2025 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants