-
Notifications
You must be signed in to change notification settings - Fork 6
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
Error if running zero tests #102
Comments
In comunica we use http://w3c.github.io/rdf-tests/sparql/sparql11/manifest-all.ttl, could you try that one? I'm guessing some breaking changes were introduced in http://w3c.github.io/rdf-tests/sparql/sparql11/manifest.ttl for the RDF 1.2 tests. |
Thanks! That's indeed quite confusing, especially given that they broke URIs repeatedly (RubenVerborgh/SPARQL.js@0ef0d4c). With For Suggestion: still error on |
That should be fine indeed, since the passed runner is configured to skip all non-parsing tests: https://github.com/RubenVerborgh/SPARQL.js/blob/main/spec/parser.js#L4-L15
http://w3c.github.io/rdf-tests/sparql/sparql11/manifest-all.ttl should also work here. |
Thanks, LGTM. Maybe just consider if you want the suite to error if it finds 0 tests. |
Good idea, we should add that. In addition, we may also want to add a flag that does not error in such cases, as there may be cases where zero tests are valid. |
In SPARQL.js, running
npm run spec-base-query
now silently fails with ”0/0 tests”:The text was updated successfully, but these errors were encountered: