[
https://issues.apache.org/jira/browse/CAMEL-11807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796014#comment-16796014
]
Eric Deandrea edited comment on CAMEL-11807 at 3/19/19 12:09 PM:
-----------------------------------------------------------------
Hi [~zregvart] maybe I got to this issue by mistake - it was [linked to from
StackOverflow by Sam
Brannen|https://stackoverflow.com/questions/48292929/junit-5-with-cameltestsupport].
I understand I can use JUnit Vintage and still write my tests using JUnit 4. My
question was specifically around being able to write my Camel tests in JUnit 5
using all the goodies that it brings (i.e. parameterized tests, etc) using the
{noformat}
@ExtendWith{noformat}
annotation vs
{noformat}
@RunWith(CamelSpringJUnit4ClassRunner.class){noformat}
was (Author: edeandrea):
Hi [~zregvart] maybe I got to this issue by mistake - it was [linked to from
StackOverflow by Sam
Brannen|https://stackoverflow.com/questions/48292929/junit-5-with-cameltestsupport]].
I understand I can use JUnit Vintage and still write my tests using JUnit 4. My
question was specifically around being able to write my Camel tests in JUnit 5
using all the goodies that it brings (i.e. parameterized tests, etc) using the
{noformat}
@ExtendWith{noformat}
annotation vs
{noformat}
@RunWith(CamelSpringJUnit4ClassRunner.class){noformat}
> 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: Minor
> Labels: gsoc2019
> Fix For: 3.0.0, Future
>
>
> See http://junit.org/junit5/
> Note: it provides a junit-vintage module so we should be able to migrate
> stuffs easily (!)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
