March 7, 2026

Spec-Driven OpenAPI Conformance Testing in MockForge

Most API teams can generate requests. Fewer can prove that an implementation conforms to the OpenAPI features their spec actually depends on.

The `0.3.55` through `0.3.57` release arc moved MockForge from broad conformance coverage into spec-driven conformance. Instead of testing only a canned reference surface, MockForge can analyze a real OpenAPI spec, detect which features it exercises, generate checks for those features, validate response bodies against response schemas, and emit SARIF output that fits into CI review workflows.

What changed in practice

• `0.3.55` added OpenAPI 3.0.0 conformance testing across 47 features and 10 categories, plus per-server stats and per-target spec support.
• `0.3.56` added spec-driven conformance, response schema validation, category filtering, and SARIF 2.1.0 output.
• `0.3.57` tightened feature detection for global security requirements, security scheme type resolution, and content negotiation.

Why this matters

Generic test suites tell you whether an endpoint returned something. Spec-driven conformance tells you whether the implementation matches the behaviors your OpenAPI document promises. That distinction matters when you are validating security schemes, multiple content types, response shapes, and feature-specific behaviors that usually drift quietly until integration or audit time.

The result is a more useful workflow for platform teams and QA leads: point MockForge at the spec you already own, run conformance against the features your API actually uses, and export findings in formats your CI stack already understands.