diff --git a/features/adapter_broadcast.feature b/features/adapter_broadcast.feature index 7d3e02d994c6c1fb488e2a6dd376f5f7fd46ae70..8063a2afd58a83bce89b2493b7e68b1152144d4c 100644 --- a/features/adapter_broadcast.feature +++ b/features/adapter_broadcast.feature @@ -36,7 +36,7 @@ Feature: Can the adapter broadcast messages? When the broadcast method is called with is_retry on Then an error response is returned with status 403 Then the credentials are deleted - Then the broadcast method is not called again + Then the "broadcast" method is not called again Scenario: On 503 the message is retried once with the same credentials Given valid config @@ -47,7 +47,7 @@ Feature: Can the adapter broadcast messages? Then an error response is returned with status 503 Then the credentials are not deleted Then the broadcast method was called with is_retry on - Then the getAuthorizationHeader method is not called again + Then the "getAuthorizationHeader" method is not called again Scenario: On a retried 503 the message is not retried again Given valid config @@ -57,4 +57,4 @@ Feature: Can the adapter broadcast messages? When the broadcast method is called with is_retry on Then an error response is returned with status 503 Then the credentials are not deleted - Then the broadcast method is not called again + Then the "broadcast" method is not called again diff --git a/features/adapter_poll.feature b/features/adapter_poll.feature index 4e7116e753fa1de475626fc54a23c41665be03fa..115d04bcf4fbb0d484e202e2c1df98443bf77b1a 100644 --- a/features/adapter_poll.feature +++ b/features/adapter_poll.feature @@ -60,7 +60,7 @@ Feature: Can the adapter receive messages? When the poll method is called with is_retry on Then an error response is returned with status 403 Then the credentials are deleted - Then the poll method is not called again + Then the "poll" method is not called again Scenario: On 503 the message is retried once with the same credentials Given valid config @@ -71,7 +71,7 @@ Feature: Can the adapter receive messages? Then an error response is returned with status 503 Then the credentials are not deleted Then the poll method was called with is_retry on - Then the getAuthorizationHeader method is not called again + Then the "getAuthorizationHeader" method is not called again Scenario: On a retried 503 the message is not retried again Given valid config @@ -81,5 +81,5 @@ Feature: Can the adapter receive messages? When the poll method is called with is_retry on Then an error response is returned with status 503 Then the credentials are not deleted - Then the poll method is not called again + Then the "poll" method is not called again \ No newline at end of file diff --git a/features/adapter_publish.feature b/features/adapter_publish.feature index 10e4f5d2e261f2b2841819c6a18a2bfc8d28ae94..cd17cb575d7706f36c0faa94a2a8328757391212 100644 --- a/features/adapter_publish.feature +++ b/features/adapter_publish.feature @@ -36,7 +36,7 @@ Feature: Can the adapter publish messages? When the publish method is called with is_retry on Then an error response is returned with status 403 Then the credentials are deleted - Then the publish method is not called again + Then the "publish" method is not called again Scenario: On 503 the message is retried once with new credentials Given valid config @@ -47,7 +47,7 @@ Feature: Can the adapter publish messages? Then an error response is returned with status 503 Then the credentials are not deleted Then the publish method was called with is_retry on - Then the getAuthorizationHeader method is not called again + Then the "getAuthorizationHeader" method is not called again Scenario: On a retried 503 the message is not retried again Given valid config @@ -57,4 +57,4 @@ Feature: Can the adapter publish messages? When the publish method is called with is_retry on Then an error response is returned with status 503 Then the credentials are not deleted - Then the publish method is not called again + Then the "publish" method is not called again