You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bd...@apache.org on 2018/07/30 15:51:47 UTC

[sling-whiteboard] branch master updated: more intro

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 87e638b  more intro
87e638b is described below

commit 87e638b3b48ab9683accf6e1e261c2e58ab67751
Author: Bertrand Delacretaz <bd...@apache.org>
AuthorDate: Mon Jul 30 17:51:45 2018 +0200

    more intro
---
 literate-http-testing/karate/README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/literate-http-testing/karate/README.md b/literate-http-testing/karate/README.md
index ef23334..7d34477 100644
--- a/literate-http-testing/karate/README.md
+++ b/literate-http-testing/karate/README.md
@@ -1,11 +1,15 @@
 Literate HTTP Testing with Karate
 =================================
 
+I'm experimenting with tools to write (very) readable tests for HTTP APIs, that could serve as reference documentation.
+
+This is the Karate variant of this experiment, using https://github.com/intuit/karate
+
 To run these tests, start a Sling trunk instance on port 8080 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 test definitions are found *.feature files under `src/test`, like [createContent.feature](src/test/java/sling/postservlet/createcontent/createContent.feature)
+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.
 
 Karate notes
 ------------