Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JUnit4Migration"
(A wiki page explaining briefly the motivation about migrating the org.eclipse.* tests to JUnit 4) |
(Eclipse projects are currently ''not required'' to convert tests) |
||
| Line 1: | Line 1: | ||
| + | {{important|Note|The following is one user's personal opinion. JDT will not add support for JUnit 5 if that would mean dropping support for JUnit 3 tests, and Eclipse projects are currently '''not required''' to waste time converting their tests. Converting tests is not trivial, and any contributions need to be verified carefully. See e.g. {{bug|487095}}}} | ||
| + | |||
With JUnit 5 alpha being already available (http://repo1.maven.org/maven2/org/junit/) it seems like it will drop support for JUnit 3 APIs. Once JUnit 5 comes to JDT it would be nice not to have 3 different style of junit tests around. This work will have to eventually be done to keep up with the newer JUnit releases. | With JUnit 5 alpha being already available (http://repo1.maven.org/maven2/org/junit/) it seems like it will drop support for JUnit 3 APIs. Once JUnit 5 comes to JDT it would be nice not to have 3 different style of junit tests around. This work will have to eventually be done to keep up with the newer JUnit releases. | ||
Revision as of 11:42, 14 April 2016
The following is one user's personal opinion. JDT will not add support for JUnit 5 if that would mean dropping support for JUnit 3 tests, and Eclipse projects are currently not required to waste time converting their tests. Converting tests is not trivial, and any contributions need to be verified carefully. See e.g. bug 487095
With JUnit 5 alpha being already available (http://repo1.maven.org/maven2/org/junit/) it seems like it will drop support for JUnit 3 APIs. Once JUnit 5 comes to JDT it would be nice not to have 3 different style of junit tests around. This work will have to eventually be done to keep up with the newer JUnit releases.
Also https://junit-team.github.io/junit5/#running-tests does not even mention the possibility of running JUnit 3 tests.
The APIs are cleaner in most cases and most developers are more used to 4 API rather than 3, and that is always good for the project in terms of potential contributors.
To summarize the goal is: make sure for all (as much as we can) projects to be prepared when JUnit 5 comes and it kills support for JUnit 3 tests.