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 1b8702a Clarify test reports
1b8702a is described below
commit 1b8702a1831bb6b54bbbab5b41cd1e6d2a1130d6
Author: Bertrand Delacretaz <[email protected]>
AuthorDate: Wed Sep 5 14:58:06 2018 +0200
Clarify test reports
---
karate-http-testing/README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/karate-http-testing/README.md b/karate-http-testing/README.md
index c06aa37..b86f697 100644
--- a/karate-http-testing/README.md
+++ b/karate-http-testing/README.md
@@ -7,7 +7,7 @@ It is used as the basis of my adaptTo 2018 talk, [Karate, the
black belt of HTTP
To run these tests, start a Sling trunk instance on port 8080 (separately for
now - should be automated) and run `mvn clean test`.
-The Karate HTML output (like
`target/surefire-reports/TEST-sling.postservlet.createcontent.createContent.html`)
then displays the detailed HTTP interactions, it's very useful for debugging
the tests.
+The Karate HTML reports (`target/surefire-reports/TEST-sling.*.html`) then
display detailed HTTP interactions if tests fail, it's very useful for
troubleshooting.
The test scenarios are found *.feature files under `src/test`, like
[createContent.feature](src/test/java/sling/postservlet/createcontent/createContent.feature)
which should be self-explaining - that's the goal of all this.
