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/09/04 13:02:00 UTC
[jira] [Updated] (CAMEL-13826) Create a camel-test-junit5 module
[ https://issues.apache.org/jira/browse/CAMEL-13826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Dettinger updated CAMEL-13826:
-----------------------------------
Fix Version/s: 3.0.0.RC2
> 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
> Fix For: 3.0.0, 3.0.0.RC2
>
> Time Spent: 20m
> 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 of 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)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)