Refine OpenAPI coverage reporting for operation metrics#2355
Merged
Conversation
Summary
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What:
Refines OpenAPI coverage reporting in
junit5-supportto use operation-level metrics consistently.Why:
The report model and config terminology had drifted. The code was still carrying path/endpoint-oriented names and counters even after the behavior moved to operations, which made the coverage gate and report output harder to reason about.
How:
OpenApiCoverageReportInputto aggregate summary counts by operationOpenAPICoverageConsoleReportto expose onlytotalOperations,missedOperations, andnotImplementedOperationsgroupRecords()logic to remove duplication between coverage report classesChecklist:
Issue ID:
Closes: N/A