-
Notifications
You must be signed in to change notification settings - Fork 193
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
Enable JUnit 5 test suite engine in tycho-surefire #2462 #3358
Conversation
50b0a0d
to
731e5d7
Compare
Currently, Tycho is not capable of running JUnit 5 test suites, since the required SuiteTestEngine is not provided while running tests. This change adds the SuiteTestEngine to tycho-surefire executions using JUnit Platform 1.8 (the first with suite support) or newer. To this end, the SuiteTestEngine is always enabled when running JUnit 5 tests. It also adds a regression test for executing a test suite based on JUnit Jupiter 5.9. Fixes eclipse-tycho#2462
731e5d7
to
a842a10
Compare
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.
@akurtakov It looks al sane to me, but as you have done the surefire parts in the past you probably want to take a second look.
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.
Change looks good to me.
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Thank you for reviewing and merging this so fast, @laeubi and @akurtakov! |
Currently, Tycho is not capable of running JUnit 5 test suites, since the required
SuiteTestEngine
is not provided while running tests.This change adds the
SuiteTestEngine
to tycho-surefire executions using JUnit Platform 1.8 (the first with suite support) or newer. To this end, theSuiteTestEngine
is always enabled when running JUnit 5 tests. It also adds a regression test for executing a test suite based on JUnit Jupiter 5.9.I do not see any problems of simply making the
SuiteTestEngine
always available (other than theVintageTestEngine
), but let me know if you think different. The problem when adding further fragments likejunit59withvintage
for when the suite API is on the classpath is the combinatorial complexity, as you would needjunitX
,junitXwithvintage
,junitXwithsuite
,junitXwithsuiteandvintage
.Fixes #2462
Closes #3342