You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Alex Dettinger (Jira)" <ji...@apache.org> on 2019/10/30 08:53:00 UTC

[jira] [Updated] (CAMEL-11807) Upgrade to JUnit 5

     [ https://issues.apache.org/jira/browse/CAMEL-11807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Dettinger updated CAMEL-11807:
-----------------------------------
    Description: 
See http://junit.org/junit5/

Note: it provides a junit-vintage module so we should be able to migrate stuffs easily (!)

JUnit 5 versions of the more common test modules have been created in CAMEL-13342.
Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged.

  was:
See http://junit.org/junit5/

Note: it provides a junit-vintage module so we should be able to migrate stuffs easily (!)


> Upgrade to JUnit 5
> ------------------
>
>                 Key: CAMEL-11807
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11807
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Luca Burgazzoli
>            Priority: Major
>              Labels: gsoc2019
>             Fix For: 3.x
>
>
> See http://junit.org/junit5/
> Note: it provides a junit-vintage module so we should be able to migrate stuffs easily (!)
> JUnit 5 versions of the more common test modules have been created in CAMEL-13342.
> Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)