diff --git a/monitoring/uss_qualifier/configurations/dev/message_signing.yaml b/monitoring/uss_qualifier/configurations/dev/message_signing.yaml index 56ccd5028b..f59feedc10 100644 --- a/monitoring/uss_qualifier/configurations/dev/message_signing.yaml +++ b/monitoring/uss_qualifier/configurations/dev/message_signing.yaml @@ -59,6 +59,7 @@ v1: dss: scd_dss dss_instances: scd_dss_instances id_generator: id_generator + utm_client_identity: utm_client_identity second_utm_auth: second_utm_auth planning_area: che_planning_area problematically_big_area: che_problematically_big_area diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/create.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/create.md new file mode 100644 index 0000000000..6b20c141db --- /dev/null +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/create.md @@ -0,0 +1,24 @@ +# Create subscription test step fragment + +This test step fragment validates that subscriptions can be created. + +## 🛑 Create subscription query succeeds check + +As per **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**, the DSS API must allow callers to create a subscription with either one or both of the +start and end time missing, provided all the required parameters are valid. + +## 🛑 Create subscription response is correct check + +A successful subscription creation query is expected to return a well-defined body, the content of which reflects the created subscription. +If the format and content of the response are not conforming, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. + +## ⚠️ Create subscription response format conforms to spec check + +The response to a successful subscription creation query is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21. + +If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. + +## 🛑 Response to subscription creation contains a subscription check + +As per **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**, upon creation of a subscription, +the newly created subscription must be part of its response. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/delete.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/delete.md new file mode 100644 index 0000000000..c523ebb942 --- /dev/null +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/delete.md @@ -0,0 +1,13 @@ +# Delete subscription test step fragment + +This test step fragment validates that subscriptions can be deleted. + +## 🛑 Subscription can be deleted check + +An attempt to delete a subscription when the correct version is provided should succeed, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. + +## ⚠️ Delete subscription response format conforms to spec check + +The response to a successful subscription deletion query is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21. + +If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/read.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/read.md new file mode 100644 index 0000000000..507f2ed12d --- /dev/null +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/read.md @@ -0,0 +1,21 @@ +# Read subscription test step fragment + +This test step fragment validates that subscriptions can be read. + +## 🛑 Get Subscription by ID check + +If a subscription cannot be queried using its ID, the DSS is failing to meet **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. + +## ⚠️ Get subscription response format conforms to spec check + +The response to a successful get subscription query is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21. + +If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. + +## 🛑 Successful subscription search query check + +If the DSS fails to let us search in the area for which the subscription was created, it is failing to meet **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. + +## 🛑 Created Subscription is in search results check + +If the existing subscription is not returned in a search that covers the area it was created for, the DSS is not properly implementing **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/update.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/update.md new file mode 100644 index 0000000000..8810035448 --- /dev/null +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/update.md @@ -0,0 +1,18 @@ +# Update subscription test step fragment + +This test step fragment validates that subscriptions can be updated. + +## 🛑 Subscription can be mutated check + +If a subscription cannot be modified with a valid set of parameters, the DSS is failing to meet **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. + +## 🛑 Response to subscription mutation contains a subscription check + +As per **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**, upon mutation of a subscription, +the newly created subscription must be part of its response. + +## ⚠️ Mutate subscription response format conforms to spec check + +The response to a successful subscription mutation query is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21. + +If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_sync.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/sync.md similarity index 82% rename from monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_sync.md rename to monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/sync.md index 072db1dba1..4a8e3e2f05 100644 --- a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_sync.md +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/sync.md @@ -5,39 +5,39 @@ This test step fragment validates that subscriptions are properly synchronized a ## 🛑 Subscription can be found at every DSS check If the previously created or mutated subscription cannot be found at a DSS, either one of the instances at which the subscription was created or the one that was queried, -may be failing to implement **[astm.f3548.v21.DSS0210,1a](../../../../../requirements/astm/f3548/v21.md)**. +may be failing to implement **[astm.f3548.v21.DSS0210,1a](../../../../../../requirements/astm/f3548/v21.md)**. ## 🛑 Propagated subscription contains the correct USS base URL check If the subscription returned by a DSS to which the subscription was synchronized to does not contain the correct USS base URL, -either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1c](../../../../../requirements/astm/f3548/v21.md)**. +either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1c](../../../../../../requirements/astm/f3548/v21.md)**. ## 🛑 Propagated subscription contains the correct start time check If the subscription returned by a DSS to which the subscription was synchronized to does not contain the correct start time, -either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1e](../../../../../requirements/astm/f3548/v21.md)**. +either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1e](../../../../../../requirements/astm/f3548/v21.md)**. ## 🛑 Propagated subscription contains the correct end time check If the subscription returned by a DSS to which the subscription was synchronized to does not contain the correct end time, -either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1e](../../../../../requirements/astm/f3548/v21.md)**. +either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1e](../../../../../../requirements/astm/f3548/v21.md)**. ## 🛑 Propagated subscription contains the correct version check If the subscription returned by a DSS to which the subscription was synchronized to does not contain the correct version, -either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1f](../../../../../requirements/astm/f3548/v21.md)**. +either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1f](../../../../../../requirements/astm/f3548/v21.md)**. ## 🛑 Propagated subscription contains the correct notification flags check If the subscription returned by a DSS to which the subscription was synchronized to does not contain the correct notification flags, -either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1g](../../../../../requirements/astm/f3548/v21.md)**. +either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1g](../../../../../../requirements/astm/f3548/v21.md)**. ## 🛑 Propagated subscription contains the correct implicit flag check If the subscription returned by a DSS to which the subscription was synchronized to does not contain the correct implicit flag, -either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1h](../../../../../requirements/astm/f3548/v21.md)**. +either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1h](../../../../../../requirements/astm/f3548/v21.md)**. ## 🛑 Propagated subscription contains expected notification count check If the subscription returned by a DSS to which the subscription was synchronized to does not contain the expected notification count, -either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1i](../../../../../requirements/astm/f3548/v21.md)**. +either one of the instances at which the subscription was created or the one that was queried, may be failing to implement **[astm.f3548.v21.DSS0210,1i](../../../../../../requirements/astm/f3548/v21.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_validate.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/correctness.md similarity index 61% rename from monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_validate.md rename to monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/correctness.md index 55c63541d1..aa05b86ad0 100644 --- a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_validate.md +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/correctness.md @@ -1,67 +1,59 @@ # Validate subscription test step fragment -This test step fragment attempts to validate a single subscription returned by the DSS after its creation or mutation. +This test step fragment attempts to validate the content of a single subscription returned by the DSS. -The code for these checks lives in the [subscription_validator.py](../validators/subscription_validator.py) class. +The code for these checks lives in the [subscription_validator.py](../../../validators/subscription_validator.py) class. ## ⚠️ Returned subscription ID is correct check If the returned subscription ID does not correspond to the one specified in the creation parameters, -**[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)** is not respected. +**[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)** is not respected. ## ⚠️ New subscription has a notification index of 0 check -The notification index of a newly created subscription must be 0, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +The notification index of a newly created subscription must be 0, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. ## ⚠️ Returned notification index is equal to or greater than 0 check -If the notification index of the subscription is less than 0, the DSS fails to properly implement **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +If the notification index of the subscription is less than 0, the DSS fails to properly implement **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. ## ⚠️ Returned subscription has an USS base URL check -If the returned subscription has no USS base URL defined, **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)** is not respected. +If the returned subscription has no USS base URL defined, **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)** is not respected. ## ⚠️ Returned USS base URL has correct base URL check -The returned USS base URL must be prefixed with the USS base URL that was provided at subscription creation, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +The returned USS base URL must be prefixed with the USS base URL that was provided at subscription creation, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. ## ⚠️ Returned subscription has a start time check -If the returned subscription has no start time defined, **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)** is not respected. +If the returned subscription has no start time defined, **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)** is not respected. ## ⚠️ Returned start time is correct check -The returned start time must be the same as the provided one, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +The returned start time must be the same as the provided one, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. ## ⚠️ Returned subscription has an end time check -Subscriptions need a defined end time in order to limit their duration: if the DSS omits to set the end time, it will be in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +Subscriptions need a defined end time in order to limit their duration: if the DSS omits to set the end time, it will be in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. ## ⚠️ Returned end time is correct check -The returned end time must be the same as the provided one, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +The returned end time must be the same as the provided one, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. ## ⚠️ Returned subscription has a version check -If the returned subscription has no version defined, **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)** is not respected. - -## ⚠️ Non-mutated subscription keeps the same version check - -If the version of the subscription is updated without there having been any mutation of the subscription, the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## ⚠️ Mutated subscription version is updated check - -Following a mutation, the DSS needs to update the subscription version, otherwise it is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +If the returned subscription has no version defined, **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)** is not respected. ## ⚠️ Non-implicit subscription has implicit flag set to false check A subscription that was explicitly created by a client should always have its `implicit_subscription` flag set to false, -otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. ## ⚠️ Operational intents notification flag is as requested check -If the subscription was created with the `include_operational_intents` flag set to true, the returned subscription must have the same flag set to true, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +If the subscription was created with the `include_operational_intents` flag set to true, the returned subscription must have the same flag set to true, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. ## ⚠️ Constraints notification flag is as requested check -If the subscription was created with the `include_constraints` flag set to true, the returned subscription must have the same flag set to true, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. +If the subscription was created with the `include_constraints` flag set to true, the returned subscription must have the same flag set to true, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/mutated.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/mutated.md new file mode 100644 index 0000000000..cd8bfa17cf --- /dev/null +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/mutated.md @@ -0,0 +1,9 @@ +# Validate mutated subscription test step fragment + +This test step fragment attempts to validate a single subscription returned by the DSS after its mutation. + +The code for these checks lives in the [subscription_validator.py](../../../validators/subscription_validator.py) class. + +## ⚠️ Mutated subscription version is updated check + +Following a mutation, the DSS needs to update the subscription version, otherwise it is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/non_mutated.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/non_mutated.md new file mode 100644 index 0000000000..ab73ac7762 --- /dev/null +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/validate/non_mutated.md @@ -0,0 +1,9 @@ +# Validate non-mutated subscription test step fragment + +This test step fragment attempts to validate a single subscription returned by the DSS after its creation or mutation. + +The code for these checks lives in the [subscription_validator.py](../../../validators/subscription_validator.py) class. + +## ⚠️ Non-mutated subscription keeps the same version check + +If the version of the subscription is updated without there having been any mutation of the subscription, the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../../../requirements/astm/f3548/v21.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_crud.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_crud.md deleted file mode 100644 index 3b8f09d2d7..0000000000 --- a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/subscription_crud.md +++ /dev/null @@ -1,67 +0,0 @@ -# CRUD subscription test step fragment - -This test step fragment validates that subscriptions can be created, updated, read and modified. - -## 🛑 Create subscription query succeeds check - -As per **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**, the DSS API must allow callers to create a subscription with either one or both of the -start and end time missing, provided all the required parameters are valid. - -## 🛑 Create subscription response is correct check - -A successful subscription creation query is expected to return a well-defined body, the content of which reflects the created subscription. -If the format and content of the response are not conforming, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## ⚠️ Create subscription response format conforms to spec check - -The response to a successful subscription creation query is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21. - -If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## 🛑 Response to subscription creation contains a subscription check - -As per **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**, upon creation of a subscription, -the newly created subscription must be part of its response. - -## 🛑 Get Subscription by ID check - -If a subscription cannot be queried using its ID, the DSS is failing to meet **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## ⚠️ Get subscription response format conforms to spec check - -The response to a successful get subscription query is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21. - -If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## 🛑 Successful subscription search query check - -If the DSS fails to let us search in the area for which the subscription was created, it is failing to meet **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## 🛑 Created Subscription is in search results check - -If the existing subscription is not returned in a search that covers the area it was created for, the DSS is not properly implementing **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## 🛑 Subscription can be mutated check - -If a subscription cannot be modified with a valid set of parameters, the DSS is failing to meet **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## 🛑 Response to subscription mutation contains a subscription check - -As per **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**, upon mutation of a subscription, -the newly created subscription must be part of its response. - -## ⚠️ Mutate subscription response format conforms to spec check - -The response to a successful subscription mutation query is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21. - -If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## 🛑 Subscription can be deleted check - -An attempt to delete a subscription when the correct version is provided should succeed, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. - -## ⚠️ Delete subscription response format conforms to spec check - -The response to a successful subscription deletion query is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21. - -If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/subscription_simple.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/subscription_simple.md index b977bd6cc8..c16030ebf3 100644 --- a/monitoring/uss_qualifier/scenarios/astm/utm/dss/subscription_simple.md +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/subscription_simple.md @@ -53,7 +53,7 @@ The response to a successful subscription creation query is expected to conform If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../requirements/astm/f3548/v21.md)**. -#### [Validate subscription](fragments/subscription_validate.md) +#### [Validate subscription](fragments/sub/validate/correctness.md) Verify that the subscription returned by the DSS after its creation is properly formatted and has the right content. @@ -99,10 +99,14 @@ If the created subscription is not returned in a search that covers the area it In accordance with **[astm.f3548.v21.DSS0005,5](../../../../requirements/astm/f3548/v21.md)**, the DSS should not allow searches for areas that are too big. -#### [Validate subscription](fragments/subscription_validate.md) +#### [Validate subscription](fragments/sub/validate/correctness.md) Verify that the subscription returned by the DSS via the search is correctly formatted and corresponds to what was created earlier. +#### [Validate version field](fragments/sub/validate/non_mutated.md) + +Verify that the version field is as expected. + ### Mutate Subscription test step This test step mutates the previously created subscription to verify that the DSS reacts properly: notably, it checks that the subscription version is updated, @@ -123,10 +127,14 @@ The response to a successful subscription mutation query is expected to conform If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../../../../requirements/astm/f3548/v21.md)**. -#### [Validate subscription](fragments/subscription_validate.md) +#### [Validate subscription](fragments/sub/validate/correctness.md) Verify that the subscription returned by the DSS via the mutation is properly formatted and contains the correct content. +#### [Validate version field](fragments/sub/validate/mutated.md) + +Verify that the version field has been mutated. + ### Delete Subscription test step Attempt to delete the subscription in various ways and ensure that the DSS reacts properly. @@ -160,10 +168,14 @@ If it does not, the DSS is failing to implement **[astm.f3548.v21.DSS0005,5](../ An attempt to delete a subscription when the correct version is provided should succeed, otherwise the DSS is in violation of **[astm.f3548.v21.DSS0005,5](../../../../requirements/astm/f3548/v21.md)**. -#### [Validate subscription](fragments/subscription_validate.md) +#### [Validate subscription](fragments/sub/validate/correctness.md) Verify that the subscription returned by the DSS via the deletion is properly formatted and contains the correct content. +#### [Validate version field](fragments/sub/validate/non_mutated.md) + +Verify that the version field is as expected. + ### Query Deleted Subscription test step Attempt to query and search for the deleted subscription in various ways diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md index 5e1d24dfe9..33fe346f07 100644 --- a/monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md @@ -40,11 +40,11 @@ This test step creates multiple subscriptions with different combinations of the All subscriptions are left on the DSS when this step ends, as they are expected to be present for the subsequent step. -#### [Create subscription](../fragments/subscription_crud.md) +#### [Create subscription](../fragments/sub/crud/create.md) Verify that a subscription can be created on the primary DSS. -#### [Validate subscription](../fragments/subscription_validate.md) +#### [Validate subscription](../fragments/sub/validate/correctness.md) Verify that the subscription returned by the DSS under test is properly formatted and contains the expected content. @@ -58,31 +58,39 @@ When queried for a subscription that was created via another DSS, a DSS instance If it does not, it might be in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. -#### [Subscription is synchronized](../fragments/subscription_sync.md) +#### [Subscription is synchronized](../fragments/sub/sync.md) Confirm that the subscription that was just created is properly synchronized across all DSS instances. -#### [Get subscription](../fragments/subscription_crud.md) +#### [Get subscription](../fragments/sub/crud/read.md) Confirms that each DSS provides access to the created subscription, -#### [Validate subscription](../fragments/subscription_validate.md) +#### [Validate subscription](../fragments/sub/validate/correctness.md) Verify that the subscription returned by every DSS is correctly formatted and corresponds to what was created earlier. +#### [Validate version](../fragments/sub/validate/non_mutated.md) + +Verify that the version of the subscription returned by every DSS is as expected. + ### Mutate subscription test step This test step mutates the previously created subscription to verify that the DSS reacts properly: notably, it checks that the subscription version is updated, including for changes that are not directly visible, such as changing the subscription's footprint. -#### [Update subscription](../fragments/subscription_crud.md) +#### [Update subscription](../fragments/sub/crud/update.md) Confirm that the subscription can be mutated. -#### [Validate subscription](../fragments/subscription_validate.md) +#### [Validate subscription](../fragments/sub/validate/correctness.md) Verify that the subscription returned by the DSS is properly formatted and contains the correct content. +#### [Validate version](../fragments/sub/validate/mutated.md) + +Verify that the version of the subscription returned by the DSS has been updated. + ### Query updated subscription test step Query the updated subscription at every DSS provided in `dss_instances`. @@ -93,32 +101,40 @@ When queried for a subscription that was mutated via another DSS, a DSS instance If it does not, it might be in violation of **[astm.f3548.v21.DSS0005,5](../../../../../requirements/astm/f3548/v21.md)**. -#### [Subscription is synchronized](../fragments/subscription_sync.md) +#### [Subscription is synchronized](../fragments/sub/sync.md) Confirm that the subscription that was just mutated is properly synchronized across all DSS instances. -#### [Get subscription](../fragments/subscription_crud.md) +#### [Get subscription](../fragments/sub/crud/read.md) Confirms that the subscription that was just mutated can be retrieved from any DSS. -#### [Validate subscription](../fragments/subscription_validate.md) +#### [Validate subscription](../fragments/sub/validate/correctness.md) Verify that the subscription returned by every DSS is correctly formatted and corresponds to what was mutated earlier. +#### [Validate version](../fragments/sub/validate/non_mutated.md) + +Verify that the version of the subscription returned by every DSS is as expected. + ### Delete subscription test step Attempt to delete the subscription in various ways and ensure that the DSS reacts properly. This also checks that the subscription data returned by a successful deletion is correct. -#### [Delete subscription](../fragments/subscription_crud.md) +#### [Delete subscription](../fragments/sub/crud/delete.md) Confirms that a subscription can be deleted. -#### [Validate subscription](../fragments/subscription_validate.md) +#### [Validate subscription](../fragments/sub/validate/correctness.md) Verify that the subscription returned by the DSS via the deletion is properly formatted and contains the correct content. +#### [Validate version](../fragments/sub/validate/non_mutated.md) + +Verify that the version of the subscription returned by the DSS is as expected + ### Query deleted subscription test step Attempt to query and search for the deleted subscription in various ways diff --git a/monitoring/uss_qualifier/suites/faa/uft/message_signing.yaml b/monitoring/uss_qualifier/suites/faa/uft/message_signing.yaml index f3a4766e2b..6483275157 100644 --- a/monitoring/uss_qualifier/suites/faa/uft/message_signing.yaml +++ b/monitoring/uss_qualifier/suites/faa/uft/message_signing.yaml @@ -11,6 +11,7 @@ resources: priority_preemption_flights: resources.flight_planning.FlightIntentsResource invalid_flight_intents: resources.flight_planning.FlightIntentsResource id_generator: resources.interuss.IDGeneratorResource + utm_client_identity: resources.communications.ClientIdentityResource second_utm_auth: resources.communications.AuthAdapterResource? planning_area: resources.astm.f3548.v21.PlanningAreaResource problematically_big_area: resources.VerticesResource @@ -35,6 +36,7 @@ actions: dss_instances: dss_instances dss_crdb_cluster: dss_crdb_cluster? id_generator: id_generator + utm_client_identity: utm_client_identity second_utm_auth: second_utm_auth planning_area: planning_area problematically_big_area: problematically_big_area