@toa.io/extensions.exposition 1.0.0-alpha.3 → 1.0.0-alpha.300

package/features/octets.workflows.feature

@@ -1,286 +0,0 @@
-Feature: Octets storage workflows
-
-  Scenario: Running a workflow
-    Given the `octets.tester` is running
-    And the annotation:
-      """yaml
-      /:
-        auth:anonymous: true
-        octets:context: octets
-        POST:
-          octets:store:
-            workflow:
-              - add-foo: octets.tester.foo
-                add-bar: octets.tester.bar
-              - add-baz: octets.tester.baz
-              - diversify: octets.tester.diversify
-        /*:
-          GET:
-            octets:fetch:
-              meta: true
-      """
-    When the stream of `lenna.ascii` is received with the following headers:
-      """
-      POST / HTTP/1.1
-      accept: application/yaml
-      content-type: application/octet-stream
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      content-type: multipart/yaml; boundary=cut
-
-      --cut
-      id: 10cf16b458f759e0d617f2f3d83599ff
-      type: application/octet-stream
-      size: 8169
-      --cut
-      add-foo: null
-      --cut
-      add-bar:
-        bar: baz
-      --cut
-      add-baz: null
-      --cut
-      diversify: null
-      --cut--
-      """
-    When the following request is received:
-      """
-      GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      accept: application/vnd.toa.octets.entry+yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      id: 10cf16b458f759e0d617f2f3d83599ff
-      type: application/octet-stream
-      size: 8169
-      meta:
-        foo: bar
-        bar: baz
-        baz: qux
-      """
-    When the following request is received:
-      """
-      GET /10cf16b458f759e0d617f2f3d83599ff.hello.png HTTP/1.1
-      """
-    Then the stream equals to `lenna.png` is sent with the following headers:
-      """
-      200 OK
-      content-type: image/png
-      content-length: 473831
-      """
-
-  Scenario: Getting error when running workflow on `store`
-    Given the `octets.tester` is running
-    Given the annotation:
-      """yaml
-      /:
-        auth:anonymous: true
-        octets:context: octets
-        POST:
-          octets:store:
-            workflow:
-              add-foo: octets.tester.foo
-              add-bar: octets.tester.err
-              add-baz: octets.tester.baz
-      """
-    When the stream of `lenna.ascii` is received with the following headers:
-      """
-      POST / HTTP/1.1
-      accept: application/yaml
-      content-type: application/octet-stream
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      content-type: multipart/yaml; boundary=cut
-
-      --cut
-      id: 10cf16b458f759e0d617f2f3d83599ff
-      type: application/octet-stream
-      size: 8169
-      --cut
-      add-foo: null
-      --cut
-      error:
-        step: add-bar
-        code: ERROR
-        message: Something went wrong
-      --cut--
-      """
-
-  Scenario: Running a workflow on `delete`
-    Given the `octets.tester` is running
-    And the annotation:
-      """yaml
-      /:
-        auth:anonymous: true
-        octets:context: octets
-        POST:
-          octets:store: ~
-        /*:
-          GET:
-            octets:fetch: ~
-          DELETE:
-            octets:delete:
-              workflow:
-                echo: octets.tester.echo
-      """
-    When the stream of `lenna.ascii` is received with the following headers:
-      """
-      POST / HTTP/1.1
-      content-type: application/octet-stream
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      """
-    When the following request is received:
-      """
-      DELETE /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      202 Accepted
-      content-type: multipart/yaml; boundary=cut
-
-      --cut
-      echo: 10cf16b458f759e0d617f2f3d83599ff
-      --cut--
-      """
-    When the following request is received:
-      """
-      GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      """
-
-  Scenario: Error in the workflow on `delete`
-    Given the `octets.tester` is running
-    And the annotation:
-      """yaml
-      /:
-        auth:anonymous: true
-        octets:context: octets
-        POST:
-          octets:store: ~
-        /*:
-          GET:
-            octets:fetch: ~
-          DELETE:
-            octets:delete:
-              workflow:
-                err: octets.tester.err
-      """
-    When the stream of `lenna.ascii` is received with the following headers:
-      """
-      POST / HTTP/1.1
-      content-type: application/octet-stream
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      """
-    When the following request is received:
-      """
-      DELETE /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      202 Accepted
-      content-type: multipart/yaml; boundary=cut
-
-      --cut
-      error:
-        step: err
-        code: ERROR
-        message: Something went wrong
-      --cut--
-      """
-    When the following request is received:
-      """
-      GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-
-  Scenario: Passing parameters to the workflow
-    Given the `octets.tester` is running
-    And the annotation:
-      """yaml
-      /:
-        /:a/:b:
-          auth:anonymous: true
-          octets:context: octets
-          POST:
-            octets:store:
-              workflow:
-                concat: octets.tester.concat
-      """
-    When the stream of `lenna.ascii` is received with the following headers:
-      """
-      POST /hello/world/ HTTP/1.1
-      accept: application/yaml
-      content-type: application/octet-stream
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      content-type: multipart/yaml; boundary=cut
-
-      --cut
-      id: 10cf16b458f759e0d617f2f3d83599ff
-      type: application/octet-stream
-      size: 8169
-      --cut
-      concat: hello world
-      --cut--
-      """
-
-  Scenario: Executing a workflow with `octets:workflow`
-    Given the `octets.tester` is running
-    And the annotation:
-      """yaml
-      /:
-        auth:anonymous: true
-        octets:context: octets
-        POST:
-          octets:store: ~
-        /*:
-          DELETE:
-            octets:workflow:
-              echo: octets.tester.echo
-      """
-    When the stream of `lenna.ascii` is received with the following headers:
-      """
-      POST / HTTP/1.1
-      content-type: application/octet-stream
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      """
-    When the following request is received:
-      """
-      DELETE /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      202 Accepted
-      content-type: multipart/yaml; boundary=cut
-
-      --cut
-      echo: 10cf16b458f759e0d617f2f3d83599ff
-      --cut--
-      """

package/features/queries.feature

@@ -1,214 +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:
-          GET: observe
-      """
-    When the following request is received:
-      """
-      GET /pots/pot/?id=99988d785d7d445cad45dbf8531f560b HTTP/1.1
-      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:
-        /:
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?criteria=volume<300&limit=10 HTTP/1.1
-      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:
-        /:
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?omit=1&limit=2 HTTP/1.1
-      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:
-        /:
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?sort=volume:desc&limit=2 HTTP/1.1
-      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 a path variable
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:id:
-          GET: observe
-      """
-    When the following request is received:
-      """
-      GET /pots/99988d785d7d445cad45dbf8531f560b/ HTTP/1.1
-      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 predefined criretia
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /big:
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: volume>200
-      """
-    When the following request is received:
-      """
-      GET /pots/big/ HTTP/1.1
-      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 combined criteria
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /big:
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: volume>200; # open criteria
-      """
-    When the following request is received:
-      """
-      GET /pots/big/?criteria=temperature>50 HTTP/1.1
-      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:
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: temperature>60
-              sort: temperature:desc
-              limit: 2
-      """
-    When the following request is received:
-      """
-      GET /pots/hottest2/ HTTP/1.1
-      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
-      """

package/features/response.feature

@@ -1,65 +0,0 @@
-Feature: Response
-
-  Scenario: Content negotiation
-    Given the annotation:
-      """yaml
-      /:
-        GET:
-          anonymous: true
-          dev:stub: hello
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      accept: application/json
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/json
-      vary: accept
-      """
-
-  Scenario: Error as YAML
-    Given the `echo` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET: error
-      """
-    When the following request is received:
-      """
-      GET /echo/ HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      409 Conflict
-      content-type: application/yaml
-
-      code: CODE
-      message: message
-      """
-
-  Scenario: Error as MessagePack
-    Given the `echo` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET: error
-      """
-    When the following request is received:
-      """
-      GET /echo/ HTTP/1.1
-      accept: application/msgpack
-      """
-    Then the following reply is sent:
-      """
-      409 Conflict
-      content-type: application/msgpack
-      """
-    And response body contains MessagePack-encoded value:
-      """yaml
-      code: CODE
-      message: message
-      """

package/features/routes.feature

@@ -1,126 +0,0 @@
-Feature: Routes
-
-  Scenario Outline: Basic routes
-    Given the `greeter` is running with the following manifest:
-      """yaml
-      namespace: basic
-
-      exposition:
-        /strict:
-          GET:
-            endpoint: greet
-        /shortcuts:
-          /operation:
-            GET: greet
-      """
-    When the following request is received:
-      """
-      GET /basic/greeter<route> HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      Hello
-      """
-    Examples:
-      | route                 |
-      | /strict/              |
-      | /shortcuts/operation/ |
-
-  Scenario: Basic routes within default namespace
-    Given the `greeter` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET: greet
-      """
-    When the following request is received:
-      """
-      GET /greeter/ HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      Hello
-      """
-
-  Scenario: Wildcard routes
-    Given the `greeter` is running with the following manifest:
-      """yaml
-      exposition:
-        /*:
-          GET: greet
-        /foo/*/bar:
-          GET: greet
-      """
-    When the following request is received:
-      """
-      GET /greeter/baz/ HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      Hello
-      """
-    When the following request is received:
-      """
-      GET /greeter/baz/qux/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      """
-    When the following request is received:
-      """
-      GET /greeter/foo/baz/bar/ HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      Hello
-      """
-
-  Scenario: Routes with naming conflicts
-    Given the Gateway is running
-    And the `users` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          POST: create
-      """
-    And the `users.properties` is running with the following manifest:
-      """yaml
-      exposition:
-        /:id:
-          GET: observe
-      """
-    When the following request is received:
-      """
-      GET /users/properties/b5534021e30042259badffbd1831e472/ HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      newbie: false
-      """
-    When the following request is received:
-      """
-      POST /users/ HTTP/1.1
-      content-type: application/yaml
-
-      name: Alice
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      """

package/features/steps/Captures.ts

@@ -1,6 +0,0 @@
-import * as http from '@toa.io/agent'
-import { binding } from 'cucumber-tsflow'
-
-@binding()
-export class Captures extends http.Captures {
-}

package/features/steps/Common.ts

@@ -1,10 +0,0 @@
-import { binding, given } from 'cucumber-tsflow'
-import { timeout } from '@toa.io/generic'
-
-@binding()
-export class Common {
-  @given('after {float} second(s)')
-  public async timeout (interval: number): Promise<void> {
-    await timeout(interval * 1000)
-  }
-}