From 9f7cd14f15b06c1531bf8259f10d96f605c5ba44 Mon Sep 17 00:00:00 2001 From: Paul Sanwald Date: Fri, 9 Mar 2018 11:54:59 -0800 Subject: [PATCH] Update Gradle Testing Docs (#28970) Attempting to run the REST tests, I noticed the testing instructions in the `TESTING.asciidoc` were outdated, so I fixed the paths. Steps I took to test: * Ran `./gradlew :distribution:packages:rpm:assemble` and make sure RPM is created in `./distribution/packages/rpm/build/distributions/` * Ran testing commands and verified the REST tests ran. --- TESTING.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/TESTING.asciidoc b/TESTING.asciidoc index f1e444dbde6..f7725bd17d7 100644 --- a/TESTING.asciidoc +++ b/TESTING.asciidoc @@ -270,14 +270,14 @@ The REST tests are run automatically when executing the "./gradlew check" comman REST tests use the following command: --------------------------------------------------------------------------- -./gradlew :distribution:integ-test-zip:integTest \ +./gradlew :distribution:archives:integ-test-zip:integTest \ -Dtests.class="org.elasticsearch.test.rest.*Yaml*IT" --------------------------------------------------------------------------- A specific test case can be run with --------------------------------------------------------------------------- -./gradlew :distribution:integ-test-zip:integTest \ +./gradlew :distribution:archives:integ-test-zip:integTest \ -Dtests.class="org.elasticsearch.test.rest.*Yaml*IT" \ -Dtests.method="test {p0=cat.shards/10_basic/Help}" --------------------------------------------------------------------------- @@ -407,7 +407,7 @@ destructive. When working with a single package it's generally faster to run its tests in a tighter loop than Gradle provides. In one window: -------------------------------- -./gradlew :distribution:rpm:assemble +./gradlew :distribution:packages:rpm:assemble -------------------------------- and in another window: