This is an automated email from the ASF dual-hosted git repository. ppalaga pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/main by this push: new c156d23949 Testing guide confusing about CamelTestSupport #4068 c156d23949 is described below commit c156d23949c129934151440991c555e374af1ae7 Author: Peter Palaga <ppal...@redhat.com> AuthorDate: Mon Sep 5 15:27:05 2022 +0200 Testing guide confusing about CamelTestSupport #4068 --- docs/modules/ROOT/pages/user-guide/testing.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/user-guide/testing.adoc b/docs/modules/ROOT/pages/user-guide/testing.adoc index bb4efcc509..b2a47920e7 100644 --- a/docs/modules/ROOT/pages/user-guide/testing.adoc +++ b/docs/modules/ROOT/pages/user-guide/testing.adoc @@ -6,7 +6,8 @@ Before going deeper in the subject, it is strongly advised to read xref:user-gui When it comes to testing a route in the context of Quarkus, the paved road is to write local integration tests. This has the advantage of covering both JVM and native mode. -The flip side is that the standard Camel testing approach with `camel-test` and `CamelTestSupport` is not supported. + +The xref:#_cameltestsupport_style_of_testing[`CamelTestSupport` approach] can be used since Camel Quarkus 2.12.0. Note that it can only work in JVM mode. Let's enumerate some points of interest below.