[OpenAPI 3.1] Phase 0: test harness for paired 3.0/3.1 fixtures

Open
#948 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

@Inf1mum is already working on this.

Since Nov 16, 2026.

  • #961 by @Inf1mum — open

Assessment

Difficulty
3/5
Estimated time
3-5 days
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java, openapi, yaml
Domain
api, testing

Research direction

Start by reading the parent plan #942 to see which later phase consumes each fixture, then look at how the existing tests under core/src/test/resources and the parameterized test classes in core/src/test/java are wired so the new harness matches. Create core/src/test/resources/oas31/<rule>/ with the four 3.0/3.1 old/new YAML pairs, beginning with the type-change rule, and add the parameterized test asserting 3.0→3.0, 3.1→3.1 and 3.0→3.1 agree plus the equivalence test. Done means the build is green with today's 3.1 failures disabled and each one listed in the issue with the phase that fixes it.

Written by the indexing model from the issue text.

Description

OpenAPI 3.1.0 Support

Part of the OpenAPI 3.1 plan: #942 (Stage 1, Phase 0)

Goal

The test setup that every later phase uses.

Scope
  • Fixture layout: core/src/test/resources/oas31/<rule>/ with old-3.0.yaml, new-3.0.yaml, old-3.1.yaml, new-3.1.yaml
  • A parameterized test that checks 3.0→3.0, 3.1→3.1 and 3.0→3.1 give the same verdict
  • An equivalence test: the same spec written in 3.0 and in 3.1 gives no changes
  • First fixtures: type change, null allowed, exclusive bounds, array items, allOf, oneOf
  • One Swagger 2.0 fixture
  • Today's 3.1 failures are marked as known (disabled with a reference to the phase that fixes them), so the build stays green
Done when
  • Harness and first fixtures merged, build green
  • Known failures are listed in this issue, each linked to the phase that fixes it
Dominant language
Java
Stars
1.1k
Forks
191
Avg merge
4d 23h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenAPITools/openapi-diff

All issues in OpenAPITools/openapi-diff

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.