You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
maybe you can help me. I'm trying to use feature Erik Zawadzki (@order)() from the Junit version 5.4.1. But if I want to run the test, nothing happens. In the java, test window stands that 0 tests appear.
Thank you for reporting this. I just tested on my side, but failed to repro. See:
So I guess it might not an issue related with @order but some other problems there. Is it possible for you to share a sample project to us to repro it? Then I can investigate deeper.
I have briefly made the repository public so that you can have a look. Here is the file.
In another project it works out fine, but not in this specific case. It doesn't matter which test I started with the newer version of JUnit. No test executes.
Activity
jdneo commentedon Aug 6, 2019
Hi ducknrone,
Thank you for reporting this. I just tested on my side, but failed to repro. See:
So I guess it might not an issue related with
@orderbut some other problems there. Is it possible for you to share a sample project to us to repro it? Then I can investigate deeper.Thanks,
antonykamp commentedon Aug 6, 2019
Thanks for your quick help.
I'm kind of confused, but oke :D
I have briefly made the repository public so that you can have a look.
Here is the file.
In another project it works out fine, but not in this specific case. It doesn't matter which test I started with the newer version of JUnit. No test executes.
jdneo commentedon Aug 6, 2019
Yes I can repro now. actually the test cases could not run in IntelliJ and Eclipse either:
After searching the error message, I got this answer
So all you need to do is adding
org.junit.platform:junit-platform-commons:1.4.0in yourbuild.gradle:dependencies { testImplementation 'org.junit.jupiter:junit-jupiter-api:5.4.1' testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.4.1' testCompile 'org.junit.platform:junit-platform-commons:1.4.0' }After that, the problem is gone:

antonykamp commentedon Aug 6, 2019
Thank you very much!
jdneo commentedon Aug 7, 2019
ducknrone
I'm closing this issue since it is resolved.
One thing I missed in the above comment is that you can see test runner output in it's output channel.
The log level can be specified with
java.test.log.level.