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

Review feature and scenario definitions. Removing unnecesary and redundant steps.

Browse Source
This commit is contained in:
Roberto Abdelkader Martínez Pérez
2019-08-23 12:46:10 +02:00
parent 8752f419b5
commit 991ae618bb
13 changed files with 62 additions and 150 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec/test/features/control/list/success.feature
+10 -7
View File
@@ -1,30 +1,33 @@
Feature: Listing routes in a Kapow! server
Listing routes allow users to know what commands are
Listing routes allows users to know what URLs 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,
Scenario: List routes on a fresh started server
A 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 reason phrase
And I get an empty list
And I get the following response body:
"""
[]
"""
Scenario: Listing routes on a server with routes loaded.
Scenario: List 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:
Given I have a Kapow! server with 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 reason phrase
And I get a list with the following elements:
And I get the following response body:
"""
[
{