[
https://issues.apache.org/jira/browse/CAMEL-13826?focusedWorklogId=290494&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-290494
]
ASF GitHub Bot logged work on CAMEL-13826:
------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Aug/19 14:33
Start Date: 07/Aug/19 14:33
Worklog Time Spent: 10m
Work Description: aldettinger commented on pull request #3084:
CAMEL-13826: Initial version of a camel-test module with JUnit 5
URL: https://github.com/apache/camel/pull/3084
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 290494)
Time Spent: 20m (was: 10m)
> 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
>
> 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 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)
