-
Notifications
You must be signed in to change notification settings - Fork 93
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
Migration to junit 5 #1725
Migration to junit 5 #1725
Conversation
f89dd86
to
162b9d7
Compare
1172001
to
4f3b32d
Compare
9f9fa67
to
2bf7708
Compare
2bf7708
to
706a5a4
Compare
This pull request changes some projects for the first time in this development cycle.
An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patch
Further information are available in Common Build Issues - Missing version increments. |
67be5d2
to
1b81a66
Compare
test to run the upcoming junit 4 to junit 5 migration cleanup
1b81a66
to
d81f0a0
Compare
Thanks @carstenartur. |
run the upcoming junit 4 to junit 5 migration cleanup
What it does
This Pr changes a bunch of tests from using JUnit 4 to JUnit 5.
It does not change anything at all about how jdt.ui works. Changes are in the testing code only.
However in the testing code it should not change anything neither. The migration from JUnit 4 suites to JUnit 5 suites was able to boost performance a little bit. I am not aware of similar effects in the testing code. So what this Pr gives you is that the affected classes are following a testing pattern using a actively maintained release for the first time in the last 20(?) years.
How to test
Count the number of tests and check results.
Author checklist