Skip to content

Fix C01.02_device_identifiers_not_schema_compliant Fix feature scenario example #376

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
Sep 2, 2025
Merged

Fix C01.02_device_identifiers_not_schema_compliant Fix feature scenario example #376

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
10 changes: 5 additions & 5 deletions code/Test_definitions/geofencing-subscriptions.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,11 +168,11 @@ Feature: Camara Geofencing Subscriptions API, vwip - Operations on subscriptions
And the response property "$.message" contains a user friendly text

Examples:
| device_identifier | oas_spec_schema |
| $.config.subscriptionDetail.device.phoneNumber | /components/schemas/PhoneNumber |
| $.config.subscriptionDetail.device.ipv4Address | /components/schemas/DeviceIpv4Addr |
| $.config.subscriptionDetail.device.ipv6Address | /components/schemas/DeviceIpv6Address |
| $.config.subscriptionDetail.device.networkIdentifier | /components/schemas/NetworkAccessIdentifier |
| device_identifier | oas_spec_schema |
| $.config.subscriptionDetail.device.phoneNumber | /components/schemas/PhoneNumber |
| $.config.subscriptionDetail.device.ipv4Address | /components/schemas/DeviceIpv4Addr |
| $.config.subscriptionDetail.device.ipv6Address | /components/schemas/DeviceIpv6Address |
| $.config.subscriptionDetail.device.networkAccessIdentifier | /components/schemas/NetworkAccessIdentifier |

# This scenario may happen e.g. with 2-legged access tokens, which do not identify a single device.
@geofencing_subscriptions_C01.03_device_not_found
Expand Down
10 changes: 5 additions & 5 deletions code/Test_definitions/location-retrieval.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,11 +82,11 @@ Feature: CAMARA Device location retrieval API, vwip - Operation retrieveLocation
And the response property "$.message" contains a user friendly text

Examples:
| device_identifier | oas_spec_schema |
| $.device.phoneNumber | /components/schemas/PhoneNumber |
| $.device.ipv4Address | /components/schemas/DeviceIpv4Addr |
| $.device.ipv6Address | /components/schemas/DeviceIpv6Address |
| $.device.networkIdentifier | /components/schemas/NetworkAccessIdentifier |
| device_identifier | oas_spec_schema |
| $.device.phoneNumber | /components/schemas/PhoneNumber |
| $.device.ipv4Address | /components/schemas/DeviceIpv4Addr |
| $.device.ipv6Address | /components/schemas/DeviceIpv6Address |
| $.device.networkAccessIdentifier | /components/schemas/NetworkAccessIdentifier |

@location_retrieval_C01.03_device_not_found
Scenario: Some identifier cannot be matched to a device
Expand Down
10 changes: 5 additions & 5 deletions code/Test_definitions/location-verification.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,11 +101,11 @@ Feature: CAMARA Device location verification API, vwip - Operation verifyLocatio
And the response property "$.message" contains a user friendly text

Examples:
| device_identifier | oas_spec_schema |
| $.device.phoneNumber | /components/schemas/PhoneNumber |
| $.device.ipv4Address | /components/schemas/DeviceIpv4Addr |
| $.device.ipv6Address | /components/schemas/DeviceIpv6Address |
| $.device.networkIdentifier | /components/schemas/NetworkAccessIdentifier |
| device_identifier | oas_spec_schema |
| $.device.phoneNumber | /components/schemas/PhoneNumber |
| $.device.ipv4Address | /components/schemas/DeviceIpv4Addr |
| $.device.ipv6Address | /components/schemas/DeviceIpv6Address |
| $.device.networkAccessIdentifier | /components/schemas/NetworkAccessIdentifier |

# This scenario may happen e.g. with 2-legged access tokens, which do not identify a single device.
@location_verification_C01.03_device_not_found
Expand Down