Skip to content

Let rewriteRun verify the JUnit 4 to 5 migration settles - #1209

Merged
knutwannheden merged 2 commits into
mainfrom
cycles-follow-expected
Oct 23, 2026
Merged

knutwannheden merged 2 commits into
mainfrom
cycles-follow-expected

Conversation

@knutwannheden

Copy link
Copy Markdown
Contributor

AddJupiterDependenciesTest and AddHamcrestIfUsedTest pinned cycles(1).expectedCyclesThatMakeChanges(1), so rewriteRun never ran the cycle that checks the JUnit 4 to 5 migration changes nothing more. The migration settles, so the pins go, and the default two cycles run that check. declaresParametersGeneratedByJUnitParamsInOneCycle still asserts a single changing cycle.

This is part of removing cycle pins ahead of openrewrite/rewrite#9359, and it doesn't depend on it. Both classes pass (16 tests). ReplacePowerMockitoIntegrationTest, which gains a verification cycle under #9359, also passes against rewrite-test built from it.

cycles(1).expectedCyclesThatMakeChanges(1) skipped the cycle that checks the
recipe changes nothing more. The default of two cycles runs it.
@github-project-automation github-project-automation Bot moved this to In Progress in OpenRewrite Oct 23, 2026
@knutwannheden
knutwannheden marked this pull request as ready for review October 23, 2026 17:30
@knutwannheden
knutwannheden merged commit bc86001 into main Oct 23, 2026
2 checks passed
@knutwannheden
knutwannheden deleted the cycles-follow-expected branch October 23, 2026 17:30
@github-project-automation github-project-automation Bot moved this from In Progress to Done in OpenRewrite Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

1 participant