[OpenAPI 3.1] Phase 0: test harness for paired 3.0/3.1 fixtures
Maintainers usually reply within 5 days
Assessment
- Difficulty
- 3/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 62/100
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
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>/withold-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
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenAPITools/openapi-diff
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenAPITools/openapi-diff#506 ·
Maintainers usually reply within 5 days
-
HtmlRender: Notes of Parameters shows always the new descriptionPossibly taken @Inf1mum claimed this 6 days ago. Opengood first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenAPITools/openapi-diff#364 ·
Maintainers usually reply within 5 days
-
Render capabilities
Difficulty 5/5 Over a week Newbie friendliness 20/100
OpenAPITools/openapi-diff#959 ·
Maintainers usually reply within 5 days
-
Render capabilities
Difficulty 5/5 Over a week Newbie friendliness 18/100
OpenAPITools/openapi-diff#958 ·
Maintainers usually reply within 5 days
-
Render capabilities
Difficulty 3/5 1-2 days Newbie friendliness 55/100
OpenAPITools/openapi-diff#957 ·
Maintainers usually reply within 5 days
All issues in OpenAPITools/openapi-diff
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
eclipse-tradista/tradista#371 ·
Maintainers usually reply within 1 day
-
critical
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mars-sim/mars-sim#2199 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
projeto-ong-amar/projeto-ong-amar-backend#26 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
primefaces/primefaces#15568 ·
Maintainers usually reply within 1 day
-
崩溃日志只按 CRLF 分行Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PCL-Community/PCL-CE#3872 ·
Maintainers usually reply within 1 day