This is an automated email from the ASF dual-hosted git repository.
bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git
The following commit(s) were added to refs/heads/master by this push:
new 4fc717c Adapt for Sling 10 release
4fc717c is described below
commit 4fc717ca997b1dd79cd401a675f0b24404d2784c
Author: Bertrand Delacretaz <[email protected]>
AuthorDate: Thu Sep 6 13:02:56 2018 +0200
Adapt for Sling 10 release
---
karate-http-testing/README.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/karate-http-testing/README.md b/karate-http-testing/README.md
index 9cb1f95..91b8c67 100644
--- a/karate-http-testing/README.md
+++ b/karate-http-testing/README.md
@@ -15,6 +15,8 @@ See also https://github.com/bdelacretaz/karate-mini-mocks
which is a minimal dem
Running the tests
-----------------
+For now, the tests require a Sling instance to be started separately on port
8080. The simplest way to do that is to download the "Sling Starter Standalone"
release 10 jar file from http://sling.apache.org/downloads.cgi and start it
with `java -jar org.apache.sling.starter.*.jar` in an empty folder. To reset
the state of that instance, if needed, stop it and delete the `sling` folder
that's created when that jar file starts.
+
The karate "feature" test files are triggered by JUnit tests which have the
`@RunWith(Karate.class)` annotation, like
[SlingTest.java](src/test/java/sling/SlingTest.java), so they run as part of
the standard Maven unit or integration tests.
To run test features which have a specific tag, use for example
@@ -27,4 +29,4 @@ And to run the Gatling performance tests, use
Karate notes
------------
-The Karate UI is described at https://github.com/intuit/karate/wiki/Karate-UI
\ No newline at end of file
+The Karate UI is described at https://github.com/intuit/karate/wiki/Karate-UI
