-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
PR comment integration
- Loading branch information
Showing
25 changed files
with
880 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 0 additions & 7 deletions
7
monitoring/uss_qualifier/scenarios/astm/utm/dss/remove_op_intent.md
This file was deleted.
Oops, something went wrong.
1 change: 1 addition & 0 deletions
1
monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/__init__.py
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,2 @@ | ||
from .subscription_synchronization import SubscriptionSynchronization | ||
from .op_intent_ref_synchronization import OIRSynchronization |
148 changes: 148 additions & 0 deletions
148
...alifier/scenarios/astm/utm/dss/synchronization/op_intent_ref_synchronization.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,148 @@ | ||
# ASTM SCD DSS: Operational Intent Reference Synchronization test scenario | ||
|
||
## Overview | ||
|
||
Verifies that all CRUD operations on operational intent references performed on a given DSS instance | ||
are properly propagated to every other DSS instance participating in the deployment. | ||
|
||
## Resources | ||
|
||
### dss | ||
|
||
[`DSSInstanceResource`](../../../../../resources/astm/f3548/v21/dss.py) the DSS instance through which entities are created, modified and deleted. | ||
|
||
### other_instances | ||
|
||
[`DSSInstancesResource`](../../../../../resources/astm/f3548/v21/dss.py) pointing to the DSS instances used to confirm that entities are properly propagated. | ||
|
||
### id_generator | ||
|
||
[`IDGeneratorResource`](../../../../../resources/interuss/id_generator.py) providing the Subscription ID for this scenario. | ||
|
||
### planning_area | ||
|
||
[`PlanningAreaResource`](../../../../../resources/astm/f3548/v21/planning_area.py) describes the 3D volume in which subscriptions will be created. | ||
|
||
### client_identity | ||
|
||
[`ClientIdentityResource`](../../../../../resources/communications/client_identity.py) to be used for this scenario. | ||
|
||
## Setup test case | ||
|
||
### [Ensure clean workspace test step](../clean_workspace.md) | ||
|
||
This step ensures that no subscription with the known test ID exists in the DSS. | ||
|
||
## OIR synchronization test case | ||
|
||
This test case creates an operational intent reference on the main DSS, and verifies that it is properly synchronized to the other DSS instances. | ||
|
||
It then goes on to mutate and delete it, each time confirming that all other DSSes return the expected results. | ||
|
||
### Create OIR validation test step | ||
|
||
#### [Create OIR](../fragments/oir/crud/create.md) | ||
|
||
Verify that an operational intent reference can be created on the primary DSS. | ||
|
||
#### [OIR Content is correct](../fragments/oir/validate/correctness.md) | ||
|
||
Verify that the operational intent reference returned by the DSS under test is properly formatted and contains the expected content. | ||
|
||
### Query newly created OIR test step | ||
|
||
Query the created operational intent at every DSS provided in `dss_instances`. | ||
|
||
#### 🛑 Operational intent reference returned by a secondary DSS is valid and correct check | ||
|
||
When queried for an operational intent reference that was created via another DSS, a DSS instance is expected to provide a valid operational intent reference. | ||
|
||
If it does not, it is in violation of **[astm.f3548.v21.DSS0005,1](../../../../../requirements/astm/f3548/v21.md)**. | ||
|
||
#### [OIR is synchronized](../fragments/oir/sync.md) | ||
|
||
Confirm that the operational intent reference that was just created is properly synchronized across all DSS instances. | ||
|
||
#### [Get OIR](../fragments/oir/crud/read.md) | ||
|
||
Confirms that each DSS provides access to the created operational intent reference, | ||
|
||
#### [OIR Content is correct](../fragments/oir/validate/correctness.md) | ||
|
||
Verify that the operational intent reference returned by every DSS is correctly formatted and corresponds to what was created earlier. | ||
|
||
#### [OIR Versions are correct](../fragments/oir/validate/non_mutated.md) | ||
|
||
Verify that the operational intent reference's version fields are as expected. | ||
|
||
### Mutate OIR test step | ||
|
||
This test step mutates the previously created operational intent reference to verify that the DSS reacts properly: notably, it checks that the operational intent reference version is updated, | ||
including for changes that are not directly visible, such as changing the operational intent reference's footprint. | ||
|
||
#### [Update OIR](../fragments/oir/crud/update.md) | ||
|
||
Confirm that the operational intent reference can be mutated. | ||
|
||
#### [Validate OIR](../fragments/oir/validate/correctness.md) | ||
|
||
Verify that the operational intent reference returned by the DSS is properly formatted and contains the correct content. | ||
|
||
#### [OIR Versions are correct](../fragments/oir/validate/mutated.md) | ||
|
||
Verify that the operational intent reference's version fields have been updated. | ||
|
||
### Query updated OIR test step | ||
|
||
Query the updated operational intent reference at every DSS provided in `dss_instances`. | ||
|
||
#### 🛑 Operational intent reference returned by a secondary DSS is valid and correct check | ||
|
||
When queried for an operational intent reference that was mutated via another DSS, a DSS instance is expected to provide a valid operational intent reference. | ||
|
||
If it does not, it is in violation of **[astm.f3548.v21.DSS0005,1](../../../../../requirements/astm/f3548/v21.md)**. | ||
|
||
#### [OIR is synchronized](../fragments/oir/sync.md) | ||
|
||
Confirm that the operational intent reference that was just mutated is properly synchronized across all DSS instances. | ||
|
||
#### [Get OIR](../fragments/oir/crud/read.md) | ||
|
||
Confirms that the operational intent reference that was just mutated can be retrieved from any DSS. | ||
|
||
#### [Validate OIR](../fragments/oir/validate/correctness.md) | ||
|
||
Verify that the operational intent reference returned by every DSS is correctly formatted and corresponds to what was mutated earlier. | ||
|
||
#### [OIR Versions are correct](../fragments/oir/validate/non_mutated.md) | ||
|
||
Verify that the operational intent reference's version fields are as expected. | ||
|
||
### Delete OIR test step | ||
|
||
Attempt to delete the operational intent reference in various ways and ensure that the DSS reacts properly. | ||
|
||
This also checks that the operational intent reference data returned by a successful deletion is correct. | ||
|
||
#### [Delete OIR](../fragments/oir/crud/delete.md) | ||
|
||
Confirms that an operational intent reference can be deleted. | ||
|
||
#### [Validate OIR](../fragments/oir/validate/correctness.md) | ||
|
||
Verify that the operational intent reference returned by the DSS via the deletion is properly formatted and contains the correct content. | ||
|
||
#### [OIR Versions are correct](../fragments/oir/validate/non_mutated.md) | ||
|
||
Verify that the operational intent reference's version fields are as expected. | ||
|
||
### Query deleted OIR test step | ||
|
||
Attempt to query and search for the deleted operational intent reference in various ways | ||
|
||
#### 🛑 Secondary DSS should not return the deleted operational intent reference check | ||
|
||
If a DSS returns an operational intent reference that was previously successfully deleted from the primary DSS, | ||
either one of the primary DSS or the DSS that returned the operational intent reference is in violation of **[astm.f3548.v21.DSS0210,2a](../../../../../requirements/astm/f3548/v21.md)**. | ||
|
||
## [Cleanup](../clean_workspace.md) |
Oops, something went wrong.