From e4606ab84a1b99bbd21f1a1c8d72907139cb0de8 Mon Sep 17 00:00:00 2001 From: pancho horrillo Date: Mon, 11 Nov 2019 17:32:52 +0100 Subject: [PATCH] Drop compound error scenario MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .../data/handler/error_handleridnotfound.feature | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/spec/test/features/data/handler/error_handleridnotfound.feature b/spec/test/features/data/handler/error_handleridnotfound.feature index 3aea141..34b13f2 100644 --- a/spec/test/features/data/handler/error_handleridnotfound.feature +++ b/spec/test/features/data/handler/error_handleridnotfound.feature @@ -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" Then I get 404 as response code 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