Awesome
Try the test viewer.
shexTest
Directories:
schemas
- Test schemas in ShExC (
.shex
), ShExJ (.json
) and sometimes SHACL (.shacl
).
The ShExC and ShExJ files with the same stem name are equivalent. A ShExC syntax test consists of these steps:
- parse the ShExC version of the document with some base URI.
- parse the ShExJ, as JSON; evaluate the values of the following as relative IRIs:
- values of the
start
,inclusion
,predicate
, anddatatype
properties. - shape names (keys in the
shapes
object). - terms in
values
properties.
- values of the
- ensure that no
ValueAnd
orValueOr
expression containsValueAnd
orValueOr
expressions in the list ofvalueExprs
. - the two parsed products should be equivalent, with blank node substitution.
negativeSyntax
These tests violate the ShEx2 grammar.
negativeStrucutre
These tests should raise errors when parsed, noting the rule about nested ValueAnd
and ValueOr
expressions.
validation
- Validation tests in a manifest (Turtle -
manifest.ttl
, ShExJ (obselete primer) -manifest.json
). - Input data in Turtle (
.ttl
). - Validation returns a ShapeMap capturing which node/shape pairs conform. The expected conformance or non-conformance is captured in the test format as a
ValidationTest
orValidationFailure
.
A ShEx validator is logic-conformant
when it returns success for the tests of type ValidationTest
and failure for the tests of type ValidationFailure
.
A ShEx validator is result-conformant
(experimental) when it executes as ValidationTest
and produces the same result structure as produced by this procedure:
- parse the result file as JSON.
- parse the ShExJ, as JSON; evaluate the values of the following as relative IRIs:
- values of the
node
,shape
,subject
,predicate
, andobject
properties.
- values of the
- the two parsed products should be equivalent, with blank node substitution.
A ShEx validator is
error-conformant
(even more experimental) when it executes aValidationFailure
and produces the same result structure as produced by the procedure above.
coverage
One frequently wants to ask "does the test suite include X".
One way to test that is to guess by the relatively formulaic filenames and test names in validation/manifest
.
Another is to "grep" through the JSON representations of the queries for something with the appropriate structure, e.g. using jq to EachOf
s that include a pattern with a min
cardinality of 0:
(for f in schemas/*.json; do
jq -e '.[]|..|objects|select(.type=="EachOf").expressions[]|select(.min==0)' $f > /dev/null &&
echo $f;
done
)
which yields the files which include this pattern:
schemas/1val1IRIREFExtra1Or.json
schemas/3circularRef1.json
schemas/kitchenSink.json