-
Notifications
You must be signed in to change notification settings - Fork 194
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
tycho-surefire-plugin does not find junit5 suite #1097
Comments
@carstenartur can you provide an integration-test to demonstrate the issue? |
@carstenartur you can setup an example project first, and import only the itest-project, you don't need a full IDE setup. |
Tbh currently I think it would be more useful in this concrete case to find out how I can run the tests in the jdt.ui pull request without tycho. So the question is how I can mix - everything else running through tycho and some new tests using surefire directly. It looks like this is much faster. |
No one forces you to run them with Tycho :-)
Simply use |
Might this be just a naming problem? Your Suite name does not match any of the default include patterns: https://www.eclipse.org/tycho/sitedocs/tycho-surefire-plugin/test-mojo.html#includes |
You mean the explicit directive does not help? |
The include configuration takes Java source names, not class file names. But besides that I really recommend naming suites no different than other tests. I've run into the issue of non-execution because of not being named FooTest or TestFoo way too often in multiple tools already. |
Here you see some documentation that claims default pattern is using ".class" ending. |
Hi I am experiencing the same problem. |
Meanwhile we migrated to Junit5 Suites so this is not needed any longer. |
You can see what I mean looking at the pull request at
eclipse-jdt/eclipse.jdt.ui#129
It contains a suite like this:
The pom file contains
Unfortunately tycho does not find the junit5 suite. As soon as I exchange the entry with the (single) junit5 test class VisitorTest it works fine.
The text was updated successfully, but these errors were encountered: