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

package/features/body.feature

@@ -1,45 +0,0 @@
-Feature: Request body
-
-  Scenario: Creating an entity
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          POST: transit
-      """
-    When the following request is received:
-      """
-      POST /pots/ HTTP/1.1
-      content-type: application/yaml
-
-      title: Hello
-      volume: 1.5
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      """
-
-  Scenario Outline: Path segment as input for <operation>
-    Given the `echo` is running with the following manifest:
-      """yaml
-      exposition:
-        /:name:
-          GET: <operation>
-      """
-    When the following request is received:
-      """
-      GET /echo/world/ HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: text/plain
-
-      Hello world
-      """
-    Examples:
-      | operation |
-      | compute   |
-      | affect    |

package/features/cache.feature

@@ -1,160 +0,0 @@
-Feature: Caching
-
-  Background:
-    Given the `identity.basic` database contains:
-      # developer:secret
-      # user:12345
-      | _id                              | username  | password                                                     |
-      | b70a7dbca6b14a2eaac8a9eb4b2ff4db | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
-    Given the `identity.roles` database contains:
-      | _id                              | identity                         | role      |
-      | 775a648d054e4ce1a65f8f17e5b51803 | b70a7dbca6b14a2eaac8a9eb4b2ff4db | developer |
-
-  Scenario: Caching successful response
-    Given the annotation:
-      """yaml
-      /:
-        anonymous: true
-        GET:
-          cache:control: max-age=60000
-          dev:stub: hello
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: text/plain
-      cache-control: max-age=60000
-
-      hello
-      """
-
-  Scenario: Nested cache directives
-    Given the annotation:
-      """yaml
-      /:
-        cache:control: max-age=30000
-        GET:
-          anonymous: true
-          dev:stub: hello
-        /foo:
-          auth:role: developer
-          GET:
-            dev:stub: hello
-        /bar:
-          auth:role: developer
-          cache:control: max-age=60000, public
-          GET:
-            dev:stub: hello
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: text/plain
-      cache-control: max-age=30000
-
-      hello
-      """
-    When the following request is received:
-      """
-      GET /foo/ HTTP/1.1
-      accept: text/plain
-      authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: text/plain
-      cache-control: private, max-age=30000
-
-      hello
-      """
-    When the following request is received:
-      """
-      GET /bar/ HTTP/1.1
-      accept: text/plain
-      authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: text/plain
-      cache-control: no-cache, max-age=60000, public
-
-      hello
-      """
-    And the reply does not contain:
-      """
-      cache-control: private, max-age=30000
-      """
-
-  Scenario: Cache-control is not added when request is unsafe
-    Given the annotation:
-      """yaml
-      /:
-        anonymous: true
-        cache:control: max-age=60000
-        POST:
-          dev:stub: hello
-      """
-    When the following request is received:
-      """
-      POST / HTTP/1.1
-      accept: application/yaml
-      """
-    Then the reply does not contain:
-      """
-      cache-control: max-age=60000
-      """
-
-  Scenario: Cache-control is added without implicit modifications
-    Given the annotation:
-      """yaml
-      /:
-        auth:role: developer
-        cache:exact: max-age=60000, public
-        GET:
-          dev:stub: hello
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
-      accept: text/plain
-
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: text/plain
-      cache-control: max-age=60000, public
-
-      hello
-      """
-
-  Scenario: Response without caching
-    Given the annotation:
-      """yaml
-      /:
-        anonymous: true
-        GET:
-          dev:stub: hello
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      accept: text/plain
-      """
-    Then the reply does not contain:
-      """
-      cache-control:
-      """

package/features/cors.feature

@@ -1,72 +0,0 @@
-Feature: CORS Support
-
-  Scenario: Using CORS
-    Given the annotation:
-      """yaml
-      /:
-        anonymous: true
-        /foo:
-          GET:
-            dev:stub: Hello
-      """
-    When the following request is received:
-      """
-      OPTIONS / HTTP/1.1
-      origin: https://hello.world
-      """
-    Then the following reply is sent:
-      """
-      204 No Content
-      access-control-allow-origin: https://hello.world
-      access-control-allow-methods: GET, POST, PUT, PATCH, DELETE
-      access-control-allow-headers: accept, authorization, content-type
-      access-control-allow-credentials: true
-      access-control-max-age: 3600
-      cache-control: public, max-age=3600
-      vary: origin
-      """
-    When the following request is received:
-      """
-      GET /foo/ HTTP/1.1
-      origin: https://hello.world
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      access-control-allow-origin: https://hello.world
-      access-control-expose-headers: authorization, content-type, content-length, etag
-      vary: origin
-      """
-
-  Scenario: Errors contain CORS headers
-    Given the annotation:
-      """yaml
-      /:
-        /foo:
-          GET:
-            dev:stub: Hello
-      """
-    When the following request is received:
-      """
-      GET /bar/ HTTP/1.1
-      origin: https://hello.world
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      access-control-allow-origin: https://hello.world
-      access-control-expose-headers: authorization, content-type, content-length, etag
-      vary: origin
-      """
-    When the following request is received:
-      """
-      GET /foo/ HTTP/1.1
-      origin: https://hello.world
-      """
-    Then the following reply is sent:
-      """
-      401 Unauthorized
-      access-control-allow-origin: https://hello.world
-      access-control-expose-headers: authorization, content-type, content-length, etag
-      vary: origin
-      """

package/features/directives.feature

@@ -1,56 +0,0 @@
-Feature: Directives
-
-  Scenario: Basic directive
-    Given the annotation:
-      """yaml
-      /:
-        anonymous: true
-        GET:
-          dev:stub:
-            hello: world
-      """
-    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
-
-      {"hello":"world"}
-      """
-
-  Scenario: Nested routes
-    Given the annotation:
-      """yaml
-      /:
-        anonymous: true
-        dev:stub:
-          hello: again
-        GET: {}
-        /pots:
-          GET: {}
-      """
-    When the following request is received:
-      """
-      GET /pots/ HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      hello: again
-      """
-    When the following request is received:
-      """
-      GET /pots/non-existent/ HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      """

package/features/dynamic.feature

@@ -1,99 +0,0 @@
-Feature: Dynamic tree updates
-
-  Background:
-    Given the `pots` database contains:
-      | _id                              | title     | volume | temperature |
-      | 4c4759e6f9c74da989d64511df42d6f4 | First pot | 100    | 80          |
-
-  Scenario: Updating routes
-    Given the Gateway is running
-    And the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          isolated: true
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      401 Unauthorized
-      """
-    Then the `pots` is stopped
-    Then the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/ HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-
-  Scenario: Updating routes with conflict
-    And the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:id:
-          GET: observe
-      """
-    Then the `pots` is stopped
-    Then the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:id:
-          GET: observe
-        /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
-      """
-
-  Scenario: Updating method mapping
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /big:
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: volume>200 # closed
-      """
-    Then the `pots` is stopped
-    Then the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /big:
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: volume>200; # open
-      """
-    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
-      """

package/features/errors.feature

@@ -1,211 +0,0 @@
-Feature: Errors
-
-  Scenario Outline: Missing routes
-    Given the `greeter` is running with the following manifest:
-      """yaml
-      namespace: basic
-      """
-    When the following request is received:
-      """
-      GET <path> HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      """
-    Examples:
-      | path                                 |
-      | /basic/greeter/non-existent-segment/ |
-      | /basic/non-existent-component/       |
-      | /non-existent-namespace/             |
-
-  Scenario: Missing trailing slash
-    Given the `greeter` is running with the following manifest:
-      """yaml
-      namespace: basic
-      """
-    When the following request is received:
-      """
-      GET /basic/greeter HTTP/1.1
-      accept: application/json
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      content-type: application/json
-
-      "Trailing slash is required."
-      """
-
-  Scenario: Missing method
-    Given the `greeter` is running
-    When the following request is received:
-      """
-      PATCH /greeter/ HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """http
-      405 Method Not Allowed
-      """
-
-  Scenario: Unsupported method
-    When the following request is received:
-      """
-      COPY /basic/greeter/ HTTP/1.1
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """http
-      501 Not Implemented
-      """
-
-  Scenario: Request body does not match input schema
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          POST: transit
-      """
-    When the following request is received:
-      """
-      POST /pots/ HTTP/1.1
-      accept: application/yaml
-      content-type: application/yaml
-
-      foo: Hello
-      bar: 1.5
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-      content-type: application/yaml
-
-      must have required property 'title'
-      """
-
-  Scenario: Query limit out of range
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?limit=1001 HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-      content-type: text/plain
-
-      Query limit must be between 1 and 1000 inclusive.
-      """
-
-  Scenario: Closed query criteria
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /hot:
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: temerature>60
-      """
-    When the following request is received:
-      """
-      GET /pots/hot/?criteria=volume>500 HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-      content-type: text/plain
-
-      Query criteria is closed.
-      """
-
-  Scenario: Additional query parameters
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET:
-            endpoint: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?foo=bar HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-      content-type: text/plain
-
-      Query must NOT have additional properties
-      """
-
-  Scenario: Malformed authorization header
-    Given the annotation:
-      """yaml
-      /:
-        GET: {}
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      authorization: Basic
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      401 Unauthorized
-
-      Malformed authorization header.
-      """
-
-  Scenario Outline: Exception is thrown (debug: <debug>)
-    Given the annotation:
-      """yaml
-      debug: <debug>
-      /:
-        GET:
-          anonymous: true
-          dev:throw: Broken!
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      500 Internal Server Error
-      <response>
-      """
-    Examples:
-      | debug | response          |
-      | false | content-length: 0 |
-      | true  | Error: Broken!    |
-
-  Scenario: Not acceptable request
-    Given the annotation:
-      """yaml
-      /:
-        GET:
-          anonymous: true
-          dev:stub: hello
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      accept: image/jpeg
-      """
-    Then the following reply is sent:
-      """
-      406 Not Acceptable
-      """