Dark-Alex-17/kapow
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added append/success and append/error_unprocessable features

Browse Source
This commit is contained in:
Héctor Hurtado
2019-08-17 10:26:40 +02:00
parent 12a5d8761b
commit baf8217a14
2 changed files with 80 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec/test/features/control/append/error_unprocessable.feature
+45
View File
@@ -0,0 +1,45 @@
Feature: Kapow! server reject responses with semantic errors.
Kapow! server will reject to create routes when
it receives a valid json document but not conforming
with the specification.
Scenario: Error by lack of mandatory fields.
If a request lacks of any of the mandatory fields
the server responds with an error indicating the
missing fields.
Given I have a running Kapow! server
When I append the route:
| entrypoint | command |
| /bin/sh -c | ls -la / \| response /body |
Then I get unprocessable entity as response code
And I get "Missing Mandatory Field" as response phrase
And I get the following entity as response body:
| missing_mandatory_fields |
| "url_pattern", "method" |
Scenario: Error by wrong route spec.
If a request contains an invalid expression in the
field url_pattern the server responds with an error.
Given I have a running Kapow! server
When I append the route:
| method | url_pattern | entrypoint | command |
| GET | +123-- | /bin/sh -c | ls -la / \| response /body |
Then I get unprocessable entity as response code
And I get "Invalid Route Spec" as response phrase
And I get an empty response body
Scenario: Error by wrong method value.
If a request contains an invalid value in the
field method the server responds with an error.
Given I have a running Kapow! server
When I append the route:
| method | url_pattern | entrypoint | command |
| AVECES | +123-- | /bin/sh -c | ls -la / \| response /body |
Then I get unprocessable entity as response code
And I get "Invalid Data Type" as response phrase
And I get an empty response body
...
spec/test/features/control/append/success.feature
+35
View File
@@ -0,0 +1,35 @@
Feature: Append new routes in Kapow! server.
Append routes allow users to configure the server. New
routes are added to the list of existing routes.
Scenario: Append the first route.
A fresh server, just started or with all routes removed,
will create a new list of routes. The newly created rule
will be at index 0.
Given I have a just started Kapow! server
When I append the route:
| method | url_pattern | entrypoint | command |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body |
Then I get created as response code
And I get "Created" as response phrase
And I get the following entity as response body:
| method | url_pattern | entrypoint | command | index | id |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 | * |
Scenario: Append another route.
Appending routes on a non empty list will create new routes
at the end of the list.
Given I have a Kapow! server whith the following routes:
| method | url_pattern | entrypoint | command |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body |
| GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
When I append the route:
| method | url_pattern | entrypoint | command |
| GET | /listEtcDir | /bin/sh -c | ls -la /etc \| response /body |
Then I get created as response code
And I get "Created" as response phrase
And I get the following entity as response body:
| method | url_pattern | entrypoint | command | index | id |
| GET | /listEtcDir | /bin/sh -c | ls -la /etc \| response /body | 2 | * |