48 lines
1.8 KiB
Gherkin
48 lines
1.8 KiB
Gherkin
Feature: Listing routes in a Kapow! server
|
|
Listing routes allow users to know what commands are
|
|
available on a Kapow! server. The List endpoint returns
|
|
a list of the routes the server has configured.
|
|
|
|
Scenario: Listing routes on a fresh started server
|
|
A fresh server, just started or with all routes removed,
|
|
will show an empty list of routes.
|
|
|
|
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 phrase
|
|
And I get an empty list
|
|
|
|
Scenario: Listing routes on a server with routes loaded.
|
|
After some route creation/insertion operations the server
|
|
must return an ordered list of routes stored.
|
|
|
|
Given I have a Kapow! server whith the following routes:
|
|
| method | url_pattern | entrypoint | command |
|
|
| GET | /listRootDir | /bin/sh -c | ls -la / \| response /body |
|
|
| GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
|
|
When I request a routes listing
|
|
Then I get 200 as response code
|
|
And I get "OK" as response phrase
|
|
And I get a list with the following elements:
|
|
"""
|
|
[
|
|
{
|
|
"method": "GET",
|
|
"url_pattern": "/listRootDir",
|
|
"entrypoint": "/bin/sh -c",
|
|
"command": "ls -la / | response /body",
|
|
"index": 0,
|
|
"id": "*"
|
|
},
|
|
{
|
|
"method": "GET",
|
|
"url_pattern": "/listDir/:dirname",
|
|
"entrypoint": "/bin/sh -c",
|
|
"command": "ls -la /request/params/dirname | response /body",
|
|
"index": 1,
|
|
"id": "*"
|
|
}
|
|
]
|
|
"""
|