diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/store_flight_data.md b/monitoring/uss_qualifier/scenarios/astm/netrid/store_flight_data.md index 93b964d680..8c67c845e2 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/store_flight_data.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/store_flight_data.md @@ -2,7 +2,7 @@ ## Overview -This scenario does not perform any checks, but instead writes NetRID flights data to files. This may be useful to see or version-control the output of flight data generation, before it is used in a normal test suite. Or, it may be useful to augment the standard report with exactly the flights data content being used in a normal test suite. +This scenario does not perform any checks, but instead writes NetRID flights data to files.This may be useful to see or version-control the output of flight data generation, before it is used in a normal test suite.Or, it may be useful to augment the standard report with exactly the flights data content being used in a normal test suite. ## Resources diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_expiry.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_expiry.md index 660cf69cf3..cc521cff3f 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_expiry.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_expiry.md @@ -30,11 +30,11 @@ This scenario creates an ISA with a known ID. This step ensures that the ISA doe #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. ## ISA Expiry test case diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_simple.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_simple.md index b6b6aff850..c644173bc0 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_simple.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_simple.md @@ -27,20 +27,20 @@ after its time of applicability. ### Ensure clean workspace test step -This scenario creates an ISA with a known ID. This step ensures that ISA does not exist before the start of the main +This scenario creates an ISA with a known ID.This step ensures that ISA does not exist before the start of the main part of the test. #### Successful ISA query check -While F3411-19 does not explicitly require the implementation of a specific ISA retrieval endpoint, Annex A4 specifies the explicit format for this endpoint. If this format is not followed and the error isn't a 404, this check will fail per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +While F3411-19 does not explicitly require the implementation of a specific ISA retrieval endpoint, Annex A4 specifies the explicit format for this endpoint.If this format is not followed and the error isn't a 404, this check will fail per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. ## Create and check ISA test case @@ -60,11 +60,11 @@ This step attempts to retrieve the previously created ISA from the DSS. If the ISA cannot be queried, the GET ISA DSS endpoint in **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** is likely not implemented correctly. -The DSS returns the ID of the ISA in the response body. If this ID does not match the ID in the resource path, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. +The DSS returns the ID of the ISA in the response body.If this ID does not match the ID in the resource path, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. #### ISA version match check -The DSS returns the version of the ISA in the response body. If this version does not match the version that was returned after creation, and that no modification of the ISA occurred in the meantime, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. +The DSS returns the version of the ISA in the response body.If this version does not match the version that was returned after creation, and that no modification of the ISA occurred in the meantime, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. ## Update and search ISA test case @@ -84,11 +84,11 @@ This step attempts to retrieve at the DSS the ISA just updated. If the ISA cannot be queried, the GET ISA DSS endpoint in **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** is likely not implemented correctly. -The DSS returns the ID of the ISA in the response body. If this ID does not match the ID in the resource path, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. +The DSS returns the ID of the ISA in the response body.If this ID does not match the ID in the resource path, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. #### ISA version match check -The DSS returns the version of the ISA in the response body. If this version does not match the version that was returned after update, and that no modification of the ISA occurred in the meantime, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. +The DSS returns the version of the ISA in the response body.If this version does not match the version that was returned after update, and that no modification of the ISA occurred in the meantime, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. ### [Search by earliest time (included) test step](test_steps/search_isas.md) @@ -96,11 +96,11 @@ This step attempts an ISA search at the DSS with the area of the ISA resource an #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA returned by search check -The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search. If it is not returned, this check will fail. +The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search.If it is not returned, this check will fail. ### [Search by earliest time (excluded) test step](test_steps/search_isas.md) @@ -108,11 +108,11 @@ This step attempts an ISA search at the DSS with the area of the ISA resource an #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA not returned by search check -The ISA search are parameter cover the resource ISA but the earliest time does not, as such the resource ISA that exists at the DSS should not be returned by the search. If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search are parameter cover the resource ISA but the earliest time does not, as such the resource ISA that exists at the DSS should not be returned by the search.If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### [Search by latest time (included) test step](test_steps/search_isas.md) @@ -120,11 +120,11 @@ This step attempts an ISA search at the DSS with the area of the ISA resource an #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA returned by search check -The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search. If it is not returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search.If it is not returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### [Search by latest time (excluded) test step](test_steps/search_isas.md) @@ -132,11 +132,11 @@ This step attempts an ISA search at the DSS with the area of the ISA resource an #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA not returned by search check -The ISA search are parameter cover the resource ISA but the latest time does not, as such the resource ISA that exists at the DSS should not be returned by the search. If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search are parameter cover the resource ISA but the latest time does not, as such the resource ISA that exists at the DSS should not be returned by the search.If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### [Search by area only test step](test_steps/search_isas.md) @@ -144,11 +144,11 @@ This step attempts an ISA search at the DSS with only the area of the ISA resour #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA returned by search check -The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search. If it is not returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search.If it is not returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### Search with invalid params test step @@ -156,7 +156,7 @@ This step attempts an ISA search at the DSS with an empty search area. #### Search request rejected check -The search request contained invalid parameters (empty search area), as such the DSS should reject it with a 400 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The search request contained invalid parameters (empty search area), as such the DSS should reject it with a 400 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### Search by huge area test step @@ -164,7 +164,7 @@ This step attempts an ISA search at the DSS with a too large search area. #### Search request rejected check -The search request contained invalid parameters (too large search area), as such the DSS should reject it with a 413 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The search request contained invalid parameters (too large search area), as such the DSS should reject it with a 413 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### Search ISA with loop test step @@ -172,7 +172,7 @@ This step attempts an ISA search at the DSS with a polygon defining the area tha #### Search request rejected check -The search request contained invalid parameters (area polygon is a loop, which is not allowed), as such the DSS should reject it with a 400 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The search request contained invalid parameters (area polygon is a loop, which is not allowed), as such the DSS should reject it with a 400 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ## Delete ISA test case @@ -182,7 +182,7 @@ This step attempts an ISA deletion with a wrong version. #### Delete request rejected check -The deletion request contained invalid parameters (wrong version), as such the DSS should reject it with a 409 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)**. +The deletion request contained invalid parameters (wrong version), as such the DSS should reject it with a 409 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)**. ### Delete with empty version test step @@ -190,7 +190,7 @@ This step attempts an ISA deletion with an empty version. #### Delete request rejected check -The deletion request contained invalid parameters (empty version), as such the DSS should reject it with a 400 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)**. +The deletion request contained invalid parameters (empty version), as such the DSS should reject it with a 400 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)**. ### [Delete ISA test step](test_steps/delete_isa.md) @@ -206,7 +206,7 @@ This step attempts to retrieve at the DSS the ISA just deleted. #### ISA not found check -The ISA fetch request was about a deleted ISA, as such the DSS should reject it with a 404 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA fetch request was about a deleted ISA, as such the DSS should reject it with a 404 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### [Search ISA test step](test_steps/search_isas.md) @@ -214,11 +214,11 @@ This step attempts an ISA search at the DSS with only the area of the ISA resour #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA not returned by search check -The ISA search are parameter cover the resource ISA, but it has been previously deleted, as such the ISA should not be returned by the search. If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search are parameter cover the resource ISA, but it has been previously deleted, as such the ISA should not be returned by the search.If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ## Cleanup diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_subscription_interactions.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_subscription_interactions.md index 6b66615868..73270844da 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_subscription_interactions.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_subscription_interactions.md @@ -32,11 +32,11 @@ Any previously created subscriptions for the test ISA's area that might still ex #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,d](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,d](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. #### Successful subscription search query check @@ -52,14 +52,14 @@ This test case will do the following, using the DSS being tested: 1. Create an ISA with the configured footprint, 2. Create a subscription for the ISA's area, and expect: - - to find the created ISA mentioned in the reply - - the notification index of the subscription to be 0 + - to find the created ISA mentioned in the reply + - the notification index of the subscription to be 0 3. Modify the ISA, and expect: - - to find the created subscription in the reply - - the notification index of the subscription to be greater than 0 + - to find the created subscription in the reply + - the notification index of the subscription to be greater than 0 4. Delete the ISA, and expect: - - to find the created subscription in the reply - - the notification index of the subscription to be greater than it was after the mutation + - to find the created subscription in the reply + - the notification index of the subscription to be greater than it was after the mutation 5. Delete the subscription. ### ISA Subscription Interactions test step @@ -120,7 +120,7 @@ Failure to do so means that the DSS is not properly implementing **[astm.f3411.v #### Notified subscriber check -Notifications to any subscriber to the created ISA need to be successful. If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. +Notifications to any subscriber to the created ISA need to be successful.If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. ## Cleanup @@ -133,11 +133,11 @@ also deleting any subscription it might have created for the ISA's area. #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,d](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,d](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. #### Successful subscription search query check diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_validation.md index d348fb171c..8f554aa9ec 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_validation.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_validation.md @@ -27,7 +27,7 @@ after its time of applicability. ### Ensure clean workspace test step -This scenario creates an ISA with a known ID. This step ensures that ISA does not exist before the start of the main +This scenario creates an ISA with a known ID.This step ensures that ISA does not exist before the start of the main part of the test. #### Successful ISA query check @@ -36,11 +36,11 @@ part of the test. #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. ## ISA Validation test case diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/subscription_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/subscription_validation.md index c4dbf8e447..fc91170c5c 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/subscription_validation.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/subscription_validation.md @@ -22,7 +22,7 @@ Perform basic operations on a single DSS instance to create subscriptions and ch ### Ensure clean workspace test step -This step ensures that we remove any subscription that may already exist for the service area. First, the DSS is queried for any applicable existing subscriptions, and then any subscriptions found are deleted. +This step ensures that we remove any subscription that may already exist for the service area.First, the DSS is queried for any applicable existing subscriptions, and then any subscriptions found are deleted. #### Successful subscription search query check diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/delete_isa.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/delete_isa.md index 3047262f19..9589945f74 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/delete_isa.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/delete_isa.md @@ -5,12 +5,12 @@ See `DSSWrapper.del_isa` in [`dss_wrapper.py`](../../../dss_wrapper.py). ## ISA response format check -The API for **[astm.f3411.v19.DSS0030,b](../../../../../../requirements/astm/f3411/v19.md)** specifies an explicit format that the DSS responses must follow. If the DSS response does not validate against this format, this check will fail. +The API for **[astm.f3411.v19.DSS0030,b](../../../../../../requirements/astm/f3411/v19.md)** specifies an explicit format that the DSS responses must follow.If the DSS response does not validate against this format, this check will fail. ## ISA ID matches check -When the ISA is deleted, the DSS returns the ID of the ISA in the response body. If this ID does not match the ID in the resource path, **[astm.f3411.v19.DSS0030,b](../../../../../../requirements/astm/f3411/v19.md)** was not implemented correctly and this check will fail. +When the ISA is deleted, the DSS returns the ID of the ISA in the response body.If this ID does not match the ID in the resource path, **[astm.f3411.v19.DSS0030,b](../../../../../../requirements/astm/f3411/v19.md)** was not implemented correctly and this check will fail. ## ISA version matches check -When the ISA is deleted, the DSS returns the version of the ISA in the response body. If this version does not match the version in the resource path, **[astm.f3411.v19.DSS0030,b](../../../../../../requirements/astm/f3411/v19.md)** was not implemented correctly and this check will fail. +When the ISA is deleted, the DSS returns the version of the ISA in the response body.If this version does not match the version in the resource path, **[astm.f3411.v19.DSS0030,b](../../../../../../requirements/astm/f3411/v19.md)** was not implemented correctly and this check will fail. diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/put_isa.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/put_isa.md index 57bd29e228..a3037d07fe 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/put_isa.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/put_isa.md @@ -9,28 +9,28 @@ The API for **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f34 ## ISA response format check -The API for **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** specifies an explicit format that the DSS responses must follow. If the DSS response does not validate against this format, this check will fail. +The API for **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** specifies an explicit format that the DSS responses must follow.If the DSS response does not validate against this format, this check will fail. ## ISA ID matches check -When the ISA is created, the DSS returns the ID of the ISA in the response body. If this ID does not match the ID in the resource path, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** was not implemented correctly and this check will fail. +When the ISA is created, the DSS returns the ID of the ISA in the response body.If this ID does not match the ID in the resource path, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** was not implemented correctly and this check will fail. ## ISA version changed check -When the ISA is updated, the DSS returns the updated version of the ISA in the response body. If this version remains the same as the one before the update, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** was not implemented correctly and this check will fail. +When the ISA is updated, the DSS returns the updated version of the ISA in the response body.If this version remains the same as the one before the update, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** was not implemented correctly and this check will fail. ## ISA version format check -Because the ISA version must be used in URLs, it must be URL-safe even though the ASTM standards do not explicitly require this. If the indicated ISA version is not URL-safe, this check will fail. +Because the ISA version must be used in URLs, it must be URL-safe even though the ASTM standards do not explicitly require this.If the indicated ISA version is not URL-safe, this check will fail. ## ISA start time matches check -The ISA creation request specified an exact start time slightly past now, so the DSS should have created an ISA starting at exactly that time. If the DSS response indicates the ISA start time is not this value, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** is not implemented correctly and this check will fail. +The ISA creation request specified an exact start time slightly past now, so the DSS should have created an ISA starting at exactly that time.If the DSS response indicates the ISA start time is not this value, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** is not implemented correctly and this check will fail. ## ISA end time matches check -The ISA creation request specified an exact end time, so the DSS should have created an ISA ending at exactly that time. If the DSS response indicates the ISA end time is not this value, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** is not implemented correctly and this check will fail. +The ISA creation request specified an exact end time, so the DSS should have created an ISA ending at exactly that time.If the DSS response indicates the ISA end time is not this value, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** is not implemented correctly and this check will fail. ## ISA URL matches check -When the ISA is created, the DSS returns the URL of the ISA in the response body. If this URL does not match the URL requested, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** is not implemented correctly and this check will fail. +When the ISA is created, the DSS returns the URL of the ISA in the response body.If this URL does not match the URL requested, **[astm.f3411.v19.DSS0030,a](../../../../../../requirements/astm/f3411/v19.md)** is not implemented correctly and this check will fail. diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/search_isas.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/search_isas.md index 0103964533..5c202871b7 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/search_isas.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/test_steps/search_isas.md @@ -5,4 +5,4 @@ See `DSSWrapper.search_isa` in [`dss_wrapper.py`](../../../dss_wrapper.py). ## ISAs search response format check -While F3411-19 does not explicitly require the implementation of the ISA search endpoint, Annex A4 specifies the explicit format for this endpoint. If this format is not followed, this check will fail per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +While F3411-19 does not explicitly require the implementation of the ISA search endpoint, Annex A4 specifies the explicit format for this endpoint.If this format is not followed, this check will fail per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../../requirements/interuss/f3411/dss_endpoints.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/token_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/token_validation.md index f8af0ef184..4451e2a21c 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/token_validation.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/token_validation.md @@ -22,20 +22,20 @@ Checks that the DSS properly validates the provided client token on all its endp ### Ensure clean workspace test step -This scenario creates an ISA with a known ID. This step ensures that ISA does not exist before the start of the main +This scenario creates an ISA with a known ID.This step ensures that ISA does not exist before the start of the main part of the test. #### Successful ISA query check -While F3411-19 does not explicitly require the implementation of a specific ISA retrieval endpoint, Annex A4 specifies the explicit format for this endpoint. If this format is not followed and the error isn't a 404, this check will fail per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +While F3411-19 does not explicitly require the implementation of a specific ISA retrieval endpoint, Annex A4 specifies the explicit format for this endpoint.If this format is not followed and the error isn't a 404, this check will fail per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v19.NET0730](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the POST ISAs endpoint isn't met. ## Token validation test case diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss_interoperability.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss_interoperability.md index 0c42bf65a8..455fc3c8b3 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss_interoperability.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss_interoperability.md @@ -3,10 +3,10 @@ ## Overview The test scenario in this folder verifies that two DSS instances implementing -the API required by ASTM F3411-19 in a shared DSS region interoperate -correctly. This is generally accomplished by performing an operation on one -DSS instance and then verifying that the results are visible in the other -instance. Neither of the two DSS instances need to be an InterUSS Platform +the API required by ASTM F3411-19 in a shared DSS regioninteroperate +correctly.This is generally accomplished by performing anoperation on one +DSS instance and then verifying that the results are visiblein the other +instance.Neither of the two DSS instances need to be an InterUSS Platform implementation. ## Resources @@ -21,20 +21,20 @@ A resources.astm.f3411.DSSInstancesResource containing at least two DSS instance ## Test sequence legend -* *P*: Primary DSS instance under test. The sequence below is - intended to be repeated so that each DSS is the primary DSS under test for one - iteration of the sequence. +* *P*: Primary DSS instance under test.The sequence below is +intended to be repeated so that each DSS is the primary DSS under test for one +iteration of the sequence. * *n*: Each of the other (non-Primary) DSS instances. * ISA[*id*]: Reference to Identification Service Area with a particular test id - (test id index, not full UUID identifier). Note that the same UUID should be - used for ISA[i] throughout the sequence even though the logical ISA may be - created and deleted multiple times. +(test id index, not full UUID identifier).Note that the same UUID should be +used for ISA[i] throughout the sequence even though the logical ISA may be +created and deleted multiple times. * Subscription[*id*]: Reference to Subscription with a particular test *id* - (test id index, not full UUID identifier). Note that the same UUID should be - used for Subscription[i] throughout the sequence even though the logical - Subscription may be created and deleted multiple times. +(test id index, not full UUID identifier).Note that the same UUID should be +used for Subscription[i] throughout the sequence even though the logical +Subscription may be created and deleted multiple times. * D: Number of seconds needed to process requests to all DSS instances before - the note to wait >D seconds from a particular time +the note to wait >D seconds from a particular time ## Sequence diagram diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/misbehavior.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/misbehavior.md index af43f8b57f..9a11fbbc5e 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/misbehavior.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/misbehavior.md @@ -26,7 +26,7 @@ A [`DSSInstanceResource`](../../../../resources/astm/f3411/dss.py) is required f ### Injection test step -In this step, uss_qualifier injects a single nominal flight into each SP under test, usually with a start time in the future. Each SP is expected to queue the provided telemetry and later simulate that telemetry coming from an aircraft at the designated timestamps. +In this step, uss_qualifier injects a single nominal flight into each SP under test, usually with a start time in the future.Each SP is expected to queue the provided telemetry and later simulate that telemetry coming from an aircraft at the designated timestamps. #### Successful injection check @@ -37,7 +37,7 @@ This check will fail if the flight was not successfully injected. #### Identifiable flights check -This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights. This should generally be achieved by injecting appropriate data. +This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights.This should generally be achieved by injecting appropriate data. ### Unauthenticated requests test step diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/nominal_behavior.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/nominal_behavior.md index c39e680f2d..f54a595060 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/nominal_behavior.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/nominal_behavior.md @@ -2,7 +2,7 @@ ## Overview -In this scenario, a single nominal flight is injected into each NetRID Service Provider (SP) under test. Each of the injected flights is expected to be visible to all the observers at appropriate times and for appropriate requests. +In this scenario, a single nominal flight is injected into each NetRID Service Provider (SP) under test.Each of the injected flights is expected to be visible to all the observers at appropriate times and for appropriate requests. ## Resources @@ -12,11 +12,11 @@ A [`FlightDataResource`](../../../../resources/netrid/flight_data.py) containing ### service_providers -A set of [`NetRIDServiceProviders`](../../../../resources/netrid/service_providers.py) to be tested via the injection of RID flight data. This scenario requires at least one SP under test. +A set of [`NetRIDServiceProviders`](../../../../resources/netrid/service_providers.py) to be tested via the injection of RID flight data.This scenario requires at least one SP under test. ### observers -A set of [`NetRIDObserversResource`](../../../../resources/netrid/observers.py) to be tested via checking their observations of the NetRID system and comparing the observations against expectations. An observer generally represents a "Display Application", in ASTM F3411 terminology. This scenario requires at least one observer. +A set of [`NetRIDObserversResource`](../../../../resources/netrid/observers.py) to be tested via checking their observations of the NetRID system and comparing the observations against expectations.An observer generally represents a "Display Application", in ASTM F3411 terminology.This scenario requires at least one observer. ### evaluation_configuration @@ -30,7 +30,7 @@ If specified, uss_qualifier will act as a Display Provider and check a DSS insta ### Injection test step -In this step, uss_qualifier injects a single nominal flight into each SP under test, usually with a start time in the future. Each SP is expected to queue the provided telemetry and later simulate that telemetry coming from an aircraft at the designated timestamps. +In this step, uss_qualifier injects a single nominal flight into each SP under test, usually with a start time in the future.Each SP is expected to queue the provided telemetry and later simulate that telemetry coming from an aircraft at the designated timestamps. #### Successful injection check @@ -43,12 +43,12 @@ This check will fail if the flight was not successfully injected. TODO: Validate injected flights, especially to make sure they contain the specified injection IDs -Per **[interuss.automated_testing.rid.injection.UpsertTestResult](../../../../requirements/interuss/automated_testing/rid/injection.md)**, the NetRID Service Provider under test should only make valid modifications to the injected flights. This includes: +Per **[interuss.automated_testing.rid.injection.UpsertTestResult](../../../../requirements/interuss/automated_testing/rid/injection.md)**, the NetRID Service Provider under test should only make valid modifications to the injected flights.This includes: * A flight with the specified injection ID must be returned. #### Identifiable flights check -This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights. This should generally be achieved by injecting appropriate data. +This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights.This should generally be achieved by injecting appropriate data. ### Service Provider polling test step @@ -66,35 +66,35 @@ This implies that any recent position outside the area must be either preceded o #### Flights data format check -**[astm.f3411.v19.NET0710,1](../../../../requirements/astm/f3411/v19.md)** and **[astm.f3411.v19.NET0340](../../../../requirements/astm/f3411/v19.md)** require a Service Provider to implement the P2P portion of the OpenAPI specification. This check will fail if the response to the /flights endpoint does not validate against the OpenAPI-specified schema. +**[astm.f3411.v19.NET0710,1](../../../../requirements/astm/f3411/v19.md)** and **[astm.f3411.v19.NET0340](../../../../requirements/astm/f3411/v19.md)** require a Service Provider to implement the P2P portion of the OpenAPI specification.This check will fail if the response to the /flights endpoint does not validate against the OpenAPI-specified schema. #### ISA query check -**[interuss.f3411.dss_endpoints.SearchISAs](../../../../requirements/interuss/f3411/dss_endpoints.md)** requires a USS providing a DSS instance to implement the DSS endpoints of the OpenAPI specification. If uss_qualifier is unable to query the DSS for ISAs, this check will fail. +**[interuss.f3411.dss_endpoints.SearchISAs](../../../../requirements/interuss/f3411/dss_endpoints.md)** requires a USS providing a DSS instance to implement the DSS endpoints of the OpenAPI specification.If uss_qualifier is unable to query the DSS for ISAs, this check will fail. #### Premature flight check -The timestamps of the injected telemetry usually start in the future. If a flight with injected telemetry only in the future is observed prior to the timestamp of the first telemetry point, this check will fail because the SP does not satisfy **[interuss.automated_testing.rid.injection.ExpectedBehavior](../../../../requirements/interuss/automated_testing/rid/injection.md)**. +The timestamps of the injected telemetry usually start in the future.If a flight with injected telemetry only in the future is observed prior to the timestamp of the first telemetry point, this check will fail because the SP does not satisfy **[interuss.automated_testing.rid.injection.ExpectedBehavior](../../../../requirements/interuss/automated_testing/rid/injection.md)**. #### Missing flight check -**[astm.f3411.v19.NET0610](../../../../requirements/astm/f3411/v19.md)** requires that SPs make all UAS operations discoverable over the duration of the flight plus *NetMaxNearRealTimeDataPeriod*, so each injected flight should be observable during this time. If a flight is not observed during its appropriate time period, this check will fail. +**[astm.f3411.v19.NET0610](../../../../requirements/astm/f3411/v19.md)** requires that SPs make all UAS operations discoverable over the duration of the flight plus *NetMaxNearRealTimeDataPeriod*, so each injected flight should be observable during this time.If a flight is not observed during its appropriate time period, this check will fail. -**[astm.f3411.v19.NET0710,1](../../../../requirements/astm/f3411/v19.md)** and **[astm.f3411.v19.NET0340](../../../../requirements/astm/f3411/v19.md)** require a Service Provider to implement the GET flights endpoint. This check will also fail if uss_qualifier cannot query that endpoint (specified in the ISA present in the DSS) successfully. +**[astm.f3411.v19.NET0710,1](../../../../requirements/astm/f3411/v19.md)** and **[astm.f3411.v19.NET0340](../../../../requirements/astm/f3411/v19.md)** require a Service Provider to implement the GET flights endpoint.This check will also fail if uss_qualifier cannot query that endpoint (specified in the ISA present in the DSS) successfully. -The identity of flights is determined by precisely matching the known injected positions. If the flight can be found, the USS may not have met **[astm.f3411.v19.NET0260,Table1,9](../../../../requirements/astm/f3411/v19.md)** or **[astm.f3411.v19.NET0260,Table1,10](../../../../requirements/astm/f3411/v19.md)** prescribing provision of position data consistent with the common data dictionary. +The identity of flights is determined by precisely matching the known injected positions.If the flight can be found, the USS may not have met **[astm.f3411.v19.NET0260,Table1,9](../../../../requirements/astm/f3411/v19.md)** or **[astm.f3411.v19.NET0260,Table1,10](../../../../requirements/astm/f3411/v19.md)** prescribing provision of position data consistent with the common data dictionary. #### Service Provider altitude check -**[astm.f3411.v19.NET0260,Table1,11](../../../../requirements/astm/f3411/v19.md)** requires that relevant Remote ID data, consistent with the common data dictionary, be reported by the Service Provider. Injected flight data had known altitudes, but the altitude reported by the Service Provider did not match those known altitudes. +**[astm.f3411.v19.NET0260,Table1,11](../../../../requirements/astm/f3411/v19.md)** requires that relevant Remote ID data, consistent with the common data dictionary, be reported by the Service Provider.Injected flight data had known altitudes, but the altitude reported by the Service Provider did not match those known altitudes. #### Successful flight details query check -**[astm.f3411.v19.NET0710,2](../../../../requirements/astm/f3411/v19.md)** and **[astm.f3411.v19.NET0340](../../../../requirements/astm/f3411/v19.md)** require a Service Provider to implement the GET flight details endpoint. This check will fail if uss_qualifier cannot query that endpoint (specified in the ISA present in the DSS) successfully. +**[astm.f3411.v19.NET0710,2](../../../../requirements/astm/f3411/v19.md)** and **[astm.f3411.v19.NET0340](../../../../requirements/astm/f3411/v19.md)** require a Service Provider to implement the GET flight details endpoint.This check will fail if uss_qualifier cannot query that endpoint (specified in the ISA present in the DSS) successfully. #### Flight details data format check -**[astm.f3411.v19.NET0710,2](../../../../requirements/astm/f3411/v19.md)** and **[astm.f3411.v19.NET0340](../../../../requirements/astm/f3411/v19.md)** require a Service Provider to implement the P2P portion of the OpenAPI specification. This check will fail if the response to the flight details endpoint does not validate against the OpenAPI-specified schema. +**[astm.f3411.v19.NET0710,2](../../../../requirements/astm/f3411/v19.md)** and **[astm.f3411.v19.NET0340](../../../../requirements/astm/f3411/v19.md)** require a Service Provider to implement the P2P portion of the OpenAPI specification.This check will fail if the response to the flight details endpoint does not validate against the OpenAPI-specified schema. #### Lingering flight check @@ -102,11 +102,11 @@ The identity of flights is determined by precisely matching the known injected p #### Area too large check -**[astm.f3411.v19.NET0430](../../../../requirements/astm/f3411/v19.md)** requires that a NetRID Display Provider rejects a request for a very large view area with a diagonal greater than *NetMaxDisplayAreaDiagonal*. If such a large view is requested and a 413 error code is not received, then this check will fail. +**[astm.f3411.v19.NET0430](../../../../requirements/astm/f3411/v19.md)** requires that a NetRID Display Provider rejects a request for a very large view area with a diagonal greater than *NetMaxDisplayAreaDiagonal*.If such a large view is requested and a 413 error code is not received, then this check will fail. ### Observer polling test step -In this step, all observers are queried for the flights they observe. Based on the known flights that were injected into the SPs in the first step, these observations are checked against expected behavior/data. Observation rectangles are chosen to encompass the known flights when possible. +In this step, all observers are queried for the flights they observe.Based on the known flights that were injected into the SPs in the first step, these observations are checked against expected behavior/data.Observation rectangles are chosen to encompass the known flights when possible. #### Successful observation check @@ -118,11 +118,11 @@ Per **[interuss.automated_testing.rid.observation.UniqueFlights](../../../../req #### Premature flight check -The timestamps of the injected telemetry usually start in the future. If a flight with injected telemetry only in the future is observed prior to the timestamp of the first telemetry point, this check will fail because the SP does not satisfy **[interuss.automated_testing.rid.injection.ExpectedBehavior](../../../../requirements/interuss/automated_testing/rid/injection.md)**. +The timestamps of the injected telemetry usually start in the future.If a flight with injected telemetry only in the future is observed prior to the timestamp of the first telemetry point, this check will fail because the SP does not satisfy **[interuss.automated_testing.rid.injection.ExpectedBehavior](../../../../requirements/interuss/automated_testing/rid/injection.md)**. #### Missing flight check -**[astm.f3411.v19.NET0610](../../../../requirements/astm/f3411/v19.md)** require that SPs make all UAS operations discoverable over the duration of the flight plus *NetMaxNearRealTimeDataPeriod*, so each injected flight should be observable during this time. If one of the flights is not observed during its appropriate time period, this check will fail. +**[astm.f3411.v19.NET0610](../../../../requirements/astm/f3411/v19.md)** require that SPs make all UAS operations discoverable over the duration of the flight plus *NetMaxNearRealTimeDataPeriod*, so each injected flight should be observable during this time.If one of the flights is not observed during its appropriate time period, this check will fail. #### Lingering flight check @@ -142,7 +142,7 @@ If the observed altitude of a flight does not match the altitude of the injected #### Area too large check -**[astm.f3411.v19.NET0430](../../../../requirements/astm/f3411/v19.md)** require that a NetRID Display Provider reject a request for a very large view area with a diagonal greater than *NetMaxDisplayAreaDiagonal*. If such a large view is requested and a 413 error code is not received, then this check will fail. +**[astm.f3411.v19.NET0430](../../../../requirements/astm/f3411/v19.md)** require that a NetRID Display Provider reject a request for a very large view area with a diagonal greater than *NetMaxDisplayAreaDiagonal*.If such a large view is requested and a 413 error code is not received, then this check will fail. #### Minimal obfuscation distance of individual flights check diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/operator_interactions.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/operator_interactions.md index 13b9ba0a17..c82eb25100 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/operator_interactions.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/operator_interactions.md @@ -24,7 +24,7 @@ TODO: Create this resource ### flights_data -A [`FlightDataResource`](../../../../resources/netrid/flight_data.py) containing 1 flight. This flight must: +A [`FlightDataResource`](../../../../resources/netrid/flight_data.py) containing 1 flight.This flight must: * (Phase 1): Start out nominal * (Phase 2): Then contain a pause (lack of telemetry) sufficient to trigger NET0040 * (Phase 3): Then resume nominal telemetry @@ -40,7 +40,7 @@ TODO: Create this resource ### Verify no ISAs test step -uss_qualifier checks the DSS to ensure that the Service Provider under test does not have any ISAs in the system. If ISAs are present, the Service Provider is instructed to clear the area of active flights, after which uss_qualifier reverifies the absence of ISAs. +uss_qualifier checks the DSS to ensure that the Service Provider under test does not have any ISAs in the system.If ISAs are present, the Service Provider is instructed to clear the area of active flights, after which uss_qualifier reverifies the absence of ISAs. ### Disable DSS test step @@ -66,7 +66,7 @@ uss_qualifier retrieves the current (after failed flight) set of operator notifi #### Operator notified of discoverability failure check -The "after" set of operator notifications should contain at least one more entry than the "before" set of operator notifications. If there was no new operator notification, the Service Provider will not have met **[astm.f3411.v19.NET0620](../../../../requirements/astm/f3411/v19.md)**. +The "after" set of operator notifications should contain at least one more entry than the "before" set of operator notifications.If there was no new operator notification, the Service Provider will not have met **[astm.f3411.v19.NET0620](../../../../requirements/astm/f3411/v19.md)**. TODO: Implement diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_expiry.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_expiry.md index e02761ff56..bc830f6752 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_expiry.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_expiry.md @@ -30,11 +30,11 @@ This scenario creates an ISA with a known ID. This step ensures that the ISA doe #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. ## ISA Expiry test case diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_simple.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_simple.md index d0988648cd..9f2d3496cc 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_simple.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_simple.md @@ -27,20 +27,20 @@ after its time of applicability. ### Ensure clean workspace test step -This scenario creates an ISA with a known ID. This step ensures that ISA does not exist before the start of the main +This scenario creates an ISA with a known ID.This step ensures that ISA does not exist before the start of the main part of the test. #### Successful ISA query check -While F3411-22a does not explicitly require the implementation of a specific ISA retrieval endpoint, Annex A4 specifies the explicit format for this endpoint. If this format is not followed and the error isn't a 404, this check will fail per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +While F3411-22a does not explicitly require the implementation of a specific ISA retrieval endpoint, Annex A4 specifies the explicit format for this endpoint.If this format is not followed and the error isn't a 404, this check will fail per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** and **[astm.f3411.v22a.NET0340](../../../../../requirements/astm/f3411/v22a.md)** requirements to implement the POST ISAs endpoint aren't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** and **[astm.f3411.v22a.NET0340](../../../../../requirements/astm/f3411/v22a.md)** requirements to implement the POST ISAs endpoint aren't met. ## Create and check ISA test case @@ -60,11 +60,11 @@ This step attempts to retrieve the previously created ISA from the DSS. If the ISA cannot be queried, the GET ISA DSS endpoint in **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** is likely not implemented correctly. -The DSS returns the ID of the ISA in the response body. If this ID does not match the ID in the resource path, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. +The DSS returns the ID of the ISA in the response body.If this ID does not match the ID in the resource path, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. #### ISA version match check -The DSS returns the version of the ISA in the response body. If this version does not match the version that was returned after creation, and that no modification of the ISA occurred in the meantime, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. +The DSS returns the version of the ISA in the response body.If this version does not match the version that was returned after creation, and that no modification of the ISA occurred in the meantime, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. ## Update and search ISA test case @@ -84,11 +84,11 @@ This step attempts to retrieve at the DSS the ISA just updated. If the ISA cannot be queried, the GET ISA DSS endpoint in **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** is likely not implemented correctly. -The DSS returns the ID of the ISA in the response body. If this ID does not match the ID in the resource path, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. +The DSS returns the ID of the ISA in the response body.If this ID does not match the ID in the resource path, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. #### ISA version match check -The DSS returns the version of the ISA in the response body. If this version does not match the version that was returned after update, and that no modification of the ISA occurred in the meantime, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. +The DSS returns the version of the ISA in the response body.If this version does not match the version that was returned after update, and that no modification of the ISA occurred in the meantime, **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** was not implemented correctly and this check will fail. ### [Search by earliest time (included) test step](test_steps/search_isas.md) @@ -96,11 +96,11 @@ This step attempts an ISA search at the DSS with the area of the ISA resource an #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA returned by search check -The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search. If it is not returned, this check will fail. +The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search.If it is not returned, this check will fail. ### [Search by earliest time (excluded) test step](test_steps/search_isas.md) @@ -108,11 +108,11 @@ This step attempts an ISA search at the DSS with the area of the ISA resource an #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA not returned by search check -The ISA search are parameter cover the resource ISA but the earliest time does not, as such the resource ISA that exists at the DSS should not be returned by the search. If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search are parameter cover the resource ISA but the earliest time does not, as such the resource ISA that exists at the DSS should not be returned by the search.If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### [Search by latest time (included) test step](test_steps/search_isas.md) @@ -120,11 +120,11 @@ This step attempts an ISA search at the DSS with the area of the ISA resource an #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA returned by search check -The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search. If it is not returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search.If it is not returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### [Search by latest time (excluded) test step](test_steps/search_isas.md) @@ -132,11 +132,11 @@ This step attempts an ISA search at the DSS with the area of the ISA resource an #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA not returned by search check -The ISA search are parameter cover the resource ISA but the latest time does not, as such the resource ISA that exists at the DSS should not be returned by the search. If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search are parameter cover the resource ISA but the latest time does not, as such the resource ISA that exists at the DSS should not be returned by the search.If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### [Search by area only test step](test_steps/search_isas.md) @@ -144,11 +144,11 @@ This step attempts an ISA search at the DSS with only the area of the ISA resour #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA returned by search check -The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search. If it is not returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters cover the resource ISA, as such the resource ISA that exists at the DSS should be returned by the search.If it is not returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### Search with invalid params test step @@ -156,7 +156,7 @@ This step attempts an ISA search at the DSS with an empty search area. #### Search request rejected check -The search request contained invalid parameters (empty search area), as such the DSS should reject it with a 400 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The search request contained invalid parameters (empty search area), as such the DSS should reject it with a 400 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### Search by huge area test step @@ -164,7 +164,7 @@ This step attempts an ISA search at the DSS with a too large search area. #### Search request rejected check -The search request contained invalid parameters (too large search area), as such the DSS should reject it with a 413 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The search request contained invalid parameters (too large search area), as such the DSS should reject it with a 413 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### Search ISA with loop test step @@ -172,7 +172,7 @@ This step attempts an ISA search at the DSS with a polygon defining the area tha #### Search request rejected check -The search request contained invalid parameters (area polygon is a loop, which is not allowed), as such the DSS should reject it with a 400 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The search request contained invalid parameters (area polygon is a loop, which is not allowed), as such the DSS should reject it with a 400 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ## Delete ISA test case @@ -182,7 +182,7 @@ This step attempts an ISA deletion with a wrong version. #### Delete request rejected check -The deletion request contained invalid parameters (wrong version), as such the DSS should reject it with a 409 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)**. +The deletion request contained invalid parameters (wrong version), as such the DSS should reject it with a 409 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)**. ### Delete with empty version test step @@ -190,7 +190,7 @@ This step attempts an ISA deletion with an empty version. #### Delete request rejected check -The deletion request contained invalid parameters (empty version), as such the DSS should reject it with a 400 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)**. +The deletion request contained invalid parameters (empty version), as such the DSS should reject it with a 400 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)**. ### [Delete ISA test step](test_steps/delete_isa.md) @@ -206,7 +206,7 @@ This step attempts to retrieve at the DSS the ISA just deleted. #### ISA not found check -The ISA fetch request was about a deleted ISA, as such the DSS should reject it with a 404 HTTP code. If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA fetch request was about a deleted ISA, as such the DSS should reject it with a 404 HTTP code.If the DSS responds successfully to this request, or if it rejected with an incorrect HTTP code, this check will fail as per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ### [Search ISA test step](test_steps/search_isas.md) @@ -214,11 +214,11 @@ This step attempts an ISA search at the DSS with only the area of the ISA resour #### Successful ISAs search check -The ISA search parameters are valid, as such the search should be successful. If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search parameters are valid, as such the search should be successful.If the request is not successful, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### ISA not returned by search check -The ISA search are parameter cover the resource ISA, but it has been previously deleted, as such the ISA should not be returned by the search. If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +The ISA search are parameter cover the resource ISA, but it has been previously deleted, as such the ISA should not be returned by the search.If it is returned, this check will fail as per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. ## Cleanup diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_subscription_interactions.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_subscription_interactions.md index 526545c24a..60d63fac7e 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_subscription_interactions.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_subscription_interactions.md @@ -32,11 +32,11 @@ Any previously created subscriptions for the test ISA's area that might still ex #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,d](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,d](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. #### Successful subscription search query check @@ -52,14 +52,14 @@ This test case will do the following, using the DSS being tested: 1. Create an ISA with the configured footprint, 2. Create a subscription for the ISA's area, and expect: - - to find the created ISA mentioned in the reply - - the notification index of the subscription to be 0 + - to find the created ISA mentioned in the reply + - the notification index of the subscription to be 0 3. Modify the ISA, and expect: - - to find the created subscription in the reply - - the notification index of the subscription to be greater than 0 + - to find the created subscription in the reply + - the notification index of the subscription to be greater than 0 4. Delete the ISA, and expect: - - to find the created subscription in the reply - - the notification index of the subscription to be greater than it was after the mutation + - to find the created subscription in the reply + - the notification index of the subscription to be greater than it was after the mutation 5. Delete the subscription. ### ISA Subscription Interactions test step @@ -120,7 +120,7 @@ Failure to do so means that the DSS is not properly implementing **[astm.f3411.v #### Notified subscriber check -Notifications to any subscriber to the created ISA need to be successful. If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. +Notifications to any subscriber to the created ISA need to be successful.If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. ## Cleanup @@ -133,11 +133,11 @@ also deleting any subscription it might have created for the ISA's area. #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,d](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,d](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. #### Successful subscription search query check diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_validation.md index 2af1539903..ff1a08cbb2 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_validation.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_validation.md @@ -27,7 +27,7 @@ after its time of applicability. ### Ensure clean workspace test step -This scenario creates an ISA with a known ID. This step ensures that ISA does not exist before the start of the main +This scenario creates an ISA with a known ID.This step ensures that ISA does not exist before the start of the main part of the test. #### Successful ISA query check @@ -36,11 +36,11 @@ part of the test. #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. ## ISA Validation test case diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/subscription_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/subscription_validation.md index e3067824b0..fd5d6d434f 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/subscription_validation.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/subscription_validation.md @@ -22,7 +22,7 @@ Perform basic operations on a single DSS instance to create subscriptions and ch ### Ensure clean workspace test step -This step ensures that we remove any subscription that may already exist for the service area. First, the DSS is queried for any applicable existing subscriptions, and then any subscriptions found are deleted. +This step ensures that we remove any subscription that may already exist for the service area.First, the DSS is queried for any applicable existing subscriptions, and then any subscriptions found are deleted. #### Successful subscription search query check diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/delete_isa.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/delete_isa.md index c0c048aa21..b26af8ca99 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/delete_isa.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/delete_isa.md @@ -5,12 +5,12 @@ See `DSSWrapper.del_isa` in [`dss_wrapper.py`](../../../dss_wrapper.py). ## ISA response format check -The API for **[astm.f3411.v22a.DSS0030,b](../../../../../../requirements/astm/f3411/v22a.md)** specifies an explicit format that the DSS responses must follow. If the DSS response does not validate against this format, this check will fail. +The API for **[astm.f3411.v22a.DSS0030,b](../../../../../../requirements/astm/f3411/v22a.md)** specifies an explicit format that the DSS responses must follow.If the DSS response does not validate against this format, this check will fail. ## ISA ID matches check -When the ISA is deleted, the DSS returns the ID of the ISA in the response body. If this ID does not match the ID in the resource path, **[astm.f3411.v22a.DSS0030,b](../../../../../../requirements/astm/f3411/v22a.md)** was not implemented correctly and this check will fail. +When the ISA is deleted, the DSS returns the ID of the ISA in the response body.If this ID does not match the ID in the resource path, **[astm.f3411.v22a.DSS0030,b](../../../../../../requirements/astm/f3411/v22a.md)** was not implemented correctly and this check will fail. ## ISA version matches check -When the ISA is deleted, the DSS returns the version of the ISA in the response body. If this version does not match the version in the resource path, **[astm.f3411.v22a.DSS0030,b](../../../../../../requirements/astm/f3411/v22a.md)** was not implemented correctly and this check will fail. +When the ISA is deleted, the DSS returns the version of the ISA in the response body.If this version does not match the version in the resource path, **[astm.f3411.v22a.DSS0030,b](../../../../../../requirements/astm/f3411/v22a.md)** was not implemented correctly and this check will fail. diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/put_isa.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/put_isa.md index aabd1b6a9c..0a851e3fc8 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/put_isa.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/put_isa.md @@ -9,28 +9,28 @@ The API for **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3 ## ISA response format check -The API for **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** specifies an explicit format that the DSS responses must follow. If the DSS response does not validate against this format, this check will fail. +The API for **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** specifies an explicit format that the DSS responses must follow.If the DSS response does not validate against this format, this check will fail. ## ISA ID matches check -When the ISA is created, the DSS returns the ID of the ISA in the response body. If this ID does not match the ID in the resource path, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** was not implemented correctly and this check will fail. +When the ISA is created, the DSS returns the ID of the ISA in the response body.If this ID does not match the ID in the resource path, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** was not implemented correctly and this check will fail. ## ISA version changed check -When the ISA is updated, the DSS returns the updated version of the ISA in the response body. If this version remains the same as the one before the update, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** was not implemented correctly and this check will fail. +When the ISA is updated, the DSS returns the updated version of the ISA in the response body.If this version remains the same as the one before the update, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** was not implemented correctly and this check will fail. ## ISA version format check -Because the ISA version must be used in URLs, it must be URL-safe even though the ASTM standards do not explicitly require this. If the indicated ISA version is not URL-safe, this check will fail. +Because the ISA version must be used in URLs, it must be URL-safe even though the ASTM standards do not explicitly require this.If the indicated ISA version is not URL-safe, this check will fail. ## ISA start time matches check -The ISA creation request specified an exact start time slightly past now, so the DSS should have created an ISA starting at exactly that time. If the DSS response indicates the ISA start time is not this value, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** is not implemented correctly and this check will fail. +The ISA creation request specified an exact start time slightly past now, so the DSS should have created an ISA starting at exactly that time.If the DSS response indicates the ISA start time is not this value, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** is not implemented correctly and this check will fail. ## ISA end time matches check -The ISA creation request specified an exact end time, so the DSS should have created an ISA ending at exactly that time. If the DSS response indicates the ISA end time is not this value, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** is not implemented correctly and this check will fail. +The ISA creation request specified an exact end time, so the DSS should have created an ISA ending at exactly that time.If the DSS response indicates the ISA end time is not this value, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** is not implemented correctly and this check will fail. ## ISA URL matches check -When the ISA is created, the DSS returns the URL of the ISA in the response body. If this URL does not match the URL requested, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** is not implemented correctly and this check will fail. +When the ISA is created, the DSS returns the URL of the ISA in the response body.If this URL does not match the URL requested, **[astm.f3411.v22a.DSS0030,a](../../../../../../requirements/astm/f3411/v22a.md)** is not implemented correctly and this check will fail. diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/search_isas.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/search_isas.md index 5f50e1b067..795aeb2da5 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/search_isas.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/test_steps/search_isas.md @@ -5,4 +5,4 @@ See `DSSWrapper.search_isa` in [`dss_wrapper.py`](../../../dss_wrapper.py). ## ISAs search response format check -While F3411-22a does not explicitly require the implementation of the ISA search endpoint, Annex A4 specifies the explicit format for this endpoint. If this format is not followed, this check will fail per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +While F3411-22a does not explicitly require the implementation of the ISA search endpoint, Annex A4 specifies the explicit format for this endpoint.If this format is not followed, this check will fail per **[interuss.f3411.dss_endpoints.SearchISAs](../../../../../../requirements/interuss/f3411/dss_endpoints.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/token_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/token_validation.md index 7bf9e15a98..e62e26eb8d 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/token_validation.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/token_validation.md @@ -22,20 +22,20 @@ Checks that the DSS properly validates the provided client token on all its endp ### Ensure clean workspace test step -This scenario creates an ISA with a known ID. This step ensures that ISA does not exist before the start of the main +This scenario creates an ISA with a known ID.This step ensures that ISA does not exist before the start of the main part of the test. #### Successful ISA query check -While F3411-19 does not explicitly require the implementation of a specific ISA retrieval endpoint, Annex A4 specifies the explicit format for this endpoint. If this format is not followed and the error isn't a 404, this check will fail per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. +While F3411-19 does not explicitly require the implementation of a specific ISA retrieval endpoint, Annex A4 specifies the explicit format for this endpoint.If this format is not followed and the error isn't a 404, this check will fail per **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)**. #### Removed pre-existing ISA check -If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test. If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. +If an ISA with the intended ID is already present in the DSS, it needs to be removed before proceeding with the test.If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met. #### Notified subscriber check -When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS). If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. +When a pre-existing ISA needs to be deleted to ensure a clean workspace, any subscribers to ISAs in that area must be notified (as specified by the DSS).If a notification cannot be delivered, then the **[astm.f3411.v22a.NET0730](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the POST ISAs endpoint isn't met. ## Token validation test case diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss_interoperability.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss_interoperability.md index 2e1cd00015..97d8146407 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss_interoperability.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss_interoperability.md @@ -3,10 +3,10 @@ ## Overview The test scenario in this folder verifies that two DSS instances implementing -the API required by ASTM F3411-22a in a shared DSS region interoperate -correctly. This is generally accomplished by performing an operation on one -DSS instance and then verifying that the results are visible in the other -instance. Neither of the two DSS instances need to be an InterUSS Platform +the API required by ASTM F3411-22a in a shared DSS regioninteroperate +correctly.This is generally accomplished by performing anoperation on one +DSS instance and then verifying that the results are visiblein the other +instance.Neither of the two DSS instances need to be an InterUSS Platform implementation. ## Resources @@ -21,16 +21,16 @@ A resources.astm.f3411.DSSInstancesResource containing at least two DSS instance ## Test sequence legend -* *P*: Primary DSS instance under test. The sequence below is +* *P*: Primary DSS instance under test.The sequence below is intended to be repeated so that each DSS is the primary DSS under test for one iteration of the sequence. * *n*: Each of the other (non-Primary) DSS instances. * ISA[*id*]: Reference to Identification Service Area with a particular test id -(test id index, not full UUID identifier). Note that the same UUID should be +(test id index, not full UUID identifier).Note that the same UUID should be used for ISA[i] throughout the sequence even though the logical ISA may be created and deleted multiple times. * Subscription[*id*]: Reference to Subscription with a particular test *id* -(test id index, not full UUID identifier). Note that the same UUID should be +(test id index, not full UUID identifier).Note that the same UUID should be used for Subscription[i] throughout the sequence even though the logical Subscription may be created and deleted multiple times. * D: Number of seconds needed to process requests to all DSS instances before diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/misbehavior.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/misbehavior.md index 698084d61d..ac8956595c 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/misbehavior.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/misbehavior.md @@ -26,7 +26,7 @@ A [`DSSInstanceResource`](../../../../resources/astm/f3411/dss.py) is required f ### Injection test step -In this step, uss_qualifier injects a single nominal flight into each SP under test, usually with a start time in the future. Each SP is expected to queue the provided telemetry and later simulate that telemetry coming from an aircraft at the designated timestamps. +In this step, uss_qualifier injects a single nominal flight into each SP under test, usually with a start time in the future.Each SP is expected to queue the provided telemetry and later simulate that telemetry coming from an aircraft at the designated timestamps. #### Successful injection check @@ -37,7 +37,7 @@ This check will fail if the flight was not successfully injected. #### Identifiable flights check -This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights. This should generally be achieved by injecting appropriate data. +This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights.This should generally be achieved by injecting appropriate data. ### Unauthenticated requests test step diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/nominal_behavior.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/nominal_behavior.md index 4b51b1e82a..679f57de7c 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/nominal_behavior.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/nominal_behavior.md @@ -2,7 +2,7 @@ ## Overview -In this scenario, a single nominal flight is injected into each NetRID Service Provider (SP) under test. Each of the injected flights is expected to be visible to all the observers at appropriate times and for appropriate requests. +In this scenario, a single nominal flight is injected into each NetRID Service Provider (SP) under test.Each of the injected flights is expected to be visible to all the observers at appropriate times and for appropriate requests. ## Resources @@ -12,11 +12,11 @@ A [`FlightDataResource`](../../../../resources/netrid/flight_data.py) containing ### service_providers -A set of [`NetRIDServiceProviders`](../../../../resources/netrid/service_providers.py) to be tested via the injection of RID flight data. This scenario requires at least one SP under test. +A set of [`NetRIDServiceProviders`](../../../../resources/netrid/service_providers.py) to be tested via the injection of RID flight data.This scenario requires at least one SP under test. ### observers -A set of [`NetRIDObserversResource`](../../../../resources/netrid/observers.py) to be tested via checking their observations of the NetRID system and comparing the observations against expectations. An observer generally represents a "Display Application", in ASTM F3411 terminology. This scenario requires at least one observer. +A set of [`NetRIDObserversResource`](../../../../resources/netrid/observers.py) to be tested via checking their observations of the NetRID system and comparing the observations against expectations.An observer generally represents a "Display Application", in ASTM F3411 terminology.This scenario requires at least one observer. ### evaluation_configuration @@ -30,7 +30,7 @@ If specified, uss_qualifier will act as a Display Provider and check a DSS insta ### Injection test step -In this step, uss_qualifier injects a single nominal flight into each SP under test, usually with a start time in the future. Each SP is expected to queue the provided telemetry and later simulate that telemetry coming from an aircraft at the designated timestamps. +In this step, uss_qualifier injects a single nominal flight into each SP under test, usually with a start time in the future.Each SP is expected to queue the provided telemetry and later simulate that telemetry coming from an aircraft at the designated timestamps. #### Successful injection check @@ -43,12 +43,12 @@ This check will fail if the flight was not successfully injected. TODO: Validate injected flights, especially to make sure they contain the specified injection IDs -Per **[interuss.automated_testing.rid.injection.UpsertTestResult](../../../../requirements/interuss/automated_testing/rid/injection.md)**, the NetRID Service Provider under test should only make valid modifications to the injected flights. This includes: +Per **[interuss.automated_testing.rid.injection.UpsertTestResult](../../../../requirements/interuss/automated_testing/rid/injection.md)**, the NetRID Service Provider under test should only make valid modifications to the injected flights.This includes: * A flight with the specified injection ID must be returned. #### Identifiable flights check -This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights. This should generally be achieved by injecting appropriate data. +This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights.This should generally be achieved by injecting appropriate data. ### Service Provider polling test step @@ -70,31 +70,31 @@ This implies that any recent position outside the area must be either preceded o #### ISA query check -**[interuss.f3411.dss_endpoints.SearchISAs](../../../../requirements/interuss/f3411/dss_endpoints.md)** requires a USS providing a DSS instance to implement the DSS endpoints of the OpenAPI specification. If uss_qualifier is unable to query the DSS for ISAs, this check will fail. +**[interuss.f3411.dss_endpoints.SearchISAs](../../../../requirements/interuss/f3411/dss_endpoints.md)** requires a USS providing a DSS instance to implement the DSS endpoints of the OpenAPI specification.If uss_qualifier is unable to query the DSS for ISAs, this check will fail. #### Premature flight check -The timestamps of the injected telemetry usually start in the future. If a flight with injected telemetry only in the future is observed prior to the timestamp of the first telemetry point, this check will fail because the SP does not satisfy **[interuss.automated_testing.rid.injection.ExpectedBehavior](../../../../requirements/interuss/automated_testing/rid/injection.md)**. +The timestamps of the injected telemetry usually start in the future.If a flight with injected telemetry only in the future is observed prior to the timestamp of the first telemetry point, this check will fail because the SP does not satisfy **[interuss.automated_testing.rid.injection.ExpectedBehavior](../../../../requirements/interuss/automated_testing/rid/injection.md)**. #### Missing flight check -**[astm.f3411.v22a.NET0610](../../../../requirements/astm/f3411/v22a.md)** requires that SPs make all UAS operations discoverable over the duration of the flight plus *NetMaxNearRealTimeDataPeriod*, so each injected flight should be observable during this time. If a flight is not observed during its appropriate time period, this check will fail. +**[astm.f3411.v22a.NET0610](../../../../requirements/astm/f3411/v22a.md)** requires that SPs make all UAS operations discoverable over the duration of the flight plus *NetMaxNearRealTimeDataPeriod*, so each injected flight should be observable during this time.If a flight is not observed during its appropriate time period, this check will fail. -**[astm.f3411.v22a.NET0710,1](../../../../requirements/astm/f3411/v22a.md)** and **[astm.f3411.v22a.NET0340](../../../../requirements/astm/f3411/v22a.md) require a Service Provider to implement the GET flights endpoint. This check will also fail if uss_qualifier cannot query that endpoint (specified in the ISA present in the DSS) successfully. +**[astm.f3411.v22a.NET0710,1](../../../../requirements/astm/f3411/v22a.md)** and **[astm.f3411.v22a.NET0340](../../../../requirements/astm/f3411/v22a.md) require a Service Provider to implement the GET flights endpoint.This check will also fail if uss_qualifier cannot query that endpoint (specified in the ISA present in the DSS) successfully. -The identity of flights is determined by precisely matching the known injected positions. If the flight can be found, the USS may not have met **[astm.f3411.v22a.NET0260,Table1,10](../../../../requirements/astm/f3411/v22a.md)** or **[astm.f3411.v22a.NET0260,Table1,11](../../../../requirements/astm/f3411/v22a.md)** prescribing provision of position data consistent with the common data dictionary. +The identity of flights is determined by precisely matching the known injected positions.If the flight can be found, the USS may not have met **[astm.f3411.v22a.NET0260,Table1,10](../../../../requirements/astm/f3411/v22a.md)** or **[astm.f3411.v22a.NET0260,Table1,11](../../../../requirements/astm/f3411/v22a.md)** prescribing provision of position data consistent with the common data dictionary. #### Service Provider altitude check -**[astm.f3411.v22a.NET0260,Table1,12](../../../../requirements/astm/f3411/v22a.md)** requires that relevant Remote ID data, consistent with the common data dictionary, be reported by the Service Provider. Injected flight data had known altitudes, but the altitude reported by the Service Provider did not match those known altitudes. +**[astm.f3411.v22a.NET0260,Table1,12](../../../../requirements/astm/f3411/v22a.md)** requires that relevant Remote ID data, consistent with the common data dictionary, be reported by the Service Provider.Injected flight data had known altitudes, but the altitude reported by the Service Provider did not match those known altitudes. #### Successful flight details query check -**[astm.f3411.v22a.NET0710,2](../../../../requirements/astm/f3411/v22a.md)** and **[astm.f3411.v22a.NET0340](../../../../requirements/astm/f3411/v22a.md) require a Service Provider to implement the GET flight details endpoint. This check will fail if uss_qualifier cannot query that endpoint (specified in the ISA present in the DSS) successfully. +**[astm.f3411.v22a.NET0710,2](../../../../requirements/astm/f3411/v22a.md)** and **[astm.f3411.v22a.NET0340](../../../../requirements/astm/f3411/v22a.md) require a Service Provider to implement the GET flight details endpoint.This check will fail if uss_qualifier cannot query that endpoint (specified in the ISA present in the DSS) successfully. #### Flight details data format check -**[astm.f3411.v22a.NET0710,2](../../../../requirements/astm/f3411/v22a.md)** and **[astm.f3411.v22a.NET0340](../../../../requirements/astm/f3411/v22a.md) require a Service Provider to implement the P2P portion of the OpenAPI specification. This check will fail if the response to the flight details endpoint does not validate against the OpenAPI-specified schema. +**[astm.f3411.v22a.NET0710,2](../../../../requirements/astm/f3411/v22a.md)** and **[astm.f3411.v22a.NET0340](../../../../requirements/astm/f3411/v22a.md) require a Service Provider to implement the P2P portion of the OpenAPI specification.This check will fail if the response to the flight details endpoint does not validate against the OpenAPI-specified schema. #### UAS ID presence in flight details check @@ -134,11 +134,11 @@ If the Operational status reported for an observation does not correspond to the #### Area too large check -**[astm.f3411.v22a.NET0430](../../../../requirements/astm/f3411/v22a.md)** requires that a NetRID Display Provider rejects a request for a very large view area with a diagonal greater than *NetMaxDisplayAreaDiagonal*. If such a large view is requested and a 413 error code is not received, then this check will fail. +**[astm.f3411.v22a.NET0430](../../../../requirements/astm/f3411/v22a.md)** requires that a NetRID Display Provider rejects a request for a very large view area with a diagonal greater than *NetMaxDisplayAreaDiagonal*.If such a large view is requested and a 413 error code is not received, then this check will fail. ### Observer polling test step -In this step, all observers are queried for the flights they observe. Based on the known flights that were injected into the SPs in the first step, these observations are checked against expected behavior/data. Observation rectangles are chosen to encompass the known flights when possible. +In this step, all observers are queried for the flights they observe.Based on the known flights that were injected into the SPs in the first step, these observations are checked against expected behavior/data.Observation rectangles are chosen to encompass the known flights when possible. #### Successful observation check @@ -150,11 +150,11 @@ Per **[interuss.automated_testing.rid.observation.UniqueFlights](../../../../req #### Premature flight check -The timestamps of the injected telemetry usually start in the future. If a flight with injected telemetry only in the future is observed prior to the timestamp of the first telemetry point, this check will fail because the SP does not satisfy **[interuss.automated_testing.rid.injection.ExpectedBehavior](../../../../requirements/interuss/automated_testing/rid/injection.md)**. +The timestamps of the injected telemetry usually start in the future.If a flight with injected telemetry only in the future is observed prior to the timestamp of the first telemetry point, this check will fail because the SP does not satisfy **[interuss.automated_testing.rid.injection.ExpectedBehavior](../../../../requirements/interuss/automated_testing/rid/injection.md)**. #### Missing flight check -**[astm.f3411.v22a.NET0610](../../../../requirements/astm/f3411/v22a.md)** require that SPs make all UAS operations discoverable over the duration of the flight plus *NetMaxNearRealTimeDataPeriod*, so each injected flight should be observable during this time. If one of the flights is not observed during its appropriate time period, this check will fail. +**[astm.f3411.v22a.NET0610](../../../../requirements/astm/f3411/v22a.md)** require that SPs make all UAS operations discoverable over the duration of the flight plus *NetMaxNearRealTimeDataPeriod*, so each injected flight should be observable during this time.If one of the flights is not observed during its appropriate time period, this check will fail. #### Lingering flight check @@ -174,7 +174,7 @@ If the observed altitude of a flight does not match the altitude of the injected #### Area too large check -**[astm.f3411.v22a.NET0430](../../../../requirements/astm/f3411/v22a.md)** require that a NetRID Display Provider reject a request for a very large view area with a diagonal greater than *NetMaxDisplayAreaDiagonal*. If such a large view is requested and a 413 error code is not received, then this check will fail. +**[astm.f3411.v22a.NET0430](../../../../requirements/astm/f3411/v22a.md)** require that a NetRID Display Provider reject a request for a very large view area with a diagonal greater than *NetMaxDisplayAreaDiagonal*.If such a large view is requested and a 413 error code is not received, then this check will fail. #### Minimal obfuscation distance of individual flights check diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/operator_interactions.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/operator_interactions.md index 91c4fb6162..c40c98f769 100644 --- a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/operator_interactions.md +++ b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/operator_interactions.md @@ -24,7 +24,7 @@ TODO: Create this resource ### flights_data -A [`FlightDataResource`](../../../../resources/netrid/flight_data.py) containing 1 flight. This flight must: +A [`FlightDataResource`](../../../../resources/netrid/flight_data.py) containing 1 flight.This flight must: * (Phase 1): Start out nominal * (Phase 2): Then contain a pause (lack of telemetry) sufficient to trigger NET0040 * (Phase 3): Then resume nominal telemetry @@ -40,7 +40,7 @@ TODO: Create this resource ### Verify no ISAs test step -uss_qualifier checks the DSS to ensure that the Service Provider under test does not have any ISAs in the system. If ISAs are present, the Service Provider is instructed to clear the area of active flights, after which uss_qualifier reverifies the absence of ISAs. +uss_qualifier checks the DSS to ensure that the Service Provider under test does not have any ISAs in the system.If ISAs are present, the Service Provider is instructed to clear the area of active flights, after which uss_qualifier reverifies the absence of ISAs. ### Disable DSS test step @@ -66,7 +66,7 @@ uss_qualifier retrieves the current (after failed flight) set of operator notifi #### Operator notified of discoverability failure check -The "after" set of operator notifications should contain at least one more entry than the "before" set of operator notifications. If there was no new operator notification, the Service Provider will not have met **[astm.f3411.v22a.NET0620](../../../../requirements/astm/f3411/v22a.md)**. +The "after" set of operator notifications should contain at least one more entry than the "before" set of operator notifications.If there was no new operator notification, the Service Provider will not have met **[astm.f3411.v22a.NET0620](../../../../requirements/astm/f3411/v22a.md)**. TODO: Implement