[camel-quarkus] 20/43: Add more details about @QuarkusIntegrationTest to the testing guide

[pp...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ppalaga pushed a commit to branch 2.7.x
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git

commit 986490a86ca3f45a0c5ba8ce5650114066332a23
Author: James Netherton <ja...@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