Skip to content

Commit

Permalink
Update device-reachability-status-subscriptions.feature
Browse files Browse the repository at this point in the history
  • Loading branch information
@mdomale
mdomale authored Aug 30, 2024
1 parent bf37c42 commit b48638e
Showing 1 changed file with 19 additions and 19 deletions.
38 changes: 19 additions & 19 deletions code/Test_definitions/device-reachability-status-subscriptions.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Feature: Device Reachability Status Subscriptions API, v0.6.0 - Operations Reach
Scenario: Create reachability status subscription synchronously
Given that subscriptions are created synchronously
And a valid subscription request body
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 201
And the response header "Content-Type" is "application/json"
And the response header "x-correlator" has same value as the request header "x-correlator"
Expand All @@ -26,7 +26,7 @@ Feature: Device Reachability Status Subscriptions API, v0.6.0 - Operations Reach
Scenario: Create reachability status subscription asynchronously
Given that subscriptions are created asynchronously
And a valid subscription request body
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 202
And the response header "Content-Type" is "application/json"
And the response header "x-correlator" has same value as the request header "x-correlator"
Expand All @@ -53,7 +53,7 @@ Feature: Device Reachability Status Subscriptions API, v0.6.0 - Operations Reach
@reachability_status_subscriptions_05_Operation_to_retrieve_subscription_based_on_an_existing_subscription-id
Scenario: Get a subscription based on existing subscription-id.
Given the path parameter "subscriptionId" is set to the identifier of an existing subscription
When the request "retrieveReachabilityStatusSubscription" is sent
When the request "retrieveSubscription" is sent
Then the response code is 200
And the response header "Content-Type" is "application/json"
And the response header "x-correlator" has same value as the request header "x-correlator"
Expand All @@ -62,7 +62,7 @@ Feature: Device Reachability Status Subscriptions API, v0.6.0 - Operations Reach
@reachability_status_subscriptions_06_Operation_to_delete_subscription_based_on_an_existing_subscription-id
Scenario: Delete a subscription based on existing subscription-id.
Given the path parameter "subscriptionId" is set to the identifier of an existing subscription
When the request "deleteReachabilityStatusSubscription" is sent
When the request "deleteSubscription" is sent
Then the response code is 202 or 204
And the response header "x-correlator" has same value as the request header "x-correlator"
And if the response property $.status is 204 then response body is not available
Expand All @@ -73,7 +73,7 @@ Feature: Device Reachability Status Subscriptions API, v0.6.0 - Operations Reach
Given that subscriptions are created synchronously
And a valid subscription request body
And the request body property "$.type" is "reachability-data"
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 201
And if the device reachability is changed to data usage
Then event notification "reachability-data" is received on callback-url
Expand All @@ -86,7 +86,7 @@ Feature: Device Reachability Status Subscriptions API, v0.6.0 - Operations Reach
Given that subscriptions are created synchronously
And a valid subscription request body
And the request body property "$.type" is "reachability-sms"
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 201
And if the device reachability is changed to sms usage
Then event notification "reachability-sms" is received on callback-url
Expand All @@ -99,7 +99,7 @@ Feature: Device Reachability Status Subscriptions API, v0.6.0 - Operations Reach
Given that subscriptions are created synchronously
And a valid subscription request body
And the request body property "$.type" is "reachability-disconnected"
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 201
And if the device reachability is changed to disconnected
Then event notification "reachability-disconnected" is received on callback-url
Expand All @@ -112,7 +112,7 @@ Scenario: Receive notification for subscription-ends event on expiry
Given that subscriptions are created synchronously
And a valid subscription request body
And the request body property "$.subscriptionExpireTime" is set to a value in the near future
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 201
Then the subscription is expired
Then event notification "subscription-ends" is received on callback-url
Expand All @@ -126,7 +126,7 @@ Scenario: Receive notification for subscription-ends event on expiry
And a valid subscription request body
And the request body property "$.type" is "reachability-data"
And the request body property "$.subscriptionMaxEvents" is set to 1
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 201
Then event notification "reachability-data" is received on callback-url
Then event notification "subscription-ends" is received on callback-url
Expand All @@ -138,9 +138,9 @@ Scenario: Receive notification for subscription-ends event on expiry
Scenario: Receive notification for subscription-ends event on deletion
Given that subscriptions are created synchronously
And a valid subscription request body
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 201
When the request "deleteReachabilityStatusSubscription" is sent
When the request "deleteSubscription" is sent
Then the response code is 202 or 204
Then event notification "subscription-ends" is received on callback-url
And notification body complies with the OAS schema at "##/components/schemas/EventSubscriptionEnds"
Expand All @@ -153,7 +153,7 @@ Scenario: Receive notification for subscription-ends event on expiry
@reachability_status_subscriptions_13_Create_reachability_status_subscription_with_invalid_parameter
Scenario: Create subscription with invalid parameter
Given the request body is not compliant with the schema "/components/schemas/SubscriptionRequest"
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 400
And the response property "$.status" is 400
And the response property "$.code" is "INVALID_ARGUMENT"
Expand All @@ -163,7 +163,7 @@ Scenario: Receive notification for subscription-ends event on expiry
Scenario: Expiry time in past
Given a valid subscription request body
And request body property "$.subscriptionexpiretime" in past
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response code is 400
And the response property "$.status" is 400
And the response property "$.code" is "INVALID_ARGUMENT"
Expand All @@ -173,7 +173,7 @@ Scenario: Receive notification for subscription-ends event on expiry
Scenario: subscription creation with invalid protocol
Given a valid subscription request body
And the request property "$.protocol" is not set to "HTTP"
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response property "$.status" is 400
And the response property "$.code" is "INVALID_PROTOCOL"
And the response property "$.message" contains a user friendly text
Expand All @@ -182,7 +182,7 @@ Scenario: Receive notification for subscription-ends event on expiry
Scenario: subscription creation with invalid credential type
Given a valid subscription request body
And the request property "$.credentialType" is not "ACCESSTOKEN"
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response property "$.status" is 400
And the response property "$.code" is "INVALID_CREDENTIAL"
And the response property "$.message" contains a user friendly text
Expand All @@ -191,7 +191,7 @@ Scenario: Receive notification for subscription-ends event on expiry
Scenario: subscription creation with invalid access token type
Given a valid subscription request body
And the request property "$.accessTokenType" is not "bearer"
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response property "$.status" is 400
And the response property "$.code" is "INVALID_TOKEN" or "INVALID_ARGUMENT"
And the response property "$.message" contains a user friendly text
Expand All @@ -200,7 +200,7 @@ Scenario: Receive notification for subscription-ends event on expiry
Scenario: subscription creation with invalid credentials
Given a valid subscription request body
And header "Authorization" token is set to invalid credentials
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response property "$.status" is 401
And the response property "$.code" is "UNAUTHENTICATED"
And the response property "$.message" contains a user friendly text
Expand All @@ -211,15 +211,15 @@ Scenario: Receive notification for subscription-ends event on expiry
Given a valid subscription request body
And the request body property "$.device" is set to a valid testing device supported by the service
And header "Authorization" set to access token referring different device
When the request "createSubscription" is sent
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response property "$.status" is 403
And the response property "$.code" is "SUBSCRIPTION_MISMATCH"
And the response property "$.message" contains a user friendly text

@reachability_status_subscription_20_unknown_subscription_id
Scenario: Get subscription when subscription-id is unknown to the system
Given the path parameter property "$.subscriptionId" is unknown to the system
When the request "retrieveReachabilityStatusSubscription" is sent
When the request "retrieveSubscription" is sent
Then the response property "$.status" is 404
And the response property "$.code" is "NOT_FOUND"
And the response property "$.message" contains a user friendly text

0 comments on commit b48638e

Please sign in to comment.