[uss_qualifier] rid net0470 - nominal_behavior: check SP issues notifications to subscribers #891
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Shastick
force-pushed
the
rid-net0740-dp-notif-reception-check
branch
3 times, most recently
from
13e190f to
614bcf6
Compare
…cations to subscribers
Shastick
force-pushed
the
rid-net0740-dp-notif-reception-check
branch
from
614bcf6 to
a18f629
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expand the NominalBehavior scenario to cover NetRID net0470: mock_uss now subscribes for ISA's in the area where the test flight(s) are being created, and will expect to receive notifications from SPs.
We also check for the end-to-end latency between flight injection and the reception of the notification as a proxy for evaluating the timeliness of the SP's actions.
Note that the NET0740 requirement only exists for F3411-v22a. There is no equivalent requirement in the v19 specification, but given than failing to dispatch notifications would be problematic in any case, for v19 we fail checks without requirements with a severity of 'informational'