Upgrade to wheels 3 #1836
michaeldiederich
started this conversation in
General
Replies: 2 comments
|
Michael,There is no migrator at the moment. But I could imagine trying to make one this year. Zain may be able to chime in on best practices.-Peter Amiri Sent from my iPhone (auto-typing mispell disclaimer in effect)On Jan 16, 2026, at 5:22 AM, Michael Diederich ***@***.***> wrote:
Congratulations for publishing version 3! Hooray!
I checked the documentation for upgrading (https://wheels.dev/3.0.0/guides/introduction/upgrading). Are there any best practices, you could share?
Especially the part with the tests - we have right now >1200 unit tests. Does the migration to TestBox needs to made by hand or is there any migrator?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
0 replies
|
Thanks, @michaeldiederich — and congrats on having such a solid test suite 👏 At the moment, there’s no automated migrator for converting existing tests to TestBox, so the migration does need to be done by hand. With large suites (like 1,200+ tests), the approach that’s worked best is to migrate incrementally rather than attempting a big-bang rewrite. A few best practices we’ve seen work well:
A TestBox migrator is something I’d like to explore this year, but there’s nothing available today and no fixed timeline yet. Happy to answer any specific questions as you go through the upgrade. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Congratulations for publishing version 3! Hooray!
I checked the documentation for upgrading (https://wheels.dev/3.0.0/guides/introduction/upgrading). Are there any best practices, you could share?
Especially the part with the tests - we have right now >1200 unit tests. Does the migration to TestBox needs to made by hand or is there any migrator?
All reactions