OpenAPI Validation

[cmheazel]

Note on requirement 36 - "Currently, no tool is known to validate that a server implements the API specified in its OpenAPI definition."
One result from the hackathon should be a first cut at Annex A and a strategy on how it will be tested using TeamEngine. A general purpose OpenAPI test (does your service conform to your OpenAPI advertisement) seems like a good place to start.

[cportele]

By the way, I had a look at

• https://assertible.com/
• https://www.npmjs.com/package/open-api-test-generator

before writing that statement. Later on https://swagger.io/swagger-inspector/ was released, but again only very basic tests are derived from the API definition, as far as I could tell. I have not yet had a really close look though.

It would be great to get something that tests at least some assertions out of the hackathon!

[cmheazel]

Investigating an extension to Team Engine which will read an OpenAPI JSON document and then use it as the test document for that server (do you actually do what you claim to do). Biggest advantage is that the infrastructure and reporting will be the same as for all other OGC conformance tests.

[cmheazel]

The Abstract Test Suite calls for validation of the OpenAPI doc against the JSON Schema (under development). It then crawls through the OpenAPI document extracting the information it needs to perform the compliance tests. Not an exhaustive OpenAPI test suite, but it should validate the bits that we need.

[cportele]

Here is another tool (based on Node.js): https://github.com/google/oatts