You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by al...@apache.org on 2019/08/23 07:27:07 UTC
[camel] 03/03: CAMEL-13826: Added a comment in the doc about the
possibility to migrate per camel test
This is an automated email from the ASF dual-hosted git repository.
aldettinger pushed a commit to branch CAMEL-13826
in repository https://gitbox.apache.org/repos/asf/camel.git
commit f169f194ba8934d6aa1176e4150facd07a0a19c1
Author: aldettinger <al...@gmail.com>
AuthorDate: Thu Aug 22 17:39:28 2019 +0200
CAMEL-13826: Added a comment in the doc about the possibility to migrate per camel test
---
components/camel-test-junit5/src/main/docs/test-junit5.adoc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/components/camel-test-junit5/src/main/docs/test-junit5.adoc b/components/camel-test-junit5/src/main/docs/test-junit5.adoc
index f31ff75..858e3b7 100644
--- a/components/camel-test-junit5/src/main/docs/test-junit5.adoc
+++ b/components/camel-test-junit5/src/main/docs/test-junit5.adoc
@@ -57,6 +57,8 @@ Projects using `camel-test` would need to use `camel-test-junit5`. For instance,
</dependency>
----
+Tips: Note that it's possible to reference both `camel-test` and `camel-test-junit5` thus allowing to migrate camel tests once at a time.
+
=== 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`