From a0f3a249dd5117a0ec2f55c08600070f0147c439 Mon Sep 17 00:00:00 2001 From: Georgios Andrianakis Date: Thu, 10 Jun 2021 08:22:04 +0300 Subject: [PATCH] Add note in guide about @QuarkusIntegrationTest and the test phase Relates to: #17812 (cherry picked from commit d006dc510697a039a69a3d34075fb9560372b3a1) --- docs/src/main/asciidoc/getting-started-testing.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/src/main/asciidoc/getting-started-testing.adoc b/docs/src/main/asciidoc/getting-started-testing.adoc index 9dca364914a59..7989be7187b05 100644 --- a/docs/src/main/asciidoc/getting-started-testing.adoc +++ b/docs/src/main/asciidoc/getting-started-testing.adoc @@ -1088,6 +1088,12 @@ Finally, if a container image was created during the build (by using including t As is the case with `@NativeImageTest`, this is a black box test that supports the same set features and has the same limitations. +[NOTE] +==== +As the `@QuarkusIntegrationTest` tests the result of the build, it should be run as part of the integration test suite - i.e., via the `maven-failsafe-plugin` if using Maven or an additional task if using Gradle. +These tests will **not** work if run in the same phase as `@QuarkusTest` as Quarkus has not yet created the final artifact. +==== + [[test-from-ide]] == Running `@QuarkusTest` from an IDE