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

Adapting style to the capabilities of gherkin-lint.

Browse Source
This commit is contained in:
Roberto Abdelkader Martínez Pérez
2019-08-20 08:22:48 +02:00
parent e4771de5ed
commit 5352322ad5
8 changed files with 55 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec/test/.gherkin-lintrc
+3 -3
View File
@@ -12,8 +12,8 @@
"Scenario": 2, "Scenario": 2,
"Background": 2, "Background": 2,
"given": 4, "given": 4,
"when": 6, "when": 4,
"then": 6, "then": 4,
"and": 6, "and": 6,
"but": 6, "but": 6,
"example": 2, "example": 2,
@@ -24,7 +24,7 @@
"new-line-at-eof": ["on", "yes"], "new-line-at-eof": ["on", "yes"],
"no-multiple-empty-lines": "on", "no-multiple-empty-lines": "on",
"no-scenario-outlines-without-examples": "on", "no-scenario-outlines-without-examples": "on",
"name-length": ["on", {"Feature": 50}], "name-length": ["on", {"Feature": 80}],
"no-restricted-tags": ["on", {"tags": ["@watch", "@wip"]}], "no-restricted-tags": ["on", {"tags": ["@watch", "@wip"]}],
"use-and": "on", "use-and": "on",
"no-duplicate-tags": "on", "no-duplicate-tags": "on",
spec/test/features/control/append/error_unprocessable.feature
+12 -14
View File
@@ -9,10 +9,10 @@ Feature: Kapow! server reject responses with semantic errors.
missing fields. missing fields.
Given I have a running Kapow! server Given I have a running Kapow! server
When I append the route: When I append the route:
| entrypoint | command | | entrypoint | command |
| /bin/sh -c | ls -la / \| response /body | | /bin/sh -c | ls -la / \| response /body |
Then I get unprocessable entity as response code Then I get unprocessable entity as response code
And I get "Missing Mandatory Field" as response phrase And I get "Missing Mandatory Field" as response phrase
And I get the following entity as response body: And I get the following entity as response body:
| missing_mandatory_fields | | missing_mandatory_fields |
@@ -23,10 +23,10 @@ Feature: Kapow! server reject responses with semantic errors.
field url_pattern the server responds with an error. field url_pattern the server responds with an error.
Given I have a running Kapow! server Given I have a running Kapow! server
When I append the route: When I append the route:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | +123-- | /bin/sh -c | ls -la / \| response /body | | GET | +123-- | /bin/sh -c | ls -la / \| response /body |
Then I get unprocessable entity as response code Then I get unprocessable entity as response code
And I get "Invalid Route Spec" as response phrase And I get "Invalid Route Spec" as response phrase
And I get an empty response body And I get an empty response body
@@ -35,11 +35,9 @@ Feature: Kapow! server reject responses with semantic errors.
field method the server responds with an error. field method the server responds with an error.
Given I have a running Kapow! server Given I have a running Kapow! server
When I append the route: When I append the route:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| AVECES | +123-- | /bin/sh -c | ls -la / \| response /body | | AVECES | +123-- | /bin/sh -c | ls -la / \| response /body |
Then I get unprocessable entity as response code Then I get unprocessable entity as response code
And I get "Invalid Data Type" as response phrase And I get "Invalid Data Type" as response phrase
And I get an empty response body And I get an empty response body
...
spec/test/features/control/append/success.feature
+8 -8
View File
@@ -8,10 +8,10 @@ Feature: Append new routes in Kapow! server.
will be at index 0. will be at index 0.
Given I have a just started Kapow! server Given I have a just started Kapow! server
When I append the route: When I append the route:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | | GET | /listRootDir | /bin/sh -c | ls -la / \| response /body |
Then I get created as response code Then I get created as response code
And I get "Created" as response phrase And I get "Created" as response phrase
And I get the following entity as response body: And I get the following entity as response body:
| method | url_pattern | entrypoint | command | index | id | | method | url_pattern | entrypoint | command | index | id |
@@ -25,10 +25,10 @@ Feature: Append new routes in Kapow! server.
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | | GET | /listRootDir | /bin/sh -c | ls -la / \| response /body |
| GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
When I append the route: When I append the route:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /listEtcDir | /bin/sh -c | ls -la /etc \| response /body | | GET | /listEtcDir | /bin/sh -c | ls -la /etc \| response /body |
Then I get created as response code Then I get created as response code
And I get "Created" as response phrase And I get "Created" as response phrase
And I get the following entity as response body: And I get the following entity as response body:
| method | url_pattern | entrypoint | command | index | id | | method | url_pattern | entrypoint | command | index | id |
spec/test/features/control/delete/error_notfound.feature
+2 -2
View File
@@ -7,7 +7,7 @@ Feature: Fail to delete a route in Kapow! server.
will trigger a not found error. will trigger a not found error.
Given I have a just started Kapow! server Given I have a just started Kapow! server
When I delete the route with id "xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx" When I delete the route with id "xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx"
Then I get not found as response code Then I get not found as response code
And I get "Not Found" as response phrase And I get "Not Found" as response phrase
And I get an empty response body And I get an empty response body
spec/test/features/control/delete/success.feature
+3 -3
View File
@@ -6,8 +6,8 @@ Feature: Delete routes in Kapow! server.
Routes are removed from the sever by specifying their id. Routes are removed from the sever by specifying their id.
Given I have a running Kapow! server Given I have a running Kapow! server
And It has a route with id "xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx" And It has a route with id "xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx"
When I delete the route with id "xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx" When I delete the route with id "xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx"
Then I get ok as response code Then I get ok as response code
And I get "OK" as response phrase And I get "OK" as response phrase
And I get an empty response body And I get an empty response body
spec/test/features/control/insert/error_unprocessable.feature
+12 -14
View File
@@ -8,10 +8,10 @@ Feature: Kapow! server reject insert responses with semantic errors.
missing fields. missing fields.
Given I have a running Kapow! server Given I have a running Kapow! server
When I insert the route: When I insert the route:
| entrypoint | command | | entrypoint | command |
| /bin/sh -c | ls -la / \| response /body | | /bin/sh -c | ls -la / \| response /body |
Then I get unprocessable entity as response code Then I get unprocessable entity as response code
And I get "Missing Mandatory Field" as response phrase And I get "Missing Mandatory Field" as response phrase
And I get the following entity as response body: And I get the following entity as response body:
| missing_mandatory_fields | | missing_mandatory_fields |
@@ -22,10 +22,10 @@ Feature: Kapow! server reject insert responses with semantic errors.
url_pattern field the server responds with an error. url_pattern field the server responds with an error.
Given I have a running Kapow! server Given I have a running Kapow! server
When I insert the route: When I insert the route:
| method | url_pattern | entrypoint | command | index | | method | url_pattern | entrypoint | command | index |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 | | GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 |
Then I get unprocessable entity as response code Then I get unprocessable entity as response code
And I get "Invalid Route Spec" as response phrase And I get "Invalid Route Spec" as response phrase
And I get an empty response body And I get an empty response body
@@ -34,11 +34,9 @@ Feature: Kapow! server reject insert responses with semantic errors.
method field the server responds with an error. method field the server responds with an error.
Given I have a running Kapow! server Given I have a running Kapow! server
When I insert the route: When I insert the route:
| method | url_pattern | entrypoint | command | index | | method | url_pattern | entrypoint | command | index |
| AVECES | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 | | AVECES | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 |
Then I get unprocessable entity as response code Then I get unprocessable entity as response code
And I get "Invalid Data Type" as response phrase And I get "Invalid Data Type" as response phrase
And I get an empty response body And I get an empty response body
...
spec/test/features/control/insert/success.feature
+8 -8
View File
@@ -13,10 +13,10 @@ Feature: Insert new routes in Kapow! server.
A route can be inserted at the begining of the list A route can be inserted at the begining of the list
by specifying an index 0 in the request. by specifying an index 0 in the request.
When I insert the route: When I insert the route:
| method | url_pattern | entrypoint | command | index | | method | url_pattern | entrypoint | command | index |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 | | GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 |
Then I get ok as response code Then I get ok as response code
And I get "OK" as response phrase And I get "OK" as response phrase
And I get the following entity as response body: And I get the following entity as response body:
| method | url_pattern | entrypoint | command | index | id | | method | url_pattern | entrypoint | command | index | id |
@@ -27,10 +27,10 @@ Feature: Insert new routes in Kapow! server.
by specifying an index less or equal to the last by specifying an index less or equal to the last
index in the request. index in the request.
When I insert the route: When I insert the route:
| method | url_pattern | entrypoint | command | index | | method | url_pattern | entrypoint | command | index |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 1 | | GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 1 |
Then I get ok as response code Then I get ok as response code
And I get "OK" as response phrase And I get "OK" as response phrase
And I get the following entity as response body: And I get the following entity as response body:
| method | url_pattern | entrypoint | command | index | id | | method | url_pattern | entrypoint | command | index | id |
spec/test/features/control/list/success.feature
+7 -7
View File
@@ -9,8 +9,8 @@ Feature: Listing routes in a Kapow! server
will show an empty list of routes. will show an empty list of routes.
Given I have a just started Kapow! server Given I have a just started Kapow! server
When I request a routes listing When I request a routes listing
Then I get an empty list Then I get an empty list
Scenario: Listing routes on a server with routes loaded. Scenario: Listing routes on a server with routes loaded.
After some route creation/insertion operations the server After some route creation/insertion operations the server
@@ -20,8 +20,8 @@ Feature: Listing routes in a Kapow! server
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | | GET | /listRootDir | /bin/sh -c | ls -la / \| response /body |
| GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
When I request a routes listing When I request a routes listing
Then I get a list with the following elements: Then I get a list with the following elements:
| method | url_pattern | entrypoint | command | index | id | | method | url_pattern | entrypoint | command | index | id |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 | * | | GET | /listRootDir | /bin/sh -c | ls -la / \| response /body | 0 | * |
| GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | 1 | * | | GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | 1 | * |