Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docs on running @QuarkusIntegrationTest against a running application #33378

Merged
merged 1 commit into from
May 16, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions docs/src/main/asciidoc/getting-started-testing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -1385,11 +1385,6 @@ public class CustomResource implements QuarkusTestResourceLifecycleManager, DevS

=== Executing against a running application

[WARNING]
====
This feature is considered experimental and is likely to change in future versions of Quarkus.
====

`@QuarkusIntegrationTest` supports executing tests against an already running instance of the application. This can be achieved by setting the
`quarkus.http.test-host` system property when running the tests.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,6 @@
* A launcher that simply sets the {@code quarkus.http.host} property based on the value {@code quarkus.http.test-host}
* in order to support the case of running integration tests against an already running application
* using RestAssured without any chances.
*
* This is highly experimental, so changes are to be expected.
*/
@SuppressWarnings("rawtypes")
public class TestHostLauncher implements ArtifactLauncher {
Expand Down