Skip to content

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

Open
bigludo7 wants to merge 1 commit intomainfrom
bigludo7-patch-1
Open

Update scenarios for non-existent and unable to locate devices#390
bigludo7 wants to merge 1 commit intomainfrom
bigludo7-patch-1

Conversation

@bigludo7
Copy link
Collaborator

@bigludo7 bigludo7 commented Mar 10, 2026

What type of PR is this?

Add one of the following kinds:

  • bug

What this PR does / why we need it:

Update scenarios for non-existent and unable to locate devices

Which issue(s) this PR fixes:

Fixes #388

Special notes for reviewers:

To be check if we are ok with 404 test case. I'm wondering if we're not going to far by testing non-existent device.

Changelog input

 release-note
- Add a test case for 422 LOCATION_RETRIEVAL.UNABLE_TO_LOCATE
- Update 404 test case to be used for non-existent devices

Additional documentation

This section can be blank.

FYI: @JayVaishnavNio

docs

Update scenarios for non-existent and unable to locate devices
@github-actions
Copy link

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.01s
✅ API spectral 3 0 5.09s
✅ GHERKIN gherkin-lint 3 0 1.21s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY secretlint yes no 0.85s
✅ YAML yamllint 3 0 0.99s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarification on expected error code when maxAge is absent and device location cannot be determined

1 participant