Tavern 1.0.3 (#8)

Tavern 1.0.3

Author: oliverbaehler

charts/tavern/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 name: tavern
 description: "Unofficial Tavern Helm Chart"
 type: application
-version: 0.1.1
+version: 0.1.2
 appVersion: 1.0.3
 home: "https://tavern.readthedocs.io/en/latest/"
 icon: "https://tavern.readthedocs.io/en/latest/_static/icon.png"

charts/tavern/README.md

@@ -1,11 +1,11 @@
-# Jira Software
+# Tavern
 
-![Version: 0.1.0](https://img.shields.io/badge/Version-0.1.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
-
-The chart is under active development and may contain bugs/unfinished documentation. Any testing/contributions are welcome! :)
+![Version: 0.1.2](https://img.shields.io/badge/Version-0.1.2-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
 
 Unofficial Tavern Helm Chart
 
+The chart is under active development and may contain bugs/unfinished documentation. Any testing/contributions are welcome! :)
+
 **Homepage:** <https://tavern.readthedocs.io/en/latest/>
 
 ## Maintainers
@@ -87,6 +87,8 @@ Tavern tests are implemented under the key `$.Values.tests`. Each element of thi
 
 This chart provides the functionality to create templates, which can be rereferenced. The templates allow you to implement go sprig logic and therefor might dramatically improve your tavern test suites.
 
+**NOTE**: While tavern statements use single `{ .. }` I had to replace the go sprig `\{\{ .. }}` as well with single `{ .. }` because of the documenting engine.
+
 ### Stage
 
 Tavern Stage templates are defined under the `$.Values.stageTemplates` key. You can define as many templates as you want below this key, just use the following semantic:
@@ -193,23 +195,35 @@ Referencing in a tavern test suite:
 ## Tavern Test Suites
 tests:
 
-  # Test Suite without Template
-  - name: "Base Call"
-    test:
-      stages:
-      request:
-        method: POST
-        json:
-          extraData: "extraValue"
-
-  # Single Tavern Stage for Suite
-  ## Will be last stage to be executed
+  # Single Tavern Stage for Suite using Template
   - name: "Product Suite"
+    template: "testtplname"
     values:
-      enable_base: false
+      get_products: [ "Shirt", "Shorts", "Socks" ]
     test:
       stages:
 
+        # Overtwrites/Merges with "Base Call" stage from Suite Template
+        # Merged Stages will be executed at the end of the suite eventhough
+        # they are the first stage defined in the template
+        - name: "Base Call"
+          stage:
+            request:
+              method: POST
+              json:
+                extraData: "extraValue"
+
+        # Single Tavern Stage for Suite (Will be last stage to be executed)
+        - name: "Test Admin User"
+          template: "http_get"
+          values:
+            endpoint: "user?name=admin"
+          stage:
+            response:
+              status_code:
+                - 200
+                - 301
+
 ```
 
 # Tavern Concepts

charts/tavern/README.md.gotmpl

@@ -46,7 +46,7 @@ Tavern tests are implemented under the key `$.Values.tests`. Each element of thi
 
 This chart provides the functionality to create templates, which can be rereferenced. The templates allow you to implement go sprig logic and therefor might dramatically improve your tavern test suites.
 
-**NOTE**: While tavern statements use single `{ .. }` I had to replace the go sprig `{{ .. }}` as well with single `{ .. }` because of the documenting engine.
+**NOTE**: While tavern statements use single `{ .. }` I had to replace the go sprig `\{\{ .. }}` as well with single `{ .. }` because of the documenting engine.
 
 ### Stage
 
@@ -154,23 +154,35 @@ Referencing in a tavern test suite:
 ## Tavern Test Suites
 tests:
 
-  # Test Suite without Template
-  - name: "Base Call"
-    test:
-      stages:
-      request:
-        method: POST
-        json:
-          extraData: "extraValue"
-
-  # Single Tavern Stage for Suite
-  ## Will be last stage to be executed
+  # Single Tavern Stage for Suite using Template
   - name: "Product Suite"
+    template: "testtplname"
     values:
-      enable_base: false
+      get_products: [ "Shirt", "Shorts", "Socks" ]
     test:
       stages:
 
+        # Overtwrites/Merges with "Base Call" stage from Suite Template
+        # Merged Stages will be executed at the end of the suite eventhough
+        # they are the first stage defined in the template
+        - name: "Base Call"
+          stage:
+            request:
+              method: POST
+              json:
+                extraData: "extraValue"
+
+        # Single Tavern Stage for Suite (Will be last stage to be executed)
+        - name: "Test Admin User"
+          template: "http_get"
+          values:
+            endpoint: "user?name=admin"
+          stage:
+            response:
+              status_code:
+                - 200
+                - 301
+
 ```
 
 # Tavern Concepts

charts/tavern/examples/advanced.yaml

@@ -112,8 +112,24 @@ testTemplates:
 ## Tavern Test Suites
 tests:
 
-  # Single Tavern Stage for Suite
-  ## Will be last stage to be executed
+  # Single Tavern Stage for Suite using Template
+  - name: "Standalone Suite"
+    test:
+      stages:
+        - name: "Standalone Stage"
+          request:
+            url: '{tavern.env_vars.HOST}/home'
+            method: GET
+            json:
+              country: {{ $.Values.common.country }}
+            headers:
+              content-type: "application/json"
+          response:
+            verify_response_with:
+              function: "testing_utils:message_says_hello"
+
+
+  # Single Tavern Stage for Suite using Template
   - name: "Product Suite"
     template: "get_api"
     values: