This is an automated email from the ASF dual-hosted git repository.
jamesnetherton 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 b0f2797 Add more details about @QuarkusIntegrationTest to the testing
guide
b0f2797 is described below
commit b0f2797e04060b3991e302fbb7d17ee79688926b
Author: James Netherton <jamesnether...@gmail.com>
AuthorDate: Fri Mar 25 11:41:59 2022 +0000
Add more details about @QuarkusIntegrationTest to the testing guide
Fixes #3650
---
docs/modules/ROOT/pages/user-guide/testing.adoc | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/docs/modules/ROOT/pages/user-guide/testing.adoc
b/docs/modules/ROOT/pages/user-guide/testing.adoc
index a2136a0..24688eb 100644
--- a/docs/modules/ROOT/pages/user-guide/testing.adoc
+++ b/docs/modules/ROOT/pages/user-guide/testing.adoc
@@ -73,6 +73,14 @@ An important consequence of this setup is that all
communication between tests a
must go over network (HTTP/REST, or any other protocol your application speaks)
or through watching filesystem (log files, etc.) or any other kind of
interprocess communication.
+`QuarkusIntegrationTest` also provides some additional features that are not
available through `@QuarkusTest`.
+
+* In JVM mode it can launch and test the runnable application JAR produced by
the Quarkus build.
+* As mentioned above, in native mode it can launch and test the native
application produced by the Quarkus build.
+* If a container image was created during the build, then a container is
started so that tests can be executed against it.
+
+For more information about `QuarkusIntegrationTest` see the
https://quarkus.io/guides/getting-started-testing#quarkus-integration-test[Quarkus
testing guide].
+
== Testing with external services
=== Testcontainers
