WORK IN PROGRESS

This Compliance Test Suite follows, and usually lags behind, the internet draft.

See cts.json for the Compliance Test Suite.

See the Contributor Guide if you'd like to submit changes.

To use this test suite, it's recommended you embed this repository as a git submodule of your implementation.

Basic conventions around source file formatting are captured in the .editorconfig file. Many editors support that file natively. Others (such as VS code) require a plugin, see https://editorconfig.org/.

To add or modify a test suite, edit the corresponding file in the tests directory. To generate cts.json, run the build.sh located in the root folder. Do not modify cts.json directly. More details are available in the Contributor Guide.

Where the spec allows non-deterministic results for a given testcase, the testcase should specify an array of all the valid results (each of which is itself an array representing the resultant nodelist from the query) in the "results" member (and should not specify a "result" member).