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

package/features/discovery.ui.feature

@@ -1,213 +0,0 @@
-Feature: The discovery page
-
-  The page that reads the tree, served from the same origin the tree is. The scenarios are
-  about the server rather than the page: it is pointed at a fixture, so none of them needs
-  a UI build.
-
-  Scenario: The page
-    When the following request is received:
-      """
-      GET /.discovery/ HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      cache-control: no-cache
-      content-type: text/html; charset=utf-8
-
-      the page
-      """
-
-  Scenario: The bare path is the directory it is
-    When the following request is received:
-      """
-      GET /.discovery HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      302 Moved Temporarily
-      location: /.discovery/
-      """
-
-  Scenario: An asset carries the build it was named for
-    When the following request is received:
-      """
-      GET /.discovery/_app/immutable/asset.js HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      cache-control: public, max-age=31536000, immutable
-      content-type: text/javascript; charset=utf-8
-      """
-
-  Scenario: Anything that could be a route is the page
-    The client router knows what routes there are, and this server does not.
-
-    When the following request is received:
-      """
-      GET /.discovery/pots/:id HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: text/html; charset=utf-8
-
-      the page
-      """
-
-  Scenario: An asset that is not there is not there
-    When the following request is received:
-      """
-      GET /.discovery/_app/immutable/gone.js HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      """
-
-  Scenario: A path that merely starts like this one is not this one
-    When the following request is received:
-      """
-      GET /.discoveryable/ HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      """
-
-  Scenario: A path that climbs out of the page is refused
-    An encoded separator is what reaches here: a dot segment is collapsed while the URL is
-    parsed, and `%2f` survives that to decode into one afterwards.
-
-    When the following request is received:
-      """
-      GET /.discovery/%2f%2e%2e%2f%2e%2e%2fpackage.json HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-      """
-
-  Scenario: The page is served before a credential is read
-    A page is public, and one served after `auth` would refuse the client holding a stale
-    token — who is the client most likely to have opened it.
-
-    Given the annotation:
-      """yaml
-      /:
-        GET:
-          dev:stub: hello
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      401 Unauthorized
-      """
-    When the following request is received:
-      """
-      GET /.discovery/ HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      the page
-      """
-
-  Scenario: What else the path answers
-    When the following request is received:
-      """
-      POST /.discovery/ HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      405 Method Not Allowed
-      allow: GET, HEAD, OPTIONS
-      """
-
-  Scenario: A browser at the trunk is sent to the page
-    An application serves what it declares, and `/` is usually not one of those. Someone
-    who typed the address into a browser is looking for something to look at, and the page
-    is the only thing here that is one.
-
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-      """
-    Then the following reply is sent:
-      """
-      302 Moved Temporarily
-      location: /.discovery/
-      """
-
-  Scenario: A client that asks for nothing in particular is sent there too
-    Several unfurlers ask for anything at all, and a link to an application would otherwise
-    show nothing.
-
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      accept: */*
-      """
-    Then the following reply is sent:
-      """
-      302 Moved Temporarily
-      location: /.discovery/
-      """
-
-  Scenario: A client that asked for something else gets what it asked for
-    An `accept` naming what the gateway answers with is a client that wants the resource,
-    not the page.
-
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      accept: application/json
-      """
-    Then the following reply is sent:
-      """
-      405 Method Not Allowed
-      """
-
-  Scenario: What the application serves there answers instead
-    A route declared at the trunk is what answers it, browser or not.
-
-    Given the annotation:
-      """yaml
-      /:
-        anonymous: true
-        GET:
-          dev:stub: hello
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-    And the reply does not contain:
-      """
-      /.discovery/
-      """

package/features/dynamic.feature

@@ -1,192 +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
-      version: 1
-      exposition:
-        /:
-          io:output: true
-          isolated: true
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/ HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      401 Unauthorized
-      """
-    Then the `pots` is stopped
-    Then the `pots` is running with the following manifest:
-      """yaml
-      version: 2
-      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: 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
-      """
-
-  @timing
-  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
-          GET: observe
-      """
-    Then the `pots` is stopped
-    Then the `pots` is running with the following manifest:
-      """yaml
-      version: 1.1.0
-      exposition:
-        /:
-          io:output: true
-          /:id:
-            GET: observe
-          /big:
-            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
-      """
-
-  Scenario: Updating method mapping
-    Given the Gateway is running
-    And the `pots` is running with the following manifest:
-      """yaml
-      version: a
-      exposition:
-        /big:
-          io:output: true
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: volume>200 # closed
-      """
-    Then the `pots` is stopped
-    Then the `pots` is running with the following manifest:
-      """yaml
-      version: b
-      exposition:
-        /big:
-          io:output: true
-          GET:
-            endpoint: enumerate
-            query:
-              criteria: volume>200; # open
-      """
-    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
-      """

package/features/errors.feature

@@ -1,258 +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
-      host: nex.toa.io
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      404 Not Found
-
-      Route 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
-      host: nex.toa.io
-      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
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      405 Method Not Allowed
-      """
-
-  Scenario: Unsupported method
-    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:
-      """
-      501 Not Implemented
-      """
-
-  Scenario: Request body does not match input schema
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          POST: create
-      """
-    When the following request is received:
-      """
-      POST /pots/ HTTP/1.1
-      host: nex.toa.io
-      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: Criteria value the property cannot hold
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET: enumerate
-      """
-    When the following request is received:
-      """
-      GET /pots/?criteria=volume>abc HTTP/1.1
-      host: nex.toa.io
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-      content-type: text/plain
-
-      Criteria selector 'volume' takes a number, and 'abc' is not one
-      """
-
-  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
-      host: nex.toa.io
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-      content-type: text/plain
-
-      Query limit must be between 1 and 100 inclusive
-      """
-
-  Scenario: Closed query criteria
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /hot:
-          GET:
-            endpoint: enumerate
-            query:
-              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:
-      """
-      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
-      host: nex.toa.io
-      accept: text/plain
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-      content-type: text/plain
-
-      Query Property foo is not expected to be here
-      """
-
-  Scenario: Malformed authorization header
-    Given the annotation:
-      """yaml
-      /:
-        GET: {}
-      """
-    When the following request is received:
-      """
-      GET / HTTP/1.1
-      host: nex.toa.io
-      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
-      host: nex.toa.io
-      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:
-          io:output: true
-          anonymous: true
-          dev:stub: hello
-      """
-    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
-      """