-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to munit 1.0.0-M6 #6657
Update to munit 1.0.0-M6 #6657
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's fine with me to adopt the new MUnit version if we would benefit from it.
This is a published dependency, via laws. The laws are underdeveloped, rarely depended on, and would not typically be used in applications, so it's not tragic. But this was a breaking change in a patch, and now production depends on a milestone. |
Sorry, I was completely unaware of that. Why do our laws depend on munit? Typically laws depend on Discipline and not a specific test framework. |
Good question. Looks like |
Hmm. At a glance I think the Right:tm: thing to do there would have been to use the Cats Effect testkit. Not ruling out that effectful laws are tricky. We can fix this on 1.x. |
At this point it is quite stable and brings many improvements we could benefit from, such as async resource fixtures (thanks to @danicheg for working on that in munit core :)