From 15090f2fdfa3240e13bbcb13b4659f860c40389a Mon Sep 17 00:00:00 2001 From: Eric Murray Date: Tue, 14 Jan 2025 18:36:36 +0000 Subject: [PATCH] Update qod-provisioning-createProvisioning.feature --- .../qod-provisioning-createProvisioning.feature | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/code/Test_definitions/qod-provisioning-createProvisioning.feature b/code/Test_definitions/qod-provisioning-createProvisioning.feature index c9c514268a..b3e4be4a8c 100644 --- a/code/Test_definitions/qod-provisioning-createProvisioning.feature +++ b/code/Test_definitions/qod-provisioning-createProvisioning.feature @@ -123,10 +123,12 @@ Feature: CAMARA QoD Provisioning API, vwip - Operation createProvisioning And the response property "$.code" is "INVALID_ARGUMENT" And the response property "$.message" contains a user friendly text + # Note that device schema validation errors (if any) should be thrown even if a 3-legged access token is being used @qod_provisioning_createProvisioning_400.5_device_identifiers_not_schema_compliant # Test every type of identifier even if not supported by the implementation Scenario Outline: Some device identifier value does not comply with the schema Given the request body property "" does not comply with the OAS schema at "" + And a 2-legged or 3-legged access token is being used When the request "createProvisioning" is sent Then the response status code is 400 And the response header "x-correlator" has same value as the request header "x-correlator" @@ -138,14 +140,14 @@ Feature: CAMARA QoD Provisioning API, vwip - Operation createProvisioning Examples: | device_identifier | oas_spec_schema | | $.device.phoneNumber | /components/schemas/PhoneNumber | - | $.device.ipv4Address | /components/schemas/NetworkAccessIdentifier | - | $.device.ipv6Address | /components/schemas/DeviceIpv4Addr | - | $.device.networkIdentifier | /components/schemas/DeviceIpv6Address | + | $.device.ipv4Address | /components/schemas/DeviceIpv4Addr | + | $.device.ipv6Address | /components/schemas/DeviceIpv6Address | + | $.device.networkIdentifier | /components/schemas/NetworkAccessIdentifier | # The maximum is considered in the schema so a generic schema validator may fail and generate a 400 INVALID_ARGUMENT without further distinction, and both could be accepted @qod_provisioning_createProvisioning_400.6_out_of_range_port Scenario: Out of range port - Given the request body property "$.device.ipv4Address.publicPort" is set to a value not between 0 and 65536 + Given the request body property "$.device.ipv4Address.publicPort" is set to a value not between 0 and 65535 When the request "createProvisioning" is sent Then the response status code is 400 And the response header "x-correlator" has same value as the request header "x-correlator"