@toa.io/extensions.exposition 1.0.0-alpha.19 → 1.0.0-alpha.190

package/features/errors.feature

@@ -8,6 +8,7 @@ Feature: Errors
     When the following request is received:
       """
       GET <path> HTTP/1.1
+      host: nex.toa.io
       accept: text/plain
       """
     Then the following reply is sent:
@@ -30,6 +31,7 @@ Feature: Errors
     When the following request is received:
       """
       GET /basic/greeter HTTP/1.1
+      host: nex.toa.io
       accept: application/json
       """
     Then the following reply is sent:
@@ -37,7 +39,7 @@ Feature: Errors
       404 Not Found
       content-type: application/json
 
-      "Trailing slash is required."
+      "Trailing slash is required"
       """
 
   Scenario: Missing method
@@ -45,6 +47,7 @@ Feature: Errors
     When the following request is received:
       """
       PATCH /greeter/ HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -56,6 +59,7 @@ Feature: Errors
     When the following request is received:
       """
       COPY /basic/greeter/ HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -73,6 +77,7 @@ Feature: Errors
     When the following request is received:
       """
       POST /pots/ HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       content-type: application/yaml
 
@@ -97,6 +102,7 @@ Feature: Errors
     When the following request is received:
       """
       GET /pots/?limit=1001 HTTP/1.1
+      host: nex.toa.io
       accept: text/plain
       """
     Then the following reply is sent:
@@ -104,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
@@ -115,11 +121,12 @@ Feature: Errors
           GET:
             endpoint: enumerate
             query:
-              criteria: temerature>60
+              criteria: temperature>60
       """
     When the following request is received:
       """
       GET /pots/hot/?criteria=volume>500 HTTP/1.1
+      host: nex.toa.io
       accept: text/plain
       """
     Then the following reply is sent:
@@ -127,7 +134,7 @@ Feature: Errors
       400 Bad Request
       content-type: text/plain
 
-      Query criteria is closed.
+      Query criteria is closed
       """
 
   Scenario: Additional query parameters
@@ -141,6 +148,7 @@ Feature: Errors
     When the following request is received:
       """
       GET /pots/?foo=bar HTTP/1.1
+      host: nex.toa.io
       accept: text/plain
       """
     Then the following reply is sent:
@@ -148,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
@@ -160,6 +168,7 @@ Feature: Errors
     When the following request is received:
       """
       GET / HTTP/1.1
+      host: nex.toa.io
       authorization: Basic
       accept: text/plain
       """
@@ -167,7 +176,7 @@ Feature: Errors
       """
       401 Unauthorized
 
-      Malformed authorization header.
+      Malformed authorization header
       """
 
   Scenario Outline: Exception is thrown (debug: <debug>)
@@ -182,6 +191,7 @@ Feature: Errors
     When the following request is received:
       """
       GET / HTTP/1.1
+      host: nex.toa.io
       accept: text/plain
       """
     Then the following reply is sent:
@@ -206,9 +216,22 @@ Feature: Errors
     When the following request is received:
       """
       GET / HTTP/1.1
+      host: nex.toa.io
       accept: image/jpeg
       """
     Then the following reply is sent:
       """
       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

@@ -14,6 +14,7 @@ Feature: Optimistic concurrency control
     When the following request is received:
       """
       POST /pots/ HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       content-type: application/yaml
 
@@ -30,6 +31,7 @@ Feature: Optimistic concurrency control
     When the following request is received:
       """
       GET /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
@@ -39,6 +41,7 @@ Feature: Optimistic concurrency control
     When the following request is received:
       """
       GET /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
       if-none-match: "1"
       """
     Then the following reply is sent:
@@ -49,6 +52,7 @@ Feature: Optimistic concurrency control
     When the following request is received:
       """
       PUT /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
       content-type: application/yaml
       if-match: "38"
 
@@ -61,6 +65,7 @@ Feature: Optimistic concurrency control
     When the following request is received:
       """
       PUT /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
       content-type: application/yaml
       if-match: "1"
 
@@ -72,6 +77,114 @@ 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
+      """
+    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
+      etag: ${{ etag }}
+      """
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      if-none-match: ${{ etag }}
+      """
+    Then the following reply is sent:
+      """
+      304 Not Modified
+      etag: ${{ etag }}
+      """
+
+  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: Unexpected `if-match` format
     Given the `pots` is running with the following manifest:
       """yaml
@@ -83,6 +196,7 @@ Feature: Optimistic concurrency control
     When the following request is received:
       """
       PUT /pots/fa177da8393544139915795816ad6b97/ HTTP/1.1
+      host: nex.toa.io
       accept: text/plain
       content-type: application/yaml
       if-match: "oopsie"
@@ -93,5 +207,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
+      """

package/features/identity.bans.feature

@@ -5,9 +5,9 @@ Feature: Bans
     Given the `identity.basic` database contains:
     # developer:secret
     # user:12345
-      | _id                              | username  | password                                                     | _deleted |
-      | efe3a65ebbee47ed95a73edd911ea328 | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | null     |
-      | e8e4f9c2a68d419b861403d71fabc915 | user      | $2b$10$Frszmrmsz9iwSXzBbRRMKeDVKsNxozkrLNSsN.SnVC.KPxLtQr/bK | null     |
+      | _id                              | authority | username  | password                                                     | _deleted |
+      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O | null     |
+      | e8e4f9c2a68d419b861403d71fabc915 | nex       | user      | $2b$10$Frszmrmsz9iwSXzBbRRMKeDVKsNxozkrLNSsN.SnVC.KPxLtQr/bK | null     |
     And the `identity.bans` database is empty
 
   Scenario: Banning an Identity
@@ -31,6 +31,7 @@ Feature: Bans
     When the following request is received:
       """
       GET /e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Basic dXNlcjoxMjM0NQ==
       """
     Then the following reply is sent:
@@ -41,6 +42,7 @@ Feature: Bans
     When the following request is received:
       """
       PUT /identity/bans/e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
       content-type: application/yaml
 
@@ -55,6 +57,7 @@ Feature: Bans
     When the following request is received:
       """
       GET /e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Basic dXNlcjoxMjM0NQ==
       """
     Then the following reply is sent:
@@ -65,6 +68,7 @@ Feature: Bans
     When the following request is received:
       """
       GET /e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Token ${{ token }}
       """
     Then the following reply is sent:
@@ -74,6 +78,7 @@ Feature: Bans
     When the following request is received:
       """
       PUT /identity/bans/e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
       content-type: application/yaml
 
@@ -86,6 +91,7 @@ Feature: Bans
     When the following request is received:
       """
       GET /e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Basic dXNlcjoxMjM0NQ==
       """
     Then the following reply is sent:
@@ -98,6 +104,7 @@ Feature: Bans
     When the following request is received:
       """
       PUT /identity/bans/e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
       content-type: application/yaml
 
@@ -110,6 +117,7 @@ Feature: Bans
     When the following request is received:
       """
       GET /e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Basic dXNlcjoxMjM0NQ==
       """
     Then the following reply is sent:
@@ -120,6 +128,7 @@ Feature: Bans
     When the following request is received:
       """
       GET /e8e4f9c2a68d419b861403d71fabc915/ HTTP/1.1
+      host: nex.toa.io
       authorization: Token ${{ new_token }}
       """
     Then the following reply is sent: