Skip to content

Conformance tests #1

Description

@scothis

We have a spec that has requirements for implementations. It would be nice to have a test suite that could be used to judge if an implementation is compatible with the specification.

The conformance tests should:

  • have an assertion to cover each MUST, MUST NOT, etc in the spec that will fail the suite if the assertion fails
  • have an assertion to cover each SHOULD, SHOULD NOT, etc in the spec, but do not fail the suite if the assertion fails
  • have a negative test to cover each MAY, RECOMMENDED, etc in the spec, but do not fail the suite if the assertion fails
  • make no assumptions as to ambiguities in the spec (those should be files as issues against the spec)
  • make no assumptions as to the internals of the implementation, only the spec defined interfaces should be tested
  • have minimal prerequisites (ideally none) other than a service binding implementation running in a cluster
  • remove any state they add to the cluster during the tests

Initially, we should focus on the core specification. Spec extensions should discrete conformance tests that can be run independently.

Activity

  1. arthurdm commented on Aug 23, 2020

    @arthurdm
    Member

    great idea @scothis - it will be crucial for ensuring adopting frameworks remain consistent.

  2. arthurdm commented on Nov 24, 2020

    @arthurdm
    Member

    Community to check whether there's guidance or requirements from a SIG perspective on conformance test suites.

  3. added this to the core/1.0.0 milestone on Nov 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions