Skip to content

Incorporating and merging with the compliance test suite #130

@gregsdennis

Description

@gregsdennis

Both this project and the CTS have a lot of useful test cases. I think it would be ideal to maintain these in a single place.

To that end, I'd like to propose merging the CTS test cases into this project. This project seems to be ideal because it already contains test harnesses for many well-known implementations.

To do this, I'd like to add some properties to the test cases to indicate what the spec says:

  • spec-valid - A boolean that determines whether the path is valid (can be parsed) according to the spec. There are a number of test cases in the CTS to ensure that the implementation returns an error when it should.
  • spec-result - The expected result as defined by the spec. I think it's still valuable to collect consensus results as well.

There may be more needed, but this is what I can think of so far.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions