Skip to content

Missing compatibility with Junit 5.4.0+ #764

Closed

Description

Hey,

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.

Can you help me?

greetz
DuckNr.1

Activity

  1. jdneo commented on Aug 6, 2019

    @jdneo
    Member

    Hi ducknrone,

    Thank you for reporting this. I just tested on my side, but failed to repro. See:

    demo

    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.

    Thanks,

  2. antonykamp commented on Aug 6, 2019

    @antonykamp
    Author

    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.

  3. jdneo commented on Aug 6, 2019

    @jdneo
    Member

    Yes I can repro now. actually the test cases could not run in IntelliJ and Eclipse either:

    Screen Shot 2019-08-06 at 8 29 09 PM

    Screen Shot 2019-08-06 at 8 29 53 PM

    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.0 in your build.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:
    Screen Shot 2019-08-06 at 8 33 10 PM

  4. antonykamp commented on Aug 6, 2019

    @antonykamp
    Author

    Thank you very much!

  5. jdneo commented on Aug 7, 2019

    @jdneo
    Member

    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.

    image

    The log level can be specified with java.test.log.level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions