Skip to content

GitLab

Unverified Commit a89f9bf6 authored by Dan Jones's avatar Dan Jones
Browse files

refactor: use parameters for not called again test

parent 7bb6235a
This commit is part of merge request !3. Comments created here will be created in the context of that merge request.
Show whitespace changes
Inline Side-by-side
Showing with 9 additions and 9 deletions
features/adapter_broadcast.feature
View file @ a89f9bf6
......@@ -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
features/adapter_poll.feature
View file @ a89f9bf6
......@@ -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
features/adapter_publish.feature
View file @ a89f9bf6
......@@ -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
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment