This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new 2b76b18 Regen
2b76b18 is described below
commit 2b76b186761648d7833b57ce3f08e747ec987fa0
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Sep 5 05:17:18 2019 +0200
Regen
---
docs/components/modules/ROOT/pages/test-junit5.adoc | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/components/modules/ROOT/pages/test-junit5.adoc
b/docs/components/modules/ROOT/pages/test-junit5.adoc
index 99c3f6b..6b23e2d 100644
--- a/docs/components/modules/ROOT/pages/test-junit5.adoc
+++ b/docs/components/modules/ROOT/pages/test-junit5.adoc
@@ -58,11 +58,17 @@ Projects using `camel-test` would need to use
`camel-test-junit5`. For instance,
</dependency>
----
+Tips: It's possible to run JUnit4 & JUnit5 based camel tests side by side
including the following dependencies `camel-test`,
+`camel-test-junit5` and `junit-vintage-engine`. This configuration allows to
migrate a camel test at once.
+
=== Typical migration steps linked to JUnit 5 support in Camel Test
* Imports of `org.apache.camel.test.junit4.\*` should be replaced with
`org.apache.camel.test.junit5.*`
* `TestSupport` static methods should be imported where needed, for instance
`import static org.apache.camel.test.junit5.TestSupport.assertIsInstanceOf`
* Usage of the field `CamelTestSupport.log` should be replaced by another
logger, for instance `org.slf4j.LoggerFactory.getLogger(MyCamelTest.class);`
* Usage of the method `CamelTestSupport.createRegistry` should be replaced by
`CamelTestSupport.createCamelRegistry()`
+* Overrides of `isCreateCamelContextPerClass()` returning `false` should be
removed
+* Overrides of `isCreateCamelContextPerClass()` returning `true` should be
replaced by `@TestInstance(Lifecycle.PER_CLASS)`
+
=== Typical migration steps linked to JUnit 5 itself
Once Camel related steps have been performed, there are still typical JUnit 5
migration steps to remember:
