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

Fix tables alignment

Browse Source
This commit is contained in:
Roberto Abdelkader Martínez Pérez
2019-09-03 09:21:20 +02:00
parent 99ab41d2cb
commit 8e259b42de
13 changed files with 28 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec/test/features/control/append/success.feature
+2 -2
View File
@@ -36,8 +36,8 @@ Feature: Append new routes in Kapow! server.
at the end of the list. at the end of the list.
Given I have a Kapow! server with the following routes: Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /foo | /bin/sh -c | ls -la / \| response /body | | GET | /foo | /bin/sh -c | ls -la / \| response /body |
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
When I append the route: When I append the route:
""" """
spec/test/features/control/delete/list_order.feature
+4 -4
View File
@@ -4,10 +4,10 @@ Feature: Consistent route order after a route deletion in Kapow! server.
Background: Background:
Given I have a Kapow! server with the following routes: Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /foo | /bin/sh -c | ls -la / \| response /body | | GET | /foo | /bin/sh -c | ls -la / \| response /body |
| GET | /bar | /bin/sh -c | ls -la /var \| response /body | | GET | /bar | /bin/sh -c | ls -la /var \| response /body |
| GET | /baz | /bin/sh -c | ls -la /etc \| response /body | | GET | /baz | /bin/sh -c | ls -la /etc \| response /body |
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
Scenario: Removing the first route. Scenario: Removing the first route.
spec/test/features/control/delete/success.feature
+2 -2
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 Kapow! server with the following routes: Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /foo | /bin/sh -c | ls -la / \| response /body | | GET | /foo | /bin/sh -c | ls -la / \| response /body |
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
When I delete the first route When I delete the first route
Then I get 204 as response code Then I get 204 as response code
spec/test/features/control/get/success.feature
+2 -2
View File
@@ -6,8 +6,8 @@ Feature: Retrieve route details in Kapow! server.
Get route details by id. Get route details by id.
Given I have a Kapow! server with the following routes: Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /foo | /bin/sh -c | ls -la / \| response /body | | GET | /foo | /bin/sh -c | ls -la / \| response /body |
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
When I get the first route When I get the first route
Then I get 200 as response code Then I get 200 as response code
spec/test/features/control/insert/list_order.feature
+2 -2
View File
@@ -4,8 +4,8 @@ Feature: Consistent route ordering after inserting a route in a Kapow! server.
Background: Background:
Given I have a Kapow! server with the following routes: Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /foo | /bin/sh -c | ls -la / \| response /body | | GET | /foo | /bin/sh -c | ls -la / \| response /body |
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
Scenario: Inserting before the first route. Scenario: Inserting before the first route.
spec/test/features/control/insert/success.feature
+2 -2
View File
@@ -5,8 +5,8 @@ Feature: Insert new routes in Kapow! server.
Background: Background:
Given I have a Kapow! server with the following routes: Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /foo | /bin/sh -c | ls -la / \| response /body | | GET | /foo | /bin/sh -c | ls -la / \| response /body |
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
Scenario: Insert a route at the beginning. Scenario: Insert a route at the beginning.
spec/test/features/control/list/success.feature
+2 -2
View File
@@ -21,8 +21,8 @@ Feature: Listing routes in a Kapow! server.
must return an ordered list of routes stored. must return an ordered list of routes stored.
Given I have a Kapow! server with the following routes: Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command | | method | url_pattern | entrypoint | command |
| GET | /foo | /bin/sh -c | ls -la / \| response /body | | GET | /foo | /bin/sh -c | ls -la / \| response /body |
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body | | GET | /qux/{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 200 as response code Then I get 200 as response code
spec/test/features/data/handler/error_invalidresource.feature
+2 -2
View File
@@ -7,8 +7,8 @@ Feature: Fail to retrieve an invalid resource for a handler in Kapow! server.
from a handler will trigger a invalid resource error. from a handler will trigger a invalid resource error.
Given I have a Kapow! server with the following testing routes: Given I have a Kapow! server with the following testing routes:
| method | url_pattern | | method | url_pattern |
| GET | /foo | | GET | /foo |
When I send a request to the testing route "/foo" When I send a request to the testing route "/foo"
And I get the resource "/invented/path" And I get the resource "/invented/path"
Then I get 400 as response code Then I get 400 as response code
spec/test/features/data/handler/error_itemnotfound.feature
+2 -2
View File
@@ -8,8 +8,8 @@ Feature: Fail to retrieve nonexistent resource items in Kapow! server.
error. error.
Given I have a Kapow! server with the following testing routes: Given I have a Kapow! server with the following testing routes:
| method | url_pattern | | method | url_pattern |
| GET | /foo | | GET | /foo |
When I send a request to the testing route "/foo" When I send a request to the testing route "/foo"
And I get the resource "/request/params/meloinvento" And I get the resource "/request/params/meloinvento"
Then I get 204 as response code Then I get 204 as response code
spec/test/features/data/handler/error_notfound.feature
+1 -1
View File
@@ -1,6 +1,6 @@
Feature: Fail to retrieve resources from nonexistent handler in Kapow! server. Feature: Fail to retrieve resources from nonexistent handler in Kapow! server.
If trying to access a nonexistent handler then the If trying to access a nonexistent handler then the
server responds with a noptfound error. server responds with a not found error.
Scenario: Try to get a valid resource path from a nonexistent handler. Scenario: Try to get a valid resource path from a nonexistent handler.
A request to retrieve a resource from a A request to retrieve a resource from a
spec/test/features/data/handler/success.feature
+4 -4
View File
@@ -8,8 +8,8 @@ Feature: Retrieve a resource from a handler in Kapow! server.
request through the handler id. request through the handler id.
Given I have a Kapow! server with the following testing routes: Given I have a Kapow! server with the following testing routes:
| method | url_pattern | | method | url_pattern |
| GET | /foo | | GET | /foo |
When I send a request to the testing route "/foo" When I send a request to the testing route "/foo"
And I get the resource "/request/path" And I get the resource "/request/path"
Then I get 200 as response code Then I get 200 as response code
@@ -24,8 +24,8 @@ Feature: Retrieve a resource from a handler in Kapow! server.
the current request through the handler id. the current request through the handler id.
Given I have a Kapow! server with the following testing routes: Given I have a Kapow! server with the following testing routes:
| method | url_pattern | | method | url_pattern |
| GET | /foo | | GET | /foo |
When I send a request to the testing route "/foo" When I send a request to the testing route "/foo"
And I get the resource "/request/headers/Host" And I get the resource "/request/headers/Host"
Then I get 200 as response code Then I get 200 as response code
spec/test/features/data/request/success.feature
+1 -1
View File
@@ -28,7 +28,7 @@ Feature: Retrieve request resources from a handler in Kapow! server.
Examples: Examples:
| resourcePath | value | | resourcePath | value |
| /request/method | GET | | /request/method | GET |
| /request/path | /foo/matchVal1 | | /request/path | /foo/matchVal1 |
| /request/host | localhost:8080 | | /request/host | localhost:8080 |
| /request/matches/path | matchVal1 | | /request/matches/path | matchVal1 |
| /request/params/par1 | paramVal1 | | /request/params/par1 | paramVal1 |
spec/test/features/data/response/success.feature
+2 -2
View File
@@ -9,7 +9,7 @@ Feature: Setting values for handler response resources in Kapow! server.
Given I have a Kapow! server with the following testing routes: Given I have a Kapow! server with the following testing routes:
| method | url_pattern | | method | url_pattern |
| GET | /foo | | GET | /foo |
When I send a request to the testing route "/foo" When I send a request to the testing route "/foo"
And I set the resource "/response/status" with value "418" And I set the resource "/response/status" with value "418"
And I release the testing request And I release the testing request
@@ -21,7 +21,7 @@ Feature: Setting values for handler response resources in Kapow! server.
Given I have a Kapow! server with the following testing routes: Given I have a Kapow! server with the following testing routes:
| method | url_pattern | | method | url_pattern |
| GET | /foo | | GET | /foo |
When I send a request to the testing route "/foo" When I send a request to the testing route "/foo"
And I set the resource "<resourcePath>" with value "<value>" And I set the resource "<resourcePath>" with value "<value>"
And I release the testing request And I release the testing request