-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #186 from mdomale/patch-1
Create Gherkin tests for device-status-reachability and device-status-roaming
- Loading branch information
Showing
2 changed files
with
284 additions
and
0 deletions.
There are no files selected for viewing
149 changes: 149 additions & 0 deletions
149
code/Test_definitions/device-reachability-status.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,149 @@ | ||
|
|
||
| @Device_reachability_status | ||
| Feature: CAMARA Device reachability status API, v0.6.0 - Operations for reachability status | ||
|
|
||
| # Input to be provided by the implementation to the tests | ||
| # References to OAS spec schemas refer to schemas specifies in device-reachability-status.yaml, version v0.6.0 | ||
|
|
||
| Background: Common Device reachability status setup | ||
| Given the resource "{api-root}/device-reachability-status/v0.6/retrieve" set as base-url | | ||
| And the header "Content-Type" is set to "application/json" | ||
| And the header "Authorization" is set to a valid access token | ||
| And the header "x-correlator" is set to a UUID value | ||
|
|
||
| ############# Happy Path Scenarios ################## | ||
|
|
||
| @device_reachability_status_01_reachabilityStatusConnectedSms | ||
| Scenario: Check the reachability status if device is connected with SMS | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" is set to a valid testing device which is connected with sms and supported by the service | ||
| When the request "getReachabilityStatus" 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" | ||
| And the response body complies with the OAS schema at "/components/schemas/ReachabilityStatusResponse" | ||
| And the response property "$.status" is 200 | ||
| And the response property "$.code" is "OK" | ||
| And the response property "$.message" contains a user friendly text | ||
| And the response property "$.reachabilityStatus" is "CONNECTED_SMS" | ||
|
|
||
| @device_reachability_status_02_reachabilityStatusConnectedData | ||
| Scenario: Check the reachability status if device is connected with DATA | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" is set to a valid testing device which is connected with data and supported by the service | ||
| When the request "getReachabilityStatus" 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" | ||
| And the response body complies with the OAS schema at "/components/schemas/ReachabilityStatusResponse" | ||
| And the response property "$.status" is 200 | ||
| And the response property "$.code" is "OK" | ||
| And the response property "$.reachabilityStatus" is "CONNECTED_DATA" | ||
|
|
||
| @device_reachability_status_03_reachabilityStatusDeviceNotConnected | ||
| Scenario: Check the reachability status for DeviceNotConnected | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" is set to a valid testing device which is not connected and supported by the service | ||
| When the request "getReachabilityStatus" 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" | ||
| And the response body complies with the OAS schema at "/components/schemas/ReachabilityStatusResponse" | ||
| And the response property "$.status" is 200 | ||
| And the response property "$.code" is "OK" | ||
| And the response property "$.reachabilityStatus" is "NOT_CONNECTED" | ||
|
|
||
| #############Error Response Scenarios################## | ||
|
|
||
| @device_reachability_status_04_deviceStatus_with_invalid_parameter | ||
| Scenario: Device reachability status request with invalid parameter | ||
| Given the request body is not compliant with the schema "/components/schemas/RequestReachabilityStatus" | ||
| When the request "getReachabilityStatus" is sent | ||
| Then Response code is 400 | ||
| And the response property "$.status" is 400 | ||
| And the response property "$.code" is "INVALID_ARGUMENT" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_reachability_status_05_expired_access_token | ||
| Scenario: Expired access token | ||
| Given a valid devicestatus request body | ||
| And header "Authorization" is set to expired token | ||
| When the request "getReachabilityStatus" is sent | ||
| Then the response status code is 401 | ||
| And the response property "$.status" is 401 | ||
| And the response property "$.code" is "UNAUTHENTICATED" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_reachability_status_06_no_authorization_header | ||
| Scenario: No Authorization header | ||
| Given a valid devicestatus request body | ||
| And header "Authorization" is not available | ||
| When the request "getReachabilityStatus" is sent | ||
| Then the response status code is 401 | ||
| And the response property "$.status" is 401 | ||
| And the response property "$.code" is "UNAUTHENTICATED" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_reachability_status_07_invalid_access_token | ||
| Scenario: Invalid access token | ||
| Given a valid devicestatus request body | ||
| And header "Authorization" set to an invalid access token | ||
| When the request "getReachabilityStatus" is sent | ||
| Then the response status code is 401 | ||
| And the response header "Content-Type" is "application/json" | ||
| And the response property "$.status" is 401 | ||
| And the response property "$.code" is "UNAUTHENTICATED" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_reachability_status_08_deviceStatus_inconsistent_access_token | ||
| Scenario: Inconsistent access token context for the device | ||
| # To test this, a token has to be obtained for a different device | ||
| Given a valid devicestatus 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 "getReachabilityStatus" is sent | ||
| Then the response status code is 403 | ||
| And the response property "$.status" is 403 | ||
| And the response property "$.code" is "INVALID_TOKEN_CONTEXT" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_reachability_status_09_deviceStatusWithIdentifiersMismatch | ||
| Scenario: Device reachabilityidentifiers mismatch | ||
| # To test this, at least 2 types of identifiers have to be provided, e.g. a phoneNumber and the IP address of a Device reachability associated to a different phoneNumber | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" includes several identifiers, each of them identifying a valid but different device | ||
| When the request "getReachabilityStatus" is sent | ||
| Then the response status code is 422 | ||
| And the response property "$.status" is 422 | ||
| And the response property "$.code" is "DEVICE_IDENTIFIERS_MISMATCH" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_reachability_status_10_deviceStatus_NotApplicable | ||
| Scenario: Device reachability not applicable | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" refers to an unknown device | ||
| When the request "getReachabilityStatus" is sent | ||
| Then the response status code is 422 | ||
| And the response property "$.status" is 422 | ||
| And the response property "$.code" is "DEVICE_NOT_APPLICABLE" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_reachability_status_11_unable_to_provide_reachability_status | ||
| Scenario: Unable to provide reachability status for a device | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" refers to a device having network issue | ||
| When the request "getReachabilityStatus" is sent | ||
| Then the response status code is 422 | ||
| And the response property "$.status" is 422 | ||
| And the response property "$.code" is "UNABLE_TO_PROVIDE_REACHABILITY_STATUS" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_reachability_status_12_unsupported_device_identifiers | ||
| Scenario: Unsupported device identifiers | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" set to unsupported identifiers value for the service | ||
| When the request "getReachabilityStatus" is sent | ||
| Then the response status code is 422 | ||
| And the response property "$.status" is 422 | ||
| And the response property "$.code" is "UNSUPPORTED_DEVICE_IDENTIFIERS" | ||
| And the response property "$.message" contains a user friendly text |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,135 @@ | ||
|
|
||
| @Device_Roaming_Status | ||
| Feature: CAMARA Device Roaming Status API, v0.6.0 - Operations for Roaming Status | ||
|
|
||
| # Input to be provided by the implementation to the tests | ||
| # References to OAS spec schemas refer to schemas specifies in device-roaming-status.yaml, version v0.6.0 | ||
|
|
||
| Background: Common Device Roaming status setup | ||
| Given the resource "{api-root}/device-roaming-status/v0.6/retrieve" set as base-url | | ||
| And the header "Content-Type" is set to "application/json" | ||
| And the header "Authorization" is set to a valid access token | ||
| And the header "x-correlator" is set to a UUID value | ||
|
|
||
| #############Happy Path Scenarios################## | ||
|
|
||
| @device_roaming_status_01_roaming_status_true | ||
| Scenario: Check the roaming status when device is in the roaming mode | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" is set to a valid testing device which is in roaming and supported by the service | ||
| When the request "getRoamingStatus" 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" | ||
| And the response body complies with the OAS schema at "/components/schemas/RoamingStatusResponse" | ||
| And the response property "$.status" is 200 | ||
| And the response property "$.code" is "OK" | ||
| And the response property "$.message" contains a user friendly text | ||
| Then the roaming status is true | ||
|
|
||
| @device_roaming_status_02_roaming_status_false | ||
| Scenario: Check the roaming state synchronously if the device is not in the roaming mode | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" is set to a valid testing device which is not in roaming and supported by the service | ||
| When the request "getRoamingStatus" 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" | ||
| And the response body complies with the OAS schema at "/components/schemas/RoamingStatusResponse" | ||
| And the response property "$.status" is 200 | ||
| And the response property "$.code" is "OK" | ||
| Then the roaming status is false | ||
|
|
||
| #############Error Response Scenarios################## | ||
|
|
||
| @device_roaming_status_03_deviceStatus_with_invalid_parameter | ||
| Scenario: Device status request with invalid parameter | ||
| Given the request body is not compliant with the schema "/components/schemas/RequestRoamingStatus" | ||
| When the request "getRoamingStatus" is sent | ||
| Then Response code is 400 | ||
| And the response property "$.status" is 400 | ||
| And the response property "$.code" is "INVALID_ARGUMENT" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_roaming_status_04_expired_access_token | ||
| Scenario: Expired access token | ||
| Given a valid devicestatus request body | ||
| And header "Authorization" is set to expired token | ||
| When the request "getRoamingStatus" is sent | ||
| Then the response status code is 401 | ||
| And the response property "$.status" is 401 | ||
| And the response property "$.code" is "UNAUTHENTICATED" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_roaming_status_05_no_authorization_header | ||
| Scenario: No Authorization header | ||
| Given a valid devicestatus request body | ||
| And header "Authorization" is not available | ||
| When the request "getRoamingStatus" is sent | ||
| Then the response status code is 401 | ||
| And the response property "$.status" is 401 | ||
| And the response property "$.code" is "UNAUTHENTICATED" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_roaming_status_06_invalid_access_token | ||
| Scenario: Invalid access token | ||
| Given a valid devicestatus request body | ||
| And header "Authorization" set to an invalid access token | ||
| Then the response status code is 401 | ||
| And the response header "Content-Type" is "application/json" | ||
| And the response property "$.status" is 401 | ||
| And the response property "$.code" is "UNAUTHENTICATED" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_roaming_status_07_deviceStatus_inconsistent_access_token | ||
| Scenario: Inconsistent access token context for the device | ||
| # To test this, a token has to be obtained for a different device | ||
| Given a valid devicestatus 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 "getRoamingStatus" is sent | ||
| Then the response status code is 403 | ||
| And the response property "$.status" is 403 | ||
| And the response property "$.code" is "INVALID_TOKEN_CONTEXT" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_roaming_status_08_deviceStatusWithIdentifiersMismatch | ||
| Scenario: Device identifiers mismatch | ||
| # To test this, at least 2 types of identifiers have to be provided, e.g. a phoneNumber and the IP address of a device associated to a different phoneNumber | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" includes several identifiers, each of them identifying a valid but different device | ||
| When the request "getRoamingStatus" is sent | ||
| Then the response status code is 422 | ||
| And the response property "$.status" is 422 | ||
| And the response property "$.code" is "DEVICE_IDENTIFIERS_MISMATCH" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_roaming_status_09_deviceStatus_not_applicable | ||
| Scenario: Device roaming not applicable | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" refers to an unknown device | ||
| When the request "getRoamingStatus" is sent | ||
| Then the response status code is 422 | ||
| And the response property "$.status" is 422 | ||
| And the response property "$.code" is "DEVICE_NOT_APPLICABLE" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_roaming_status_10_deviceStatus_unable_to_provide_reachability_status | ||
| Scenario: Unable to provide roaming status for a device | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" refers to a device having network issue | ||
| When the request "getRoamingStatus" is sent | ||
| Then the response status code is 422 | ||
| And the response property "$.status" is 422 | ||
| And the response property "$.code" is "UNABLE_TO_PROVIDE_ROAMING_STATUS" | ||
| And the response property "$.message" contains a user friendly text | ||
|
|
||
| @device_roaming_status_11_deviceStatus_unsupported_device_identifiers | ||
| Scenario: Unsupported device identifiers | ||
| Given a valid devicestatus request body | ||
| And the request body property "$.device" set to unsupported identifiers value for the service | ||
| When the request "getRoamingStatus" is sent | ||
| Then the response status code is 422 | ||
| And the response property "$.status" is 422 | ||
| And the response property "$.code" is "UNSUPPORTED_DEVICE_IDENTIFIERS" | ||
| And the response property "$.message" contains a user friendly text |