You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[OpenAPI 3.1] Phase 0: test harness for paired 3.0/3.1 fixtures #948
Hi @DrSatyr — happy to take Phase 0. Plan: paired fixtures under core/src/test/resources/oas31/<rule>/ (old/new × 3.0/3.1) for type change, nullable, exclusive bounds, array items, allOf and oneOf, plus one Swagger 2.0 pair; a parameterized test asserting 3.0→3.0, 3.1→3.1 and 3.0→3.1 produce the same verdict, and the equivalence check that the same spec written as 3.0 and as 3.1 diffs to "no changes". Today's 3.1 gaps get marked disabled, each with a reference to the phase that fixes it — I hit several of these in the fixture work on #938, so I know where they live. Planning to start in the next few days unless you're already on it.
Known-failures inventory for the harness (PR #961). Everything failing on today's engine is kept as a disabled test in Oas31PairedFixturesTest, each naming the phase that un-disables it, so the build stays green.
Same-version verdicts (3.1->3.1 must agree with 3.0->3.0) - fixed by Phase 2 (#950), engine reads 3.1 fields:
Rule
Today's 3.1->3.1
Should be
Root cause
type-change
no_changes
incompatible
engine compares getType(), null for 3.1; type lives in the types set (#938, #910)
nullable
no_changes
compatible
null rule for "null" in types not implemented
exclusive-bounds
compatible
incompatible
3.1 numeric exclusiveMinimum is not read
array-items
no_changes
incompatible
items compared only on ArraySchema, 3.1 arrays are JsonSchema
Passing today and enabled: the 3.0->3.0 baseline verdicts for all six rules, and the Swagger 2.0 pair matching the 3.0 verdict. Each phase flips its own tests back on by removing the @Disabled annotations.
Activity
Inf1mum commentedon Nov 16, 2026
Hi @DrSatyr — happy to take Phase 0. Plan: paired fixtures under
core/src/test/resources/oas31/<rule>/(old/new × 3.0/3.1) for type change, nullable, exclusive bounds, array items, allOf and oneOf, plus one Swagger 2.0 pair; a parameterized test asserting 3.0→3.0, 3.1→3.1 and 3.0→3.1 produce the same verdict, and the equivalence check that the same spec written as 3.0 and as 3.1 diffs to "no changes". Today's 3.1 gaps get marked disabled, each with a reference to the phase that fixes it — I hit several of these in the fixture work on #938, so I know where they live. Planning to start in the next few days unless you're already on it.Inf1mum commentedon Nov 16, 2026
Known-failures inventory for the harness (PR #961). Everything failing on today's engine is kept as a disabled test in
Oas31PairedFixturesTest, each naming the phase that un-disables it, so the build stays green.Same-version verdicts (3.1->3.1 must agree with 3.0->3.0) - fixed by Phase 2 (#950), engine reads 3.1 fields:
getType(), null for 3.1; type lives in the types set (#938, #910)"null"in types not implementedexclusiveMinimumis not readArraySchema, 3.1 arrays areJsonSchemaComposedSchema(#938)ComposedSchemaCross-version verdicts (3.0->3.1) and the written equivalence - fixed by Phase 3 (#951), converter wired in:
type == null, so the type gate fires on each comparison)Passing today and enabled: the 3.0->3.0 baseline verdicts for all six rules, and the Swagger 2.0 pair matching the 3.0 verdict. Each phase flips its own tests back on by removing the
@Disabledannotations.