Skip to content
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

[numbers] support JUnit 5 tests #47

Closed
wants to merge 1 commit into from

Conversation

grimreaper
Copy link
Member

No description provided.

@aherbert
Copy link
Contributor

aherbert commented Jun 5, 2019

I think the recommended way is to use the JUnit Bill of Materials which contains all the versions which work together:

  <dependencyManagement>
      <dependency>
        <groupId>org.junit</groupId>
        <artifactId>junit-bom</artifactId>
        <!-- define this in properties -->
        <version>${numbers.junit.bom.version}</version>
        <scope>import</scope>
        <type>pom</type>
      </dependency>
    </dependencies>
  </dependencyManagement>

  <!-- Include what you require without version numbers. 
       They are all in the BOM. -->
  <dependencies>
    <dependency>
      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter</artifactId>
      <scope>test</scope>
    </dependency>
    <!-- For IDE support --> 
    <dependency>
      <groupId>org.junit.platform</groupId>
      <artifactId>junit-platform-launcher</artifactId>
      <scope>test</scope>
    </dependency>
    <!-- For JUnit 4 support --> 
    <dependency>
      <groupId>org.junit.platform</groupId>
      <artifactId>junit-platform-runner</artifactId>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.junit.vintage</groupId>
      <artifactId>junit-vintage-engine</artifactId>
      <scope>test</scope>
    </dependency>
  </dependencies>

You can see what it bundles on Maven repository org.junit:junit-bom:5.4.2.

I am not sure how it works with the legacy junit 4 dependency. I would try deleting that from the POM and just trying with the vintage engine dependency.

@coveralls
Copy link

coveralls commented Jun 5, 2019

Coverage Status

Coverage remained the same at 93.642% when pulling fccc6fe on grimreaper:eax/junit5-support into d01c9e7 on apache:master.

@grimreaper grimreaper force-pushed the eax/junit5-support branch 2 times, most recently from 26580cf to f8a8ff1 Compare June 5, 2019 10:43
@grimreaper
Copy link
Member Author

grimreaper commented Jun 5, 2019

@aherbert what about this iteration? As I wrote in my original email, I don't know maven that well.

(also, you're allowed to push to this branch if it'd help)

pom.xml Outdated Show resolved Hide resolved
pom.xml Outdated Show resolved Hide resolved
@aherbert
Copy link
Contributor

aherbert commented Jun 5, 2019

Looks fine. Let's see if Travis can run all the tests.

@grimreaper
Copy link
Member Author

Updated. Travis failed previously on coveralls related errors but not on the core tests.

Copy link
Contributor

@aherbert aherbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All looks good now

@grimreaper
Copy link
Member Author

Pushed as fccc6fe. Hope I did that right.

@grimreaper grimreaper closed this Jun 6, 2019
@grimreaper grimreaper deleted the eax/junit5-support branch June 6, 2019 03:41
@aherbert
Copy link
Contributor

aherbert commented Jun 6, 2019

I've pulled master and the changes are there. Downstream PRs for the switch to JUnit 5 should all be OK.

@grimreaper grimreaper restored the eax/junit5-support branch June 7, 2019 04:06
@grimreaper
Copy link
Member Author

actually see 6bcc6d9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants