Revert "Closes: #66"

This reverts commit c3be29255a.

Co-authored-by: Roberto Abdelkader Martínez Pérez <robertomartinezp@gmail.com>
This commit is contained in:
pancho horrillo
2019-11-11 17:17:25 +01:00
parent 19f7cb0171
commit 9eb186bd0f
17 changed files with 27 additions and 27 deletions
@@ -28,4 +28,4 @@ Feature: Kapow! server reject append requests with malformed JSON bodies.
Hi! I am an invalid JSON document.
"""
Then I get 400 as response code
# And I get "Malformed JSON" as response reason phrase
And I get "Malformed JSON" as response reason phrase
@@ -31,7 +31,7 @@ Feature: Kapow! server rejects requests with semantic errors.
}
"""
Then I get 422 as response code
# And I get "Invalid Route" as response reason phrase
And I get "Invalid Route" as response reason phrase
Scenario: Error because bad route format.
If a request contains an invalid expression in the
@@ -48,4 +48,4 @@ Feature: Kapow! server rejects requests with semantic errors.
}
"""
Then I get 422 as response code
# And I get "Invalid Route" as response reason phrase
And I get "Invalid Route" as response reason phrase
@@ -33,7 +33,7 @@ Feature: Append new routes in Kapow! server.
}
"""
Then I get 201 as response code
# And I get "Created" as response reason phrase
And I get "Created" as response reason phrase
And I get the following response body:
"""
{
@@ -64,7 +64,7 @@ Feature: Append new routes in Kapow! server.
}
"""
Then I get 201 as response code
# And I get "Created" as response reason phrase
And I get "Created" as response reason phrase
And I get the following response body:
"""
{
@@ -24,4 +24,4 @@ Feature: Fail to delete a route in Kapow! server.
Given I have a just started Kapow! server
When I delete the route with id "xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx"
Then I get 404 as response code
# And I get "Not Found" as response reason phrase
And I get "Not Found" as response reason phrase
@@ -26,4 +26,4 @@ Feature: Delete routes in Kapow! server.
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| kapow set /response/body |
When I delete the first route
Then I get 204 as response code
# And I get "No Content" as response reason phrase
And I get "No Content" as response reason phrase
@@ -24,4 +24,4 @@ Feature: Fail to retrieve route details in Kapow! server.
Given I have a just started Kapow! server
When I get the route with id "xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx"
Then I get 404 as response code
# And I get "Not Found" as response reason phrase
And I get "Not Found" as response reason phrase
@@ -26,7 +26,7 @@ Feature: Retrieve route details in Kapow! server.
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| kapow set /response/body |
When I get the first route
Then I get 200 as response code
# And I get "OK" as response reason phrase
And I get "OK" as response reason phrase
And I get the following response body:
"""
{
@@ -37,4 +37,4 @@ Feature: Kapow! server rejects insertion requests with malformed JSON bodies.
}
"""
Then I get 400 as response code
# And I get "Malformed JSON" as response reason phrase
And I get "Malformed JSON" as response reason phrase
@@ -31,7 +31,7 @@ Feature: Kapow! server rejects insertion requests with semantic errors.
}
"""
Then I get 422 as response code
# And I get "Invalid Route" as response reason phrase
And I get "Invalid Route" as response reason phrase
Scenario: Error because wrong route specification.
If a request contains an invalid expression in the
@@ -49,7 +49,7 @@ Feature: Kapow! server rejects insertion requests with semantic errors.
}
"""
Then I get 422 as response code
# And I get "Invalid Route" as response reason phrase
And I get "Invalid Route" as response reason phrase
Scenario: Error because negative index specified.
If a request contains a negative number in the
@@ -67,4 +67,4 @@ Feature: Kapow! server rejects insertion requests with semantic errors.
}
"""
Then I get 422 as response code
# And I get "Invalid Route" as response reason phrase
And I get "Invalid Route" as response reason phrase
@@ -40,7 +40,7 @@ Feature: Insert new routes in Kapow! server.
}
"""
Then I get 201 as response code
# And I get "Created" as response reason phrase
And I get "Created" as response reason phrase
And I get the following response body:
"""
{
@@ -69,7 +69,7 @@ Feature: Insert new routes in Kapow! server.
}
"""
Then I get 201 as response code
# And I get "Created" as response reason phrase
And I get "Created" as response reason phrase
And I get the following response body:
"""
{
@@ -25,7 +25,7 @@ Feature: Listing routes in a Kapow! server.
Given I have a just started Kapow! server
When I request a routes listing
Then I get 200 as response code
# And I get "OK" as response reason phrase
And I get "OK" as response reason phrase
And I get the following response body:
"""
[]
@@ -41,7 +41,7 @@ Feature: Listing routes in a Kapow! server.
| GET | /qux/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| kapow set /response/body |
When I request a routes listing
Then I get 200 as response code
# And I get "OK" as response reason phrase
And I get "OK" as response reason phrase
And I get the following response body:
"""
[
@@ -25,14 +25,14 @@ Feature: Fail to retrieve resources from nonexistent handler in Kapow! server.
Given I have a running Kapow! server
When I get the resource "/request/path" for the handler with id "XXXXXXXXXX"
Then I get 404 as response code
# And I get "Handler ID Not Found" as response reason phrase
And I get "Handler ID Not Found" as response reason phrase
Scenario: Try to get an invalid resource from a nonexistent handler.
A request to retrieve an invalid resource from a nonexistent
handler will trigger an invalid resource path error
handler will trigger a handler ID not found error
even if the resource is invalid.
Given I have a running Kapow! server
When I get the resource "/invalid/path" for the handler with id "XXXXXXXXXX"
Then I get 400 as response code
# And I get "Invalid Resource Path" as response reason phrase
Then I get 404 as response code
And I get "Handler ID Not Found" as response reason phrase
@@ -27,4 +27,4 @@ Feature: Fail to retrieve an invalid resource for a handler in Kapow! server.
When I send a request to the testing route "/foo"
And I get the resource "/invented/path"
Then I get 400 as response code
# And I get "Invalid Resource Path" as response reason phrase
And I get "Invalid Resource Path" as response reason phrase
@@ -28,4 +28,4 @@ Feature: Fail to retrieve nonexistent resource items in Kapow! server.
When I send a request to the testing route "/foo"
And I get the resource "/request/params/meloinvento"
Then I get 404 as response code
# And I get "Resource Item Not Found" as response reason phrase
And I get "Resource Item Not Found" as response reason phrase
@@ -28,7 +28,7 @@ Feature: Retrieve a resource from a handler in Kapow! server.
When I send a request to the testing route "/foo"
And I get the resource "/request/path"
Then I get 200 as response code
# And I get "OK" as response reason phrase
And I get "OK" as response reason phrase
And I get the following response raw body:
"""
/foo
@@ -44,7 +44,7 @@ Feature: Retrieve a resource from a handler in Kapow! server.
When I send a request to the testing route "/foo?name=bar"
And I get the resource "/request/params/name"
Then I get 200 as response code
# And I get "OK" as response reason phrase
And I get "OK" as response reason phrase
And I get the following response raw body:
"""
bar
@@ -34,7 +34,7 @@ Feature: Retrieve request resources from a handler in Kapow! server.
| body | | bodyVal1 |
And I get the resource "<resourcePath>"
Then I get 200 as response code
# And I get "OK" as response reason phrase
And I get "OK" as response reason phrase
And I get the following response raw body:
"""
<value>
@@ -41,7 +41,7 @@ Feature: Setting values for handler response resources in Kapow! server.
And I set the resource "<resourcePath>" with value "<value>"
And I release the testing request
Then I get 200 as response code
# And I get "OK" as response reason phrase
And I get "OK" as response reason phrase
And I get the value "<value>" for the response "<fieldType>" named "<elementName>" in the testing request
Examples: