[
https://issues.apache.org/jira/browse/CAMEL-13826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901827#comment-16901827
]
Zoran Regvart commented on CAMEL-13826:
---------------------------------------
I think we should shield users from version changes. That's why I wonder if
we'll need to create or rename {{camel-test-junit5}} to {{camel-test-junit6}}
at some point in the future. I think putting versions in components has already
caused us problems, and required users to perform, some times trivial,
migrations.
> Create a camel-test-junit5 module
> ---------------------------------
>
> Key: CAMEL-13826
> URL: https://issues.apache.org/jira/browse/CAMEL-13826
> Project: Camel
> Issue Type: Sub-task
> Affects Versions: 3.0.0.M4
> Reporter: Alex Dettinger
> Assignee: Alex Dettinger
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We start this effort with below directions (and could refine later on):
> + Users should be able to keep old JUnit 4 tests for a while
> + Ideally, it would be possible to migrate camel test per camel test
> + Keeping CamelTestSupport class name and the test by inheritance approach
> would make adoption and migration easier
> + CamelTestSupport based tests looks more concise than tests that would use
> some kind of injection (e.g. injection the CamelContext and so on)
> + Adding a new module would allow users to get rid of JUnit 4 when they want
> (they simply stop using camel-test)
>
> Note that even when JUnit 4 would be dropped, camel-test would still contains
> some kind of test utility classes like
> org.apache.camel.test.AvailablePortFinder.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
