-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
Include test suite results for validator implementations #125
Comments
Further specification needed. |
I'm not really sure what I was thinking, but lemme guess |
Ideally, the test suite would produce a machine readable report (YAML, JSON, or CSV) which could be added within Perhaps too high of barrier to entry, but this could even be automated in separate repository where all implementations to be listed had to include code that boot-strapped testing their library against the suite and generating the report. |
Looking at shields.io, jenkins is the only one to support number of tests passed. |
This will shortly move to a separate job entirely, since right now only ajv's tests are running here, and they should not be. But we'll likely add a way for implementations to opt-in to having their tests run during new test additions as part of json-schema-org/json-schema-org.github.io#6, but not fail the build when their own tests fail.
I think Bowtie properly covers this. It doesn't yet have all of the implementations, but the framework is there. |
It might be useful if we include a brief summary of what features different validators support, and indicate test suite compliance.
This might be a task better handled by someone else, though.
The text was updated successfully, but these errors were encountered: