[#5017] Fix swagger/swagger-generator/generator-core OD tests
#5018
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.
Issue
Several tests (
TestApiResponse,TestOperationGenerator, andOperationMethodAnnotationProcessorTest) were identified as order-dependent (OD) flaky tests. See #5017Fix
This PR transitions the test class to the JUnit 5
@TestInstance(Lifecycle.PER_CLASS)lifecycle, replacing the shared static field with an instance-scoped variable initialized in@BeforeAll. This resolves order-dependent flakiness by eliminating global state pollution, while ensuring that the resource-intensive Swagger generation runs only once per class. This approach balances test isolation with the performance efficiency required to hopefully prevent resource exhaustion and timeouts in the CI environment.Checklist
[SCB-XXX] Fixes bug in ApproximateQuantiles, where you replaceSCB-XXXwith the appropriate JIRA issue.mvn clean install -Pitto make sure basic checks pass. A more thorough check will be performed on your pull request automatically.