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

Posted to issues@camel.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2020/07/28 11:27:00 UTC

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

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

Guillaume Nodet resolved CAMEL-11807.
-------------------------------------
    Resolution: Fixed

> Upgrade to JUnit 5
> ------------------
>
>                 Key: CAMEL-11807
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11807
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Luca Burgazzoli
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 3.5.0
>
>
> See http://junit.org/junit5/
> Note: it provides a junit-vintage module so we should be able to migrate stuffs easily (!)
> Most users should now be able to write JUnit 5 tests using the modules created in CAMEL-13342.
> Concerning the migration of camel own tests to JUnit5, the last blocker is that migrating flaky tests to JUnit 5 is not handled 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)