Review feature and scenario definitions. Removing unnecesary and redundant steps.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
Feature: Fail to delete a route in Kapow! server.
|
||||
When trying to delete a route in the server, if it
|
||||
does no exists the server respons with an error.
|
||||
When trying to delete a route that not exists in the server
|
||||
the server respons with an error.
|
||||
|
||||
Scenario: Delete a non-existing route.
|
||||
A request of removing a non-existing route
|
||||
|
||||
@@ -1,25 +1,23 @@
|
||||
Feature: Routes auto-ordering after deleting in a Kapow! server.
|
||||
|
||||
Feature: Consistent route order after a route deletion in Kapow! server.
|
||||
When deleting routes the server will mantain the
|
||||
remaining routes ordered an with consecutive indexes.
|
||||
remaining routes ordered and with consecutive indexes.
|
||||
|
||||
Background:
|
||||
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 | /listVarDir | /bin/sh -c | ls -la /var \| response /body |
|
||||
| GET | /listEtcDir | /bin/sh -c | ls -la /etc \| response /body |
|
||||
| GET | /listDir/{dirname} | /bin/sh -c | ls -la /request/params/dirname \| response /body |
|
||||
|
||||
Scenario: Removing the first routes.
|
||||
|
||||
Scenario: Removing the first route.
|
||||
After removing the first route the remaining ones
|
||||
will maintain their relative order and their indexes
|
||||
will be decreased by one.
|
||||
|
||||
When I delete the first route inserted
|
||||
When I delete the first route
|
||||
And I request a routes listing
|
||||
Then I get a list with the following elements:
|
||||
Then I get the following response body:
|
||||
"""
|
||||
[
|
||||
{
|
||||
@@ -49,13 +47,13 @@ Feature: Routes auto-ordering after deleting in a Kapow! server.
|
||||
]
|
||||
"""
|
||||
|
||||
Scenario: Removing the last routes.
|
||||
Scenario: Removing the last route.
|
||||
After removing the last route the remaining ones will
|
||||
maintain their relative order and indexes.
|
||||
|
||||
When I delete the last route inserted
|
||||
When I delete the last route
|
||||
And I request a routes listing
|
||||
Then I get a list with the following elements:
|
||||
Then I get the following response body:
|
||||
"""
|
||||
[
|
||||
{
|
||||
@@ -90,9 +88,9 @@ Feature: Routes auto-ordering after deleting in a Kapow! server.
|
||||
maintain their relative order and the indexes of the
|
||||
following routes will be decreased by one.
|
||||
|
||||
When I delete the second route inserted
|
||||
When I delete the second route
|
||||
And I request a routes listing
|
||||
Then I get a list with the following elements:
|
||||
Then I get the following response body:
|
||||
"""
|
||||
[
|
||||
{
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
Feature: Delete routes in Kapow! server.
|
||||
Delete routes allow users to remove non-desired
|
||||
Deleting routes allows users to remove undesired
|
||||
routes from the server.
|
||||
|
||||
Scenario: Delete a route.
|
||||
Routes are removed from the sever by specifying their id.
|
||||
|
||||
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 |
|
||||
|
||||
Reference in New Issue
Block a user