Skip to content

Update test-definitions with the correct types-values #272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
maxl2287 wants to merge 1 commit into from
Closed

Update test-definitions with the correct types-values #272

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion code/Test_definitions/connected-network-type-subscriptions.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -465,7 +465,7 @@ Feature: CAMARA Connected Network Type Subscriptions API, v0.1.0 - Operations cr
And the response property "$.code" is "UNAUTHENTICATED" or "AUTHENTICATION_REQUIRED"
And the response property "$.message" contains a user friendly text

@connected_network_type_subscriptions_retrieve__list_401.10_no_authorization_header
@connected_network_type_subscriptions_retrieve_list_401.10_no_authorization_header
Scenario: No Authorization header
Given the request header "Authorization" is removed
When the request "retrieveConnectedNetworkTypeSubscriptionList" is sent
Expand Down
8 changes: 4 additions & 4 deletions code/Test_definitions/device-reachability-status-subscriptions.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -501,7 +501,7 @@ Feature: Device Reachability Status Subscriptions API, v0.7.0 - Operations creat
And the response property "$.code" is "UNAUTHENTICATED" or "AUTHENTICATION_REQUIRED"
And the response property "$.message" contains a user friendly text

@reachability_status_subscriptions_retrieve__list_401.10_no_authorization_header
@reachability_status_subscriptions_retrieve_list_401.10_no_authorization_header
Scenario: No Authorization header
Given the request header "Authorization" is removed
When the request "retrieveDeviceReachabilityStatusSubscriptionList" is sent
Expand Down Expand Up @@ -540,7 +540,7 @@ Feature: Device Reachability Status Subscriptions API, v0.7.0 - Operations creat
# To test this, a token must not have the required scope
Given the header "Authorization" set to an access token not including scope "device-reachability-status-subscriptions:org.camaraproject.device-reachability-status-subscriptions.v0.reachability-data:create"
And the request body is compliant with the schema "#/components/schemas/SubscriptionRequest"
And the request body property "$.types" is equal to "device-reachability-status-subscriptions:org.camaraproject.device-reachability-status-subscriptions.v0.reachability-data"
And the request body property "$.types" is equal to "org.camaraproject.device-reachability-status-subscriptions.v0.reachability-data"
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response status code is 403
And the response property "$.status" is 403
Expand All @@ -552,7 +552,7 @@ Feature: Device Reachability Status Subscriptions API, v0.7.0 - Operations creat
# To test this, a token must not have the required scope
Given the header "Authorization" set to an access token not including scope "device-reachability-status-subscriptions:org.camaraproject.device-reachability-status-subscriptions.v0.reachability-sms:create"
And the request body is compliant with the schema "#/components/schemas/SubscriptionRequest"
And the request body property "$.types" is equal to "device-reachability-status-subscriptions:org.camaraproject.device-reachability-status-subscriptions.v0.reachability-sms"
And the request body property "$.types" is equal to "org.camaraproject.device-reachability-status-subscriptions.v0.reachability-sms"
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response status code is 403
And the response property "$.status" is 403
Expand All @@ -564,7 +564,7 @@ Feature: Device Reachability Status Subscriptions API, v0.7.0 - Operations creat
# To test this, a token must not have the required scope
Given the header "Authorization" set to an access token not including scope "device-reachability-status-subscriptions:org.camaraproject.device-reachability-status-subscriptions.v0.reachability-disconnected:create"
And the request body is compliant with the schema "#/components/schemas/SubscriptionRequest"
And the request body property "$.types" is equal to "device-reachability-status-subscriptions:org.camaraproject.device-reachability-status-subscriptions.v0.reachability-disconnected"
And the request body property "$.types" is equal to "org.camaraproject.device-reachability-status-subscriptions.v0.reachability-disconnected"
When the request "createDeviceReachabilityStatusSubscription" is sent
Then the response status code is 403
And the response property "$.status" is 403
Expand Down
10 changes: 5 additions & 5 deletions code/Test_definitions/device-roaming-status-subscriptions.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -517,7 +517,7 @@ Feature: Device Roaming Status Subscriptions API, v0.7.0 - Operations createDevi
And the response property "$.code" is "UNAUTHENTICATED" or "AUTHENTICATION_REQUIRED"
And the response property "$.message" contains a user friendly text

@roaming_status_subscriptions_retrieve__list_401.10_no_authorization_header
@roaming_status_subscriptions_retrieve_list_401.10_no_authorization_header
Scenario: No Authorization header
Given the request header "Authorization" is removed
When the request "deleteDeviceRoamingStatusSubscriptionList" is sent
Expand Down Expand Up @@ -555,7 +555,7 @@ Feature: Device Roaming Status Subscriptions API, v0.7.0 - Operations createDevi
Scenario: subscription creation without having the required scope
Given the header "Authorization" set to an access token not including scope "device-roaming-status-subscriptions:org.camaraproject.device-roaming-status-subscriptions.v0.roaming-on:create"
And the request body is compliant with the schema "#/components/schemas/SubscriptionRequest"
And the request body property "$.types" is equal to "device-roaming-status-subscriptions:org.camaraproject.device-roaming-status-subscriptions.v0.roaming-on"
And the request body property "$.types" is equal to "org.camaraproject.device-roaming-status-subscriptions.v0.roaming-on"
When the request "createDeviceRoamingStatusSubscription" is sent
Then the response status code is 403
And the response property "$.status" is 403
Expand All @@ -566,7 +566,7 @@ Feature: Device Roaming Status Subscriptions API, v0.7.0 - Operations createDevi
Scenario: subscription creation without having the required scope
Given the header "Authorization" set to an access token not including scope "device-roaming-status-subscriptions:org.camaraproject.device-roaming-status-subscriptions.v0.roaming-off:create"
And the request body is compliant with the schema "#/components/schemas/SubscriptionRequest"
And the request body property "$.types" is equal to "device-roaming-status-subscriptions:org.camaraproject.device-roaming-status-subscriptions.v0.roaming-off"
And the request body property "$.types" is equal to "org.camaraproject.device-roaming-status-subscriptions.v0.roaming-off"
When the request "createDeviceRoamingStatusSubscription" is sent
Then the response status code is 403
And the response property "$.status" is 403
Expand All @@ -577,7 +577,7 @@ Feature: Device Roaming Status Subscriptions API, v0.7.0 - Operations createDevi
Scenario: subscription creation without having the required scope
Given the header "Authorization" set to an access token not including scope "device-roaming-status-subscriptions:org.camaraproject.device-roaming-status-subscriptions.v0.roaming-status:create"
And the request body is compliant with the schema "#/components/schemas/SubscriptionRequest"
And the request body property "$.types" is equal to "device-roaming-status-subscriptions:org.camaraproject.device-roaming-status-subscriptions.v0.roaming-status"
And the request body property "$.types" is equal to "org.camaraproject.device-roaming-status-subscriptions.v0.roaming-status"
When the request "createDeviceRoamingStatusSubscription" is sent
Then the response status code is 403
And the response property "$.status" is 403
Expand All @@ -588,7 +588,7 @@ Feature: Device Roaming Status Subscriptions API, v0.7.0 - Operations createDevi
Scenario: subscription creation without having the required scope
Given the header "Authorization" set to an access token not including scope "device-roaming-status-subscriptions:org.camaraproject.device-roaming-status-subscriptions.v0.roaming-change-country:create"
And the request body is compliant with the schema "#/components/schemas/SubscriptionRequest"
And the request body property "$.types" is equal to "device-roaming-status-subscriptions:org.camaraproject.device-roaming-status-subscriptions.v0.roaming-change-country"
And the request body property "$.types" is equal to "org.camaraproject.device-roaming-status-subscriptions.v0.roaming-change-country"
When the request "createDeviceRoamingStatusSubscription" is sent
Then the response status code is 403
And the response property "$.status" is 403
Expand Down