From a89f9bf6d1f28856b1536af02ac3a11c92ec9e22 Mon Sep 17 00:00:00 2001 From: Dan Jones <dan.jones@noc.ac.uk> Date: Mon, 20 Feb 2023 16:32:19 +0000 Subject: [PATCH] refactor: use parameters for not called again test --- features/adapter_broadcast.feature | 6 +++--- features/adapter_poll.feature | 6 +++--- features/adapter_publish.feature | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/features/adapter_broadcast.feature b/features/adapter_broadcast.feature index 7d3e02d..8063a2a 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 4e7116e..115d04b 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 10e4f5d..cd17cb5 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 -- GitLab