-
Notifications
You must be signed in to change notification settings - Fork 115
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
Consider migrating from JUnit 3/4 to JUnit Jupiter & JUnit 5 #189
Comments
I'm willing to consider this, but IMO, it's something we can address after 3.0 is released. Addressing a few of the points (in ignorance of how JUnit 5/Jupiter work, since I haven't used or researched them, just going from your description above): |
If we decide this is worth doing, we will have to take the following things into account.
assertThrows
over thetry..fail..catch
idiomassertAll
over just writing assertions one line after another, so that all potential assertion errors can be gathered and thrown together as one exception for easier debugging.assertTimeout
orassertTimeoutPreemptively
where we would have used@Test(timeout=...)
or@Rule public Timeout timeout = ...
assertIterableEquals
andassertLinesMatch
where normal collection equality assertions are insufficient.@Rule
s or@Runner
s, we will need to find alternative extensions for JUnit Jupiter/5.The text was updated successfully, but these errors were encountered: