Skip to content
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.

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

[nrid] Added NRID InterUSS Test #754

Open
maryamer-wing opened this issue Aug 14, 2024 · 1 comment
Open

[nrid] Added NRID InterUSS Test #754

maryamer-wing opened this issue Aug 14, 2024 · 1 comment
Labels
enhancement New feature or request P2 Normal priority

Comments

@maryamer-wing
Copy link

maryamer-wing commented Aug 14, 2024

Please develop InterUSS automated tests that test the functionality of the attached requirements of ASTM F3411.
NRID InterUSS Needs - Summary.pdf

I'm requesting that these tests assess the functionality of Net-RID Service Providers, Net-RID Display Providers, and the Discovery and Synchronization Service (DSS) by evaluating how these components handle data transmission, error reporting, and the provision of Remote ID data, among other key areas. It is crucial that these tests are comprehensive of these requirements to guarantee the system's reliability and effectiveness.

Please feel free to reach out with any questions, comments, or concerns!

@Shastick
Copy link
Contributor

Shastick commented Oct 25, 2024

We've had a look a what needs to be done to cover the requirements present in the aforementioned document. Building new scenarios, or extending existing ones, seems doable in a reasonable time span, with one exception:

NET0620:

If a Net-RID Service Provider is unable to make a UAS operation discoverable
through the creation of an ISA in the DSS, the Net-RID Service Provider shall
(NET0620) notify the operator.

At the moment, there is no existing way in which the qualifier could cause an arbitrary ISA creation by a specific USS to fail. Some ideas have been voiced along the lines of taking the test DSS offline for a short moment, or to have a special endpoint that would trigger failures, but these are mere ideas at the moment.

Hence, we will leave NET0620 aside for the moment, and focus on the rest.

Tracking

We're tracking the efforts for this issue in this document. For anyone wishing to see it, please feel free to request access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P2 Normal priority
Projects
None yet
Development

No branches or pull requests

3 participants