From 4cb86b18e521b4703199746c9edb18fe44edc920 Mon Sep 17 00:00:00 2001 From: Maximilian Laue Date: Fri, 2 May 2025 14:04:50 +0200 Subject: [PATCH] update test-definitions with the correct `types`-values --- .../connected-network-type-subscriptions.feature | 2 +- .../device-reachability-status-subscriptions.feature | 8 ++++---- .../device-roaming-status-subscriptions.feature | 10 +++++----- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/code/Test_definitions/connected-network-type-subscriptions.feature b/code/Test_definitions/connected-network-type-subscriptions.feature index bc183aca..9e79b08e 100644 --- a/code/Test_definitions/connected-network-type-subscriptions.feature +++ b/code/Test_definitions/connected-network-type-subscriptions.feature @@ -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 diff --git a/code/Test_definitions/device-reachability-status-subscriptions.feature b/code/Test_definitions/device-reachability-status-subscriptions.feature index ffa28c26..52e58851 100644 --- a/code/Test_definitions/device-reachability-status-subscriptions.feature +++ b/code/Test_definitions/device-reachability-status-subscriptions.feature @@ -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 @@ -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 @@ -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 @@ -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 diff --git a/code/Test_definitions/device-roaming-status-subscriptions.feature b/code/Test_definitions/device-roaming-status-subscriptions.feature index 545e15cf..e0207b8c 100644 --- a/code/Test_definitions/device-roaming-status-subscriptions.feature +++ b/code/Test_definitions/device-roaming-status-subscriptions.feature @@ -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 @@ -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 @@ -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 @@ -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 @@ -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