Added @wip tag to features and fix name length issues
This commit is contained in:
@@ -1,8 +1,8 @@
|
|||||||
|
@wip
|
||||||
Feature: Fail to retrieve an invalid resource for a handler in Kapow! server.
|
Feature: Fail to retrieve an invalid resource for a handler in Kapow! server.
|
||||||
If trying to access an invalid resource for a handler
|
If trying to access an invalid resource for a handler
|
||||||
then the server responds with an error.
|
then the server responds with an error.
|
||||||
|
|
||||||
@wip
|
|
||||||
Scenario: Try to get invented/path from a existent handler.
|
Scenario: Try to get invented/path from a existent handler.
|
||||||
A request for retrieving an invalid resource for an
|
A request for retrieving an invalid resource for an
|
||||||
existent handler will trigger a invalid resource error.
|
existent handler will trigger a invalid resource error.
|
||||||
|
|||||||
@@ -1,8 +1,8 @@
|
|||||||
|
@wip
|
||||||
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 noptfound error.
|
||||||
|
|
||||||
@wip
|
|
||||||
Scenario: Try to get a valid resource from a nonexistent handler.
|
Scenario: Try to get a valid resource from a nonexistent handler.
|
||||||
A request for retrieving a resource from a nonexistent
|
A request for retrieving a resource from a nonexistent
|
||||||
handler will trigger a not found error.
|
handler will trigger a not found error.
|
||||||
@@ -10,11 +10,10 @@ Feature: Fail to retrieve resources from nonexistent handler in Kapow! server.
|
|||||||
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 | /listRootDir | /bin/sh -c | ls -la / \| response /body |
|
| 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
|
When I get the resource "request/path" for the handler with id XXXXXXXXXX
|
||||||
Then I get 404 as response code
|
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
|
||||||
|
|
||||||
@wip
|
|
||||||
Scenario: Fail to get an invalid resource from a nonexistent handler.
|
Scenario: Fail to get an invalid resource from a nonexistent handler.
|
||||||
A request for retrieving a resource from a nonexistent
|
A request for retrieving a resource from a nonexistent
|
||||||
handler will trigger a not found error even if the
|
handler will trigger a not found error even if the
|
||||||
@@ -23,6 +22,6 @@ Feature: Fail to retrieve resources from nonexistent handler in Kapow! server.
|
|||||||
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 | /listRootDir | /bin/sh -c | ls -la / \| response /body |
|
| 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
|
When I get the resource "invented/path" for the handler with id XXXXXXXXXX
|
||||||
Then I get 404 as response code
|
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
|
||||||
|
|||||||
@@ -1,9 +1,9 @@
|
|||||||
|
@wip
|
||||||
Feature: Retrieve a resource from a handler in Kapow! server.
|
Feature: Retrieve a resource from a handler in Kapow! server.
|
||||||
Users can retrieve request handler resources
|
Users can retrieve request handler resources
|
||||||
from the server by specifying the handler id
|
from the server by specifying the handler id
|
||||||
and the resource path.
|
and the resource path.
|
||||||
|
|
||||||
@wip
|
|
||||||
Scenario: Retrieve a resource for the current request.
|
Scenario: Retrieve a resource for the current request.
|
||||||
Get the "request/path" resource for the current
|
Get the "request/path" resource for the current
|
||||||
request through the handler id.
|
request through the handler id.
|
||||||
|
|||||||
Reference in New Issue
Block a user