@toa.io/extensions.exposition 1.0.0-alpha.291 → 1.0.0-alpha.293

package/features/query.feature

@@ -1,389 +0,0 @@
-Feature: Queries
-
-  Background:
-    Given the `pots` database contains:
-      | _id                              | title      | volume | temperature |
-      | 4c4759e6f9c74da989d64511df42d6f4 | First pot  | 100    | 80          |
-      | 99988d785d7d445cad45dbf8531f560b | Second pot | 200    | 30          |
-      | a7edded6b2ab47a0aca9508cc4da4138 | Third pot  | 300    | 50          |
-      | bc6913d317334d76acd07d9f25f73535 | Fourth pot | 400    | 90          |
-
-  Scenario: Request with `id` query parameter
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /pot:
-          io:output: true
-          GET: observe
-      """
-    When the following request is received:
-      """
-      GET /pots/pot/?id=99988d785d7d445cad45dbf8531f560b HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      id: 99988d785d7d445cad45dbf8531f560b
-      title: Second pot
-      volume: 200
-      """
-
-  Scenario: Request with query criteria
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: true
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?criteria=volume<300&limit=10 HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      - id: 4c4759e6f9c74da989d64511df42d6f4
-        title: First pot
-        volume: 100
-      - id: 99988d785d7d445cad45dbf8531f560b
-        title: Second pot
-        volume: 200
-      """
-
-  Scenario: Request with `omit` and `limit`
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: true
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?omit=1&limit=2 HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      - id: 99988d785d7d445cad45dbf8531f560b
-        title: Second pot
-        volume: 200
-      - id: a7edded6b2ab47a0aca9508cc4da4138
-        title: Third pot
-        volume: 300
-      """
-
-  Scenario: Request with sorting
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: true
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?sort=volume:desc&limit=2 HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      - id: bc6913d317334d76acd07d9f25f73535
-        title: Fourth pot
-        volume: 400
-      - id: a7edded6b2ab47a0aca9508cc4da4138
-        title: Third pot
-        volume: 300
-      """
-
-  Scenario: Request to a route with path variable
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:id:
-          io:output: true
-          GET: observe
-      """
-    When the following request is received:
-      """
-      GET /pots/99988d785d7d445cad45dbf8531f560b/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      id: 99988d785d7d445cad45dbf8531f560b
-      title: Second pot
-      volume: 200
-      """
-
-  Scenario: Request to a route with path variable using OR operator
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:volume:
-          io:output: true
-          GET:
-            query:
-              criteria: ',volume==100'
-            endpoint: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/200/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      - id: 4c4759e6f9c74da989d64511df42d6f4
-        title: First pot
-        volume: 100
-        temperature: 80
-      - id: 99988d785d7d445cad45dbf8531f560b
-        title: Second pot
-        volume: 200
-      """
-
-  Scenario: Request to a route with predefined criteria
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /big:
-          io:output: true
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: volume>200
-      """
-    When the following request is received:
-      """
-      GET /pots/big/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      - id: a7edded6b2ab47a0aca9508cc4da4138
-        title: Third pot
-        volume: 300
-      - id: bc6913d317334d76acd07d9f25f73535
-        title: Fourth pot
-        volume: 400
-      """
-
-  Scenario: Request to a route with open criteria
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /big:
-          io:output: true
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: volume>200; # open criteria
-      """
-    When the following request is received:
-      """
-      GET /pots/big/?criteria=temperature>50 HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      - id: bc6913d317334d76acd07d9f25f73535
-        title: Fourth pot
-        volume: 400
-        temperature: 90
-      """
-
-  Scenario: Request to a route with predefined query
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /hottest2:
-          io:output: true
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: temperature>60
-              sort: temperature:desc
-              limit: 2
-      """
-    When the following request is received:
-      """
-      GET /pots/hottest2/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      - id: bc6913d317334d76acd07d9f25f73535
-        title: Fourth pot
-        volume: 400
-        temperature: 90
-      - id: 4c4759e6f9c74da989d64511df42d6f4
-        title: First pot
-        volume: 100
-        temperature: 80
-      """
-
-  Scenario: Query parameters
-    Given the `echo` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET:
-            io:output: true
-            query:
-              parameters: [name]
-            endpoint: compute
-      """
-    When the following request is received:
-      """
-      GET /echo/?name=John HTTP/1.1
-      host: nex.toa.io
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      Hello John
-      """
-
-  # a declared parameter is taken out of the query string before what is left of it is
-  # answered for. A route that declares nothing but parameters is not queryable, so what
-  # is left has to be nothing at all
-  Scenario: Query parameters beside an undeclared one
-    Given the `echo` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET:
-            io:output: true
-            query:
-              parameters: [name]
-            endpoint: compute
-      """
-    When the following request is received:
-      """
-      GET /echo/?name=John&foo=bar HTTP/1.1
-      host: nex.toa.io
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-
-      Query parameter 'foo' is not allowed
-      """
-    When the following request is received:
-      """
-      GET /echo/?foo=bar HTTP/1.1
-      host: nex.toa.io
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-
-      Query parameter 'foo' is not allowed
-      """
-
-  Scenario: Text search
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET:
-            io:output: true
-            query:
-              search: true
-            endpoint: enumerate
-          /non-searchable:
-            GET:
-              io:output: true
-              endpoint: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?search=fourth HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      - id: bc6913d317334d76acd07d9f25f73535
-        title: Fourth pot
-        volume: 400
-      """
-    And the reply does not contain:
-      """
-      - id: 4c4759e6f9c74da989d64511df42d6f4
-        title: First pot
-        volume: 100
-      """
-    When the following request is received:
-      """
-      GET /pots/non-searchable/?search=first HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-      """
-
-  Scenario: Querying sample
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET:
-            io:output: true
-            endpoint: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?sample=2 HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """

package/features/realtime.feature

@@ -1,34 +0,0 @@
-Feature: Realtime events
-
-  Background:
-    Given the Realtime is running with the following annotation:
-      """yaml
-      users.properties.sync: id
-      """
-    And the identity Bob is consuming realtime events
-
-  Scenario: Getting realtime events
-    Given the `users.properties` is running with the following manifest:
-      """yaml
-      exposition:
-        /:id:
-          anonymous: true
-          io:output: false
-          PATCH: transit
-      """
-    When the following request is received:
-      """
-      PATCH /users/properties/${{ Bob.id }}/ HTTP/1.1
-      host: nex.toa.io
-      content-type: application/yaml
-
-      newbie: false
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-    And the following event `users.properties.sync` is received by Bob:
-      """yaml
-      newbie: false
-      """

package/features/require.feature

@@ -1,66 +0,0 @@
-Feature: Request requirements
-
-  Scenario Outline: Require headers
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: true
-          POST: create
-          /one/:id:
-            require:header: if-match
-            PUT: transit
-          /two/:id:
-            require:headers: [if-match]
-            PUT: transit
-      """
-    When the following request is received:
-      """
-      POST /pots/ HTTP/1.1
-      host: nex.toa.io
-      content-type: application/yaml
-      accept: application/yaml
-
-      title: Hello
-      volume: 1.5
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-
-      id: ${{ id }}
-      """
-    When the following request is received:
-      """
-      PUT /pots/<variant>/${{ id }}/ HTTP/1.1
-      host: nex.toa.io
-      content-type: application/yaml
-      accept: text/plain
-
-      title: Hello
-      volume: 1.5
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-
-      Header required: if-match
-      """
-    When the following request is received:
-      """
-      PUT /pots/<variant>/${{ id }}/ HTTP/1.1
-      host: nex.toa.io
-      content-type: application/yaml
-      accept: text/plain
-      if-match: "1"
-
-      title: Bye
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-    Examples:
-      | variant |
-      | one     |
-      | two     |

package/features/response.feature

@@ -1,103 +0,0 @@
-Feature: Response
-
-  Scenario: Content negotiation
-    Given the annotation:
-      """yaml
-      /:
-        io:output: true
-        GET:
-          anonymous: true
-          dev:stub:
-            hello: world
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      accept: application/json
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      vary: origin, accept
-      content-type: application/json
-
-      {"hello":"world"}
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      vary: origin, accept
-      content-type: application/yaml
-
-      hello: world
-      """
-
-    # default is JSON
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      vary: origin, accept
-      content-type: application/json
-
-      {"hello":"world"}
-      """
-
-  Scenario: Error as YAML
-    Given the `echo` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: true
-          GET: error
-      """
-    When the following request is received:
-      """
-      GET /echo/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      422 Unprocessable Entity
-      content-type: application/yaml
-
-      code: CODE
-      message: message
-      """
-
-  Scenario: Error as MessagePack
-    Given the `echo` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: true
-          GET: error
-      """
-    When the following request is received:
-      """
-      GET /echo/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/msgpack
-      """
-    Then the following reply is sent:
-      """
-      422 Unprocessable Entity
-      content-type: application/msgpack
-      """
-    And response body contains MessagePack-encoded value:
-      """yaml
-      code: CODE
-      message: message
-      """