Cleanup JUnit4 leftovers #9731
Merged
Cleanup JUnit4 leftovers #9731
Conversation
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
AlexeyKuznetsov-DD
added
tag: no release notes
AlexeyKuznetsov-DD
requested review from
daniel-mohedano,
dougqh and
nikita-tkachenko-datadog
PerfectSlayer
approved these changes
Oct 13, 2025
Contributor
PerfectSlayer
left a comment
PerfectSlayer
left a comment
There was a problem hiding this comment.
Sounds good. I left a question about the ClassRule support for clarification.
...-agent/instrumentation/jax-rs-annotations-2/src/nestedTest/groovy/NestedResourcesTest.groovy
Show resolved
Hide resolved
bric3
approved these changes
Oct 13, 2025
nikita-tkachenko-datadog
approved these changes
Oct 13, 2025
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 Does This Do
Motivation
Most tests have already been migrated to JUnit 5. This PR reduces mixed-framework friction, simplifies test execution, and makes the remaining migration surface obvious.
Additional Notes
Some modules depend on legacy libraries that currently block migration to JUnit 5. For those modules, JUnit 4 remains in place and is explicitly documented/isolated.