Skip to content

Fix issue 443 #446

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

Merged
jlurien merged 1 commit into from
Oct 20, 2026
+0 −26
Merged

Fix issue 443 #446

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
13 changes: 0 additions & 13 deletions code/Test_definitions/geofencing-subscriptions-createGeofencingSubscription.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,19 +237,6 @@ Feature: Camara Geofencing Subscriptions API, vwip - Operation createGeofencingS
And the response property "$.code" is "SERVICE_NOT_APPLICABLE"
And the response property "$.message" contains a user-friendly text

# Several identifiers provided but they do not identify the same device
# This scenario may happen with 2-legged access tokens, which do not identify a device
@geofencing_subscriptions_C01.08_device_identifiers_mismatch
Scenario: Device identifiers mismatch
Given the header "Authorization" is set to a valid access token which does not identify a single device
And at least 2 types of device identifiers are supported by the implementation
And the request body property "$.config.subscriptionDetail.device" includes several identifiers, each of them identifying a valid but different device
When the request "createGeofencingSubscription" is sent
Then the response status code is 422
And the response property "$.status" is 422
And the response property "$.code" is "IDENTIFIER_MISMATCH"
And the response property "$.message" contains a user friendly text

# Error code 400

@geofencing_subscriptions_400.1_create_subscriptions_with_invalid_parameter
Expand Down
13 changes: 0 additions & 13 deletions code/Test_definitions/location-retrieval.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,19 +156,6 @@ Feature: CAMARA Device location retrieval API, vwip - Operation retrieveLocation
And the response property "$.code" is "SERVICE_NOT_APPLICABLE"
And the response property "$.message" contains a user-friendly text

# Several identifiers provided but they do not identify the same device
# This scenario may happen with 2-legged access tokens, which do not identify a device
@location_retrieval_C01.08_device_identifiers_mismatch
Scenario: Device identifiers mismatch
Given the header "Authorization" is set to a valid access token which does not identify a single device
And at least 2 types of device identifiers are supported by the implementation
And the request body property "$.device" includes several identifiers, each of them identifying a valid but different device
When the request "retrieveLocation" is sent
Then the response status code is 422
And the response property "$.status" is 422
And the response property "$.code" is "IDENTIFIER_MISMATCH"
And the response property "$.message" contains a user friendly text

# Error code 400

@location_retrieval_400.1_no_request_body
Expand Down
Loading