[jira] [Work logged] (CAMEL-13826) Create a camel-test-junit5 module

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-13826?focusedWorklogId=289762&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-289762 ]

ASF GitHub Bot logged work on CAMEL-13826:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Aug/19 14:56
            Start Date: 06/Aug/19 14:56
    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
 
 
   Please find a minimal port of camel-test to JUnit 5 for early review, more context in https://issues.apache.org/jira/browse/CAMEL-13826. Changes of interest are mostly located in CamelTestSupport.
   
   As next steps, I would:
   + Remove TestSupport and replace with some kind of CamelAssertions classes
   + Move route coverage to a dedicated class
   + Merely remove deprecated registry stuff from CamelTestSupport (as this class is not used by anyone yet)
   + Investigate whether JUnit 5 "per-class" test instance lifecycle could replace CamelTestSupport.isCreateCamelContextPerClass
   + Move to other class some methods that are candidate for being static imported like CamelTestSupport.assert*/send*/getMock*
   + Port tests of few components to JUnit 5 (the occasion to add a small migration kind in camel-test-junit5.adoc)
   + Add the possibility for camel-test and camel-test-junit5 tests to coexist (so users could migrate camel test per camel test)
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 289762)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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)