Skip to content

Update scenarios for non-existent and unable to locate devices #390

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

Open
bigludo7 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update scenarios for non-existent and unable to locate devices #390

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
09dcc33
Update scenarios for non-existent and unable to locate devices
bigludo7 Mar 10, 2026
71325be
Delete non-existent device scenario from feature file
bigludo7 Mar 24, 2026
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
30 changes: 14 additions & 16 deletions code/Test_definitions/location-retrieval.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ Feature: CAMARA Device location retrieval API, vwip - Operation retrieveLocation
# * A device object which location is known by the network when connected. 2 distinct device are required for some scenario.
# * A device object identifying a device commercialized by the implementation for which the service is not applicable
# * A device object which location cannot be provided during test by the network.
# * A identifier to a non-existent device
# * apiRoot: API root of the server URL
#
# References to OAS spec schemas refer to schemas specifies in location-retrieval.yaml
Expand Down Expand Up @@ -222,22 +223,6 @@ Feature: CAMARA Device location retrieval API, vwip - Operation retrieveLocation
And the response property "$.code" is "PERMISSION_DENIED"
And the response property "$.message" contains a user friendly text

# Error code 404

@location_retrieval_404_unable_to_locate_device
# Input set to a device that could not be located
Scenario: Unable to provide device location
Given a valid testing device which cannot be located by the network operator, identified by the token or provided in the request body

And the request body property "$.maxAge" is not included
When the request "retrieveLocation" is sent
Then the response status code is 404
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 property "$.status" is 404
And the response property "$.code" is "LOCATION_RETRIEVAL.DEVICE_NOT_FOUND"
And the response property "$.message" contains a user friendly text

# HTTP - 422

@location_retrieval_422.1_unable_to_fulfill_max_surface
Expand All @@ -264,3 +249,16 @@ Feature: CAMARA Device location retrieval API, vwip - Operation retrieveLocation
And the response property "$.status" is 422
And the response property "$.code" is "LOCATION_RETRIEVAL.UNABLE_TO_FULFILL_MAX_AGE"
And the response property "$.message" contains a user friendly text

@location_retrieval_422.3_unable_to_locate_device
# Input set to a device that could not be located without maxAge
Scenario: Unable to provide device location
Given a valid testing device which cannot be located by the network operator, identified by the token or provided in the request body
And the request body property "$.maxAge" is not included
When the request "retrieveLocation" is sent
Then the response status code is 422
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 property "$.status" is 422
And the response property "$.code" is "LOCATION_RETRIEVAL.UNABLE_TO_LOCATE"
And the response property "$.message" contains a user friendly text
Loading