[ https://issues.apache.org/jira/browse/CAMEL-13826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Dettinger updated CAMEL-13826: ----------------------------------- Description: 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. was: We start this effort with below direction (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. > 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 > > 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)