qa-contract-validate

To validate an OpenAPI contract, provide the specification path to run a multi-tool pipeline. This orchestrates Spectral, oasdiff, Prism, and Schemathesis to lint, diff, conformance check, and fuzz the API spec.

Yes, you can detect breaking changes by providing an optional baseline OpenAPI specification. The pipeline uses oasdiff to compare the current spec against the baseline and outputs the detected breaking changes.

You can run conformance and fuzz tests on a live API URL by providing it alongside your OpenAPI specification. The pipeline orchestrates Prism and Schemathesis to validate runtime behavior against the contract.

The pipeline orchestrates Spectral, oasdiff, Prism, and Schemathesis when available and enforces tool-availability checks. You receive validation results for any supported tools installed in your environment.

The API contract validation results are written to the JAAN_OUTPUTS_DIR. This standardized output directory allows for easy ingestion, reporting, and indexing of the linting, diff, and conformance findings.

The best way to orchestrate multiple API contract validation tools is using a phased pipeline with user-approval gating. This coordinates Spectral, oasdiff, Prism, and Schemathesis to enforce OpenAPI compliance with standardized outputs.