Added features for data/handler/error_invalidresource, data/handler/error_notfound and data/handler/success

This commit is contained in:
Héctor Hurtado
2019-08-27 09:44:37 +02:00
parent 227ad8e4b7
commit 6bb8f974fb
3 changed files with 65 additions and 0 deletions
@@ -0,0 +1,28 @@
Feature: Fail to retrieve resources from nonexistent handler in Kapow! server.
If trying to access a nonexistent handler then the
server responds with a noptfound error.
@wip
Scenario: Try to get a valid resource from a nonexistent handler.
A request for retrieving a resource from a nonexistent
handler will trigger a not found error.
Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body |
When I the get the resource "request/path" for the handler with id HANDLER_ID_XXXXXXXXXX
Then I get 404 as response code
And I get "Not Found" as response reason phrase
@wip
Scenario: Fail to get an invalid resource from a nonexistent handler.
A request for retrieving a resource from a nonexistent
handler will trigger a not found error even if the
resource is invalid.
Given I have a Kapow! server with the following routes:
| method | url_pattern | entrypoint | command |
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body |
When I the get the resource "invented/path" for the handler with id HANDLER_ID_XXXXXXXXXX
Then I get 404 as response code
And I get "Not Found" as response reason phrase