corpus-test

Corpus regression testing validates parser and fixer behaviors across a diverse set of real-world OpenAPI specs to catch regressions early. It executes integration tests against a stored corpus, reporting parse, validate, and fix outcomes with per-spec notes.

Run integration tests against an OpenAPI corpus by checking corpus availability, downloading it if needed via Makefile targets, and executing tests in full or short mode. The workflow uses Glob-based discovery and reports parse, validate, and fix outcomes across multiple specs.

Corpus testing requires a Glob-based corpus discovery step and Makefile targets for corpus download and test execution. It also uses a fixer to resolve validation issues during the automated regression testing workflow.

You can run a short test mode instead of the full corpus to validate OpenAPI specs more quickly. Both modes execute integration tests and report parse, validate, and fix outcomes, allowing flexible regression testing between releases.

OpenAPI corpus regression tests report validation issues to identify spec parsing or validation failures across the corpus. The workflow uses a fixer to resolve these validation issues and tracks regressions across multiple specs between releases.

The best way to track regressions across real-world OpenAPI specs is automated corpus regression testing. By running integration tests against a stored corpus, you verify parser, validator, and fixer behaviors, generating per-spec reports to track changes between releases.