e4606ab84a
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>
29 lines
1.2 KiB
Gherkin
29 lines
1.2 KiB
Gherkin
#
|
|
# Copyright 2019 Banco Bilbao Vizcaya Argentaria, S.A.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
#
|
|
Feature: Fail to retrieve resources from nonexistent handler in Kapow! server.
|
|
If trying to access a nonexistent handler then the
|
|
server responds with a not found error.
|
|
|
|
Scenario: Try to get a valid resource path from a nonexistent handler.
|
|
A request to retrieve a resource from a
|
|
nonexistent handler will trigger
|
|
a handler ID not found error.
|
|
|
|
Given I have a running Kapow! server
|
|
When I get the resource "/request/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
|