@toa.io/extensions.exposition 1.0.0-alpha.27 → 1.0.0-alpha.271

package/features/dynamic.feature

@@ -9,6 +9,7 @@ Feature: Dynamic tree updates
     Given the Gateway is running
     And the `pots` is running with the following manifest:
       """yaml
+      version: 1
       exposition:
         /:
           io:output: true
@@ -27,6 +28,7 @@ Feature: Dynamic tree updates
     Then the `pots` is stopped
     Then the `pots` is running with the following manifest:
       """yaml
+      version: 2
       exposition:
         /:
           io:output: true
@@ -43,9 +45,84 @@ Feature: Dynamic tree updates
       200 OK
       """
 
+  Scenario: Repeat routes
+    Given the Gateway is running
+    And the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          GET: enumerate
+      """
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+    Then the `pots` is stopped
+    And the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          GET: enumerate
+      """
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+
+  Scenario: Stale branch expires
+    Given the branch TTL is 5 seconds
+    And the Gateway is running
+    And the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          GET: enumerate
+      """
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+    Then the `pots` is stopped
+    And after 6 seconds
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: text/plain
+      """
+    Then the following reply is sent:
+      """
+      404 Not Found
+
+      Route not found
+      """
+
   Scenario: Updating routes with conflict
+    Given the Gateway is running
     And the `pots` is running with the following manifest:
       """yaml
+      version: 1.0.0
       exposition:
         /:id:
           io:output: true
@@ -54,6 +131,7 @@ Feature: Dynamic tree updates
     Then the `pots` is stopped
     Then the `pots` is running with the following manifest:
       """yaml
+      version: 1.1.0
       exposition:
         /:
           io:output: true
@@ -77,8 +155,10 @@ Feature: Dynamic tree updates
       """
 
   Scenario: Updating method mapping
-    Given the `pots` is running with the following manifest:
+    Given the Gateway is running
+    And the `pots` is running with the following manifest:
       """yaml
+      version: a
       exposition:
         /big:
           io:output: true
@@ -90,6 +170,7 @@ Feature: Dynamic tree updates
     Then the `pots` is stopped
     Then the `pots` is running with the following manifest:
       """yaml
+      version: b
       exposition:
         /big:
           io:output: true

package/features/errors.feature

@@ -39,7 +39,7 @@ Feature: Errors
       404 Not Found
       content-type: application/json
 
-      "Trailing slash is required."
+      "Trailing slash is required"
       """
 
   Scenario: Missing method
@@ -110,7 +110,7 @@ Feature: Errors
       400 Bad Request
       content-type: text/plain
 
-      Query limit must be between 1 and 1000 inclusive.
+      Query limit must be between 1 and 100 inclusive
       """
 
   Scenario: Closed query criteria
@@ -121,7 +121,7 @@ Feature: Errors
           GET:
             endpoint: enumerate
             query:
-              criteria: temerature>60
+              criteria: temperature>60
       """
     When the following request is received:
       """
@@ -156,7 +156,7 @@ Feature: Errors
       400 Bad Request
       content-type: text/plain
 
-      Query must NOT have additional properties
+      Query Property foo is not expected to be here
       """
 
   Scenario: Malformed authorization header
@@ -176,7 +176,7 @@ Feature: Errors
       """
       401 Unauthorized
 
-      Malformed authorization header.
+      Malformed authorization header
       """
 
   Scenario Outline: Exception is thrown (debug: <debug>)
@@ -223,3 +223,15 @@ Feature: Errors
       """
       406 Not Acceptable
       """
+
+  Scenario: Not acceptable request with error
+    When the following request is received:
+      """
+      GET /robots.txt HTTP/1.1
+      host: nex.toa.io
+      accept: text/html
+      """
+    Then the following reply is sent:
+      """
+      404 Not Found
+      """

package/features/etag.feature

@@ -77,6 +77,203 @@ Feature: Optimistic concurrency control
       etag: "2"
       """
 
+  Scenario: Using etag with enumeration
+    Given the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          GET: enumerate
+      """
+    # sorted and bounded, or the collection does not enumerate the same way twice
+    When the following request is received:
+      """
+      GET /pots/?sort=id:asc&limit=2 HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: "${{ etag }}"
+      """
+    # the same representation must be asked for, the tag identifies it
+    When the following request is received:
+      """
+      GET /pots/?sort=id:asc&limit=2 HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      if-none-match: "${{ etag }}"
+      """
+    Then the following reply is sent:
+      """
+      304 Not Modified
+      etag: "${{ etag }}"
+      """
+
+  Scenario: `etag` of a reply that carries no version
+    Given the `echo` is running with the following manifest:
+      """yaml
+      exposition:
+        /:name:
+          io:output: true
+          GET: compute
+      """
+    When the following request is received:
+      """
+      GET /echo/Bob/ HTTP/1.1
+      host: nex.toa.io
+      accept: text/plain
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: "2d6a12ffc0a952fbd09f8909de4e0e4b20ba2b906cd12ac22bbef4ee5bd9003e"
+
+      Hello Bob
+      """
+    When the following request is received:
+      """
+      GET /echo/Bob/ HTTP/1.1
+      host: nex.toa.io
+      accept: text/plain
+      if-none-match: "2d6a12ffc0a952fbd09f8909de4e0e4b20ba2b906cd12ac22bbef4ee5bd9003e"
+      """
+    Then the following reply is sent:
+      """
+      304 Not Modified
+      etag: "2d6a12ffc0a952fbd09f8909de4e0e4b20ba2b906cd12ac22bbef4ee5bd9003e"
+      """
+    # the tag identifies the representation, which is what `vary: accept` says
+    When the following request is received:
+      """
+      GET /echo/Bob/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      if-none-match: "2d6a12ffc0a952fbd09f8909de4e0e4b20ba2b906cd12ac22bbef4ee5bd9003e"
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: "360c52c694c418b4a793a4815e611206ab17fe04836351a65638a15d1491810b"
+      """
+
+  Scenario: Weak `etag`
+    Given the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          POST: create
+          /:id:
+            GET: observe
+            PUT: transit
+      """
+    When the following request is received:
+      """
+      POST /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      content-type: application/yaml
+
+      title: Hello
+      volume: 1.5
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      etag: "1"
+
+      id: ${{ id }}
+      """
+    When the following request is received:
+      """
+      GET /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: "1"
+      """
+    When the following request is received:
+      """
+      GET /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      if-none-match: W/"1"
+      """
+    Then the following reply is sent:
+      """
+      304 Not Modified
+      etag: W/"1"
+      """
+    When the following request is received:
+      """
+      PUT /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      content-type: application/yaml
+      if-match: W/"38"
+
+      volume: 2.5
+      """
+    Then the following reply is sent:
+      """
+      412 Precondition Failed
+      """
+    When the following request is received:
+      """
+      PUT /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      content-type: application/yaml
+      if-match: W/"1"
+
+      volume: 2.5
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: "2"
+      """
+
+  Scenario: Hash `if-none-match` on versioned resource
+    Given the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          POST: create
+          /:id:
+            GET: observe
+      """
+    When the following request is received:
+      """
+      POST /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      content-type: application/yaml
+
+      title: Hello
+      volume: 1.5
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      etag: "1"
+
+      id: ${{ id }}
+      """
+    When the following request is received:
+      """
+      GET /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      if-none-match: "ef4a2abb4c896c06d0ab3037427e6c7c3e9a32a0c982eee2df68679babd96da3"
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: "1"
+      """
+
   Scenario: Unexpected `if-match` format
     Given the `pots` is running with the following manifest:
       """yaml
@@ -99,5 +296,30 @@ Feature: Optimistic concurrency control
       """
       400 Bad Request
 
-      Invalid ETag.
+      Invalid ETag
+      """
+
+  Scenario: Etag with non-queryable operation
+    Given the `echo` is running with the following manifest:
+      """yaml
+      exposition:
+        /:foo/:id:
+          GET:
+            io:output: true
+            map:headers:
+              name: if-match
+            endpoint: affect
+      """
+    When the following request is received:
+      """
+      GET /echo/foo/Bob/ HTTP/1.1
+      host: nex.toa.io
+      accept: text/plain
+      if-match: "1"
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      Hello "1"
       """

package/features/flow.feature

@@ -0,0 +1,148 @@
+Feature: Request flow
+
+  Scenario: Fetching URL
+    Given the `octets.tester` is running
+    And the annotation:
+      """yaml
+      /:
+        octets:context: octets
+        /:type:
+          GET:
+            anonymous: true
+            io:output: true
+            flow:fetch: octets.tester.redirect
+      """
+    When the following request is received:
+      """
+      GET /rfc HTTP/1.1
+      host: nex.toa.io
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      content-type: text/plain
+
+      Faster Than Light Speed Protocol (FLIP)
+      """
+    When the following request is received:
+      """
+      GET /img HTTP/1.1
+      host: nex.toa.io
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      content-type: image/svg+xml
+      """
+    When the following request is received:
+      """
+      GET /err HTTP/1.1
+      host: nex.toa.io
+      """
+    Then the following reply is sent:
+      """
+      404 Not Found
+      """
+
+  Scenario: Composing a stream
+    Given the `sequences` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          flow:compose:
+            a: $[0]
+            b: $[1]
+            c: $[2]
+            sum: $[0] + $[1] + $[2]
+            str: \hello
+            num: 1
+            arr:
+              - $[0]
+              - $[1]
+              - $[2]
+              - $[0] + $[1] + $[2]
+            copy: $
+          POST: numbers
+      """
+    When the following request is received:
+      """
+      POST /sequences/ HTTP/1.1
+      host: nex.toa.io
+      content-type: text/plain
+      accept: application/yaml
+
+      3
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      content-type: application/yaml
+
+      a: 0
+      b: 1
+      c: 2
+      sum: 3
+      str: hello
+      num: 1
+      arr:
+        - 0
+        - 1
+        - 2
+        - 3
+      copy:
+        - 0
+        - 1
+        - 2
+      """
+
+  Scenario: Composing with multiple possible shapes
+    Given the `sequences` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          flow:compose:
+            - a: $[0].b.c
+            - b: $[0]
+          POST: numbers
+      """
+    When the following request is received:
+      """
+      POST /sequences/ HTTP/1.1
+      host: nex.toa.io
+      content-type: text/plain
+      accept: application/yaml
+
+      3
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      content-type: application/yaml
+
+      b: 0
+      """
+
+  Scenario: Composing with text value
+    Given the `sequences` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          flow:compose: $[1]
+          POST: numbers
+      """
+    When the following request is received:
+      """
+      POST /sequences/ HTTP/1.1
+      host: nex.toa.io
+      content-type: text/plain
+      accept: application/yaml
+
+      3
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      content-type: application/yaml
+
+      1
+      """