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

Drop compound error scenario

Browse Source 
In order to allow different Kapow! implementations (Go, Python, ...)
compound errors will be left as implementation-dependent.
The spec will only test for simple error conditions.

Co-authored-by: Roberto Abdelkader Martínez Pérez <robertomartinezp@gmail.com>
This commit is contained in:
pancho horrillo
2019-11-11 17:32:52 +01:00
parent 9eb186bd0f
commit e4606ab84a
1 changed files with 0 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec/test/features/data/handler/error_handleridnotfound.feature
-10
View File
@@ -26,13 +26,3 @@ Feature: Fail to retrieve resources from nonexistent handler in Kapow! server.
When I get the resource "/request/path" for the handler with 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 "Handler ID Not Found" as response reason phrase And I get "Handler ID Not Found" as response reason phrase
Scenario: Try to get an invalid resource from a nonexistent handler.
A request to retrieve an invalid resource from a nonexistent
handler will trigger a handler ID not found error
even if the resource is invalid.
Given I have a running Kapow! server
When I get the resource "/invalid/path" for the handler with id "XXXXXXXXXX"
Then I get 404 as response code
And I get "Handler ID Not Found" as response reason phrase