March 7, 2026

Spec-Driven OpenAPI Conformance Testing

Most API teams can generate traffic. Fewer can prove that an implementation conforms to the OpenAPI behaviors their spec actually depends on. That is the real value behind the 0.3.55 through 0.3.57 release arc.

Why This Matters

Most API testing stops at "did the endpoint return something" and "did the status code look right." Spec-driven conformance closes that gap, providing confidence in security scheme behavior, response schema correctness, content negotiation support, and category-specific contract coverage.

What Changed

Across 0.3.55 to 0.3.57, MockForge added OpenAPI 3.0.0 conformance testing across 47 features and 10 categories, per-target spec support for multi-target mode, spec-driven conformance against a real OpenAPI file, response schema validation, conformance category filtering, SARIF 2.1.0 output for CI and scanning workflows, and fixes for global security detection, security scheme type resolution, and content negotiation.

Who Should Care

This is especially relevant if you operate a platform or API program, own integration quality across multiple services, need better proof in CI than "the endpoint returned 200," or want contract-aware testing without building custom conformance tooling.

Strategic Value

The closer your test workflow gets to the spec your consumers depend on, the fewer surprises you leave for downstream teams. Point MockForge at the spec you already own, then validate the behaviors your API actually uses instead of a generic sample surface.