Skip to content

GitLab

Merged
Created by Dan Jones@danjonOwner

Resolve "Error handling on send"

Compare
and
3 files
+ 113
- 7
Show latest version
feat‎ures‎
adapter_broa‎dcast.feature‎ +44 -2
adapter_po‎ll.feature‎ +44 -1
adapter_pub‎lish.feature‎ +25 -4
features/adapter_broadcast.feature
+ 44
- 2
Show all unchanged lines Show 20 lines
Given valid config
When the adapter instance is created
When the auth method is called
When a mock notify API response is configured to return an error
When a mock notify API response is configured to return a 403 error
When the broadcast method is called
Then an error response is returned with status 403
\ No newline at end of file
Then an error response is returned with status 403
Scenario: On 403 the message is retried once with new credentials
Given valid config
When the adapter instance is created
When the auth method is called
When a mock notify API response is configured to return a 403 error
When the broadcast method is called
Then an error response is returned with status 403
Then the credentials are deleted
Then the broadcast method was called with is_retry on
Then the getAuthorizationHeader method is called
Scenario: On a retried 403 the message is not retried again
Given valid config
When the adapter instance is created
When the auth method is called
When a mock notify API response is configured to return a 403 error
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
Scenario: On 503 the message is retried once with the same credentials
Given valid config
When the adapter instance is created
When the auth method is called
When a mock notify API response is configured to return a 503 error
When the broadcast method is called
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
Scenario: On a retried 503 the message is not retried again
Given valid config
When the adapter instance is created
When the auth method is called
When a mock notify API response is configured to return a 503 error
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
features/adapter_poll.feature
+ 44
- 1
Show all unchanged lines Show 20 lines
Given valid config
When the adapter instance is created
When the auth method is called
When a mock receive API response is configured to return an error
When a mock receive API response is configured to return a 403 error
When the poll method is called
Then an error response is returned with status 403
Scenario: On 403 the message is retried once with new credentials
Given valid config
When the adapter instance is created
When the auth method is called
When a mock receive API response is configured to return a 403 error
When the poll method is called
Then an error response is returned with status 403
Then the credentials are deleted
Then the poll method was called with is_retry on
Then the getAuthorizationHeader method is called
Scenario: On a retried 403 the message is not retried again
Given valid config
When the adapter instance is created
When the auth method is called
When a mock receive API response is configured to return a 403 error
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
Scenario: On 503 the message is retried once with the same credentials
Given valid config
When the adapter instance is created
When the auth method is called
When a mock receive API response is configured to return a 503 error
When the poll method is called
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
Scenario: On a retried 503 the message is not retried again
Given valid config
When the adapter instance is created
When the auth method is called
When a mock receive API response is configured to return a 503 error
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
\ No newline at end of file
features/adapter_publish.feature
+ 25
- 4
Show all unchanged lines Show 20 lines
Given valid config
When the adapter instance is created
When the auth method is called
When a mock send API response is configured to return an error
When a mock send API response is configured to return a 403 error
When the publish method is called
Then an error response is returned with status 403
Show 20 lines Show all unchanged lines Show 20 lines
Given valid config
When the adapter instance is created
When the auth method is called
When a mock send API response is configured to return an error
When a mock send API response is configured to return a 403 error
When the publish method is called
Then an error response is returned with status 403
Then the credentials are deleted
Show 20 lines Show all unchanged lines Show 20 lines
Given valid config
When the adapter instance is created
When the auth method is called
When a mock send API response is configured to return an error
When a mock send API response is configured to return a 403 error
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
When the adapter instance is created
When the auth method is called
When a mock send API response is configured to return a 503 error
When the publish method is called
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
Scenario: On a retried 503 the message is not retried again
Given valid config
When the adapter instance is created
When the auth method is called
When a mock send API response is configured to return a 503 error
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