-
Notifications
You must be signed in to change notification settings - Fork 216
JUnitj v5 more progression #243
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
JUnitj v5 more progression #243
Conversation
ce4c7ab to
7ae30ef
Compare
8fd83af to
a396ef7
Compare
|
@nhojpatrick Note that the tests are faiing. |
(cherry picked from commit 19bd187d6b5a099e2c46862f0bd60f0cab983437)
(cherry picked from commit 8bd6e0b5560d1ec19fa74244a8fbcff321727f8f)
a396ef7 to
80b677e
Compare
|
@garydgregory Have removed failing tests as I couldn't quickly fix, will get in the next batch. |
| import junit.framework.TestResult; | ||
|
|
||
| public class RunTest { | ||
|
|
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.
In the future, please don't mix in style changes, it makes the PR larger and it takes longer to review.
garydgregory
left a comment
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.
See 1 comment, no style changes, it's annoying to review 167 files when so many contain ONLY adding or removing blank lines.
Everything with this pr and PR #242 now migrated to JUnit v5, unless it depends upon junit.framework.TestCase.