Changed get resource item and handler ID not found scenarios.

This change is to comply with Go's implementation.

Co-authored-by: pancho horrillo <pedrofelipe.horrillo.@bbva.com>
This commit is contained in:
Héctor Hurtado
2019-10-29 15:50:43 +01:00
parent 712d26db89
commit 0021f754fd
2 changed files with 8 additions and 9 deletions
@@ -28,12 +28,11 @@ Feature: Fail to retrieve resources from nonexistent handler in Kapow! server.
# 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
A request to retrieve an invalid resource from a nonexistent
handler will trigger an invalid resource path 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
Then I get 400 as response code
# And I get "Invalid Resource Path" as response reason phrase