Skip to content

3.1 schema tests: keyword coverage #4839

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 13, 2025
Merged

3.1 schema tests: keyword coverage #4839

merged 1 commit into from
Aug 13, 2025
+46 −0

Conversation

ralfhandl
Copy link
Contributor

Raise keyword/line coverage of our OAS schemas to 100% by adding "pass" test cases:

  • Link Object with requestBody
  • Schema Object with (deprecated) example keyword
  • Specification Extension
  • technical test: Schema Object via schema.yaml instead of schema-base.yaml
  • schema changes are included in this pull request
  • schema changes are needed for this pull request but not done yet
  • no schema changes are needed for this pull request

@ralfhandl ralfhandl requested review from a team as code owners August 12, 2025 08:57
@ralfhandl ralfhandl added this to the v3.1.2 milestone Aug 12, 2025
@ralfhandl ralfhandl changed the title 3.1: schema test keyword coverage 3.1 schema tests: keyword coverage Aug 13, 2025
@ralfhandl ralfhandl mentioned this pull request Aug 13, 2025
Merged
3 tasks
@ralfhandl ralfhandl requested a review from a team August 13, 2025 15:14
@ralfhandl
Copy link
Contributor Author

Merged with one approval because it only adds test cases

@ralfhandl ralfhandl merged commit b1bb5d4 into OAI:v3.1-dev Aug 13, 2025
2 checks passed
@ralfhandl ralfhandl deleted the 3.1-schema-test-keyword-coverage branch August 13, 2025 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@handrews handrews handrews approved these changes

Assignees
No one assigned
Labels
Schema
Projects
None yet
Milestone
v3.1.2
Development

Successfully merging this pull request may close these issues.
2 participants
@ralfhandl @handrews