| Case | Step | Event | iart_dss | onesky | sait | <None> | ||
|---|---|---|---|---|---|---|---|---|
| 1 | 📓 |
Tested USS: onesky
|
||||||
| 2 | 📓 |
Control USS: sait
|
||||||
| Prerequisites check | Verify area is clear | 3 | 🌐 |
|
🌐 | |||
| 4 | ✅ | DSS responses | ✅ | |||||
| 5 | ✅ | Area is clear of op intents | ✅ | |||||
| Attempt to plan flight in conflict | Plan Flight 2 | 6 | 🌐 |
|
🌐 | |||
| 7 | ✅ | DSS responses | ✅ | |||||
| 8 | 🌐 |
|
🌐 | |||||
| 9 | ✅ | Failure | ✅ | |||||
| 10 | ✅ | Successful planning | ✅ | |||||
| 11 | 🌐 |
|
🌐 | |||||
| 12 | ✅ | DSS responses | ✅ | |||||
| 13 | ✅ | Operational intent shared correctly | ✅ | |||||
| 14 | ✅ | Operational intent state is correct | ✅ | |||||
| 15 | 🌐 |
|
🌐 | |||||
| 16 | ✅ | Operational intent details retrievable | ✅ | |||||
| 17 | ✅ | Operational intent details data format | ✅ | |||||
| 18 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | |||||
| 19 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | |||||
| 20 | ✅ | Correct operational intent details | ✅ | |||||
| 21 | ✅ | Operational intent details extents are contained within reference extents | ✅ | |||||
| 22 | ✅ | Off-nominal volumes | ✅ | |||||
| 23 | ✅ | Vertices | ✅ | |||||
| Attempt to plan Flight 1 | 24 | 🌐 |
|
🌐 | ||||
| 25 | ✅ | DSS responses | ✅ | |||||
| 26 | 🌐 |
|
🌐 | |||||
| 27 | ✅ | Failure | ✅ | |||||
| 28 | ✅ | Incorrectly planned | ✅ | |||||
| 29 | 🌐 |
|
🌐 | |||||
| 30 | ✅ | DSS responses | ✅ | |||||
| 31 | ✅ | Operational intent not shared | ✅ | |||||
| Delete Flight 2 | 32 | 🌐 |
|
🌐 | ||||
| 33 | ✅ | Successful deletion | ✅ | |||||
| Attempt to modify planned flight in conflict | Plan Flight 1 | 34 | 🌐 |
|
🌐 | |||
| 35 | ✅ | DSS responses | ✅ | |||||
| 36 | 🌐 |
|
🌐 | |||||
| 37 | ✅ | Failure | ✅ | |||||
| 38 | ✅ | Successful planning | ✅ | |||||
| 39 | 🌐 |
|
🌐 | |||||
| 40 | ✅ | DSS responses | ✅ | |||||
| 41 | ✅ | Operational intent shared correctly | ✅ | |||||
| 42 | ✅ | Operational intent state is correct | ✅ | |||||
| 43 | 🌐 |
|
🌐 | |||||
| 44 | ✅ | Operational intent details retrievable | ✅ | |||||
| 45 | ✅ | Operational intent details data format | ✅ | |||||
| 46 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | |||||
| 47 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | |||||
| 48 | ✅ | Correct operational intent details | ✅ | |||||
| 49 | ✅ | Operational intent details extents are contained within reference extents | ✅ | |||||
| 50 | ✅ | Off-nominal volumes | ✅ | |||||
| 51 | ✅ | Vertices | ✅ | |||||
| Plan Flight 2 | 52 | 🌐 |
|
🌐 | ||||
| 53 | ✅ | Retrieve pre-existing notifications | ✅ | |||||
| 54 | 🌐 |
|
🌐 | |||||
| 55 | ✅ | Retrieve pre-existing notifications | ✅ | |||||
| 56 | 🌐 |
|
🌐 | |||||
| 57 | ✅ | DSS responses | ✅ | |||||
| 58 | 🌐 |
|
🌐 | |||||
| 59 | ✅ | Failure | ✅ | |||||
| 60 | ✅ | Successful planning | ✅ | |||||
| 61 | 🌐 |
|
🌐 | |||||
| 62 | ✅ | DSS responses | ✅ | |||||
| 63 | ✅ | Operational intent shared correctly | ✅ | |||||
| 64 | ✅ | Operational intent state is correct | ✅ | |||||
| 65 | 🌐 |
|
🌐 | |||||
| 66 | ✅ | Operational intent details retrievable | ✅ | |||||
| 67 | ✅ | Operational intent details data format | ✅ | |||||
| 68 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | |||||
| 69 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | |||||
| 70 | ✅ | Correct operational intent details | ✅ | |||||
| 71 | ✅ | Operational intent details extents are contained within reference extents | ✅ | |||||
| 72 | ✅ | Off-nominal volumes | ✅ | |||||
| 73 | ✅ | Vertices | ✅ | |||||
| Check for conflict notifications | 75 | 🌐 |
|
🌐 | ||||
| 76 | ✅ | Retrieve notifications | ✅ | |||||
| 77 | 🌐 |
|
🌐 | |||||
| 78 | ✅ | Retrieve notifications | ✅ | |||||
| 79 | 🌐 |
|
🌐 | |||||
| 80 | ✅ | Retrieve notifications | ✅ | |||||
| 81 | 🌐 |
|
🌐 | |||||
| 82 | ✅ | Retrieve notifications | ✅ | |||||
| 83 | 🌐 |
|
🌐 | |||||
| 84 | ✅ | Retrieve notifications | ✅ | |||||
| 85 | 📓 |
scd0090_notification: sait notification latency: >0s
|
||||||
| Attempt to modify planned Flight 1 in conflict | 87 | 🌐 |
|
🌐 | ||||
| 88 | ✅ | DSS responses | ✅ | |||||
| 89 | 🌐 |
|
🌐 | |||||
| 90 | ✅ | Failure | ✅ | |||||
| 91 | ✅ | Incorrectly modified | ✅ | |||||
| 92 | 🌐 |
|
🌐 | |||||
| 93 | ✅ | DSS responses | ✅ | |||||
| 94 | 📓 |
onesky no op intent: Operational intent reference with ID c2ced5c7-79db-4ddd-bb51-80e40a13734e not found in DSS for test step 'Attempt to modify planned Flight 1 in conflict'.
|
||||||
| Attempt to activate flight in conflict | Attempt to activate conflicting Flight 1 | 96 | 🌐 |
|
🌐 | |||
| 97 | ✅ | DSS responses | ✅ | |||||
| 98 | 🌐 |
|
🌐 | |||||
| 99 | ✅ | Failure | ✅ | |||||
| 100 | ✅ | Incorrectly activated | ✅ | |||||
| 101 | 🌐 |
|
🌐 | |||||
| 102 | ✅ | DSS responses | ✅ | |||||
| 103 | 📓 |
onesky no op intent_1: No new operational intent was found in DSS for test step 'Attempt to activate conflicting Flight 1'.
|
||||||
| 104 | ✅ | Operational intent shared correctly | ✅ | |||||
| Modify activated flight with pre-existing conflict | Delete Flight 2 | 105 | 🌐 |
|
🌐 | |||
| 106 | ✅ | Successful deletion | ✅ | |||||
| Activate Flight 1 | 107 | 🌐 |
|
🌐 | ||||
| 108 | ✅ | DSS responses | ✅ | |||||
| 109 | 🌐 |
|
🌐 | |||||
| 110 | ✅ | Failure | ✅ | |||||
| 111 | ✅ | Successful activation | ✅ | |||||
| 112 | 🌐 |
|
🌐 | |||||
| 113 | ✅ | DSS responses | ✅ | |||||
| 114 | ✅ | Operational intent shared correctly | ✅ | |||||
| 115 | ✅ | Operational intent state is correct | ✅ | |||||
| 116 | 🌐 |
|
🌐 | |||||
| 117 | ✅ | Operational intent details retrievable | ✅ | |||||
| 118 | ✅ | Operational intent details data format | ✅ | |||||
| 119 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | |||||
| 120 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | |||||
| 121 | ✅ | Correct operational intent details | ✅ | |||||
| 122 | ✅ | Operational intent details extents are contained within reference extents | ✅ | |||||
| 123 | ✅ | Off-nominal volumes | ✅ | |||||
| 124 | ✅ | Vertices | ✅ | |||||
| Plan Flight 2 | 125 | 🌐 |
|
🌐 | ||||
| 126 | ✅ | DSS responses | ✅ | |||||
| 127 | 🌐 |
|
🌐 | |||||
| 128 | 🛑 |
Successful planning
[127]
Error from sait when attempting to submit a flight intent (flight ID: None) Attempt to plan flight returned status 401 rather than 200 as expected Stack trace: Traceback (most recent call last): File "/app/monitoring/uss_qualifier/scenarios/flight_planning/test_steps.py", line 377, in request_flight resp = flight_planner.try_plan_flight( flight_info, ExecutionStyle.IfAllowed, additional_fields ) File "/app/monitoring/monitorlib/clients/flight_planning/client_v1.py", line 122, in try_plan_flight return self._inject( ~~~~~~~~~~~~^ str(uuid.uuid4()), flight_info, execution_style, additional_fields ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/app/monitoring/monitorlib/clients/flight_planning/client_v1.py", line 77, in _inject raise PlanningActivityError( ...<2 lines>... ) monitoring.monitorlib.clients.flight_planning.client.PlanningActivityError: Attempt to plan flight returned status 401 rather than 200 as expected During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/app/monitoring/uss_qualifier/scenarios/flight_planning/test_steps.py", line 286, in submit_flight resp, query, flight_id = request_flight( ~~~~~~~~~~~~~~^ flight_planner, flight_info, flight_id, additional_fields ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/app/monitoring/uss_qualifier/scenarios/flight_planning/test_steps.py", line 381, in request_flight raise QueryError(str(e), e.queries) monitoring.monitorlib.fetch.QueryError: Attempt to plan flight returned status 401 rather than 200 as expected |
🛑 | |||||
| Cleanup | 129 | 🌐 |
|
🌐 | ||||
| 130 | ⚠️ |
Successful flight deletion
[129]
Failed to clean up flight a301a1e0-8616-4291-897c-85799d8ca367 from sait Attempt to delete flight plan returned status 401 rather than 200 as expected Stack trace: Traceback (most recent call last): File "/app/monitoring/uss_qualifier/scenarios/flight_planning/test_steps.py", line 458, in cleanup_flights resp = flight_planner.try_end_flight( flight_id, ExecutionStyle.IfAllowed ) File "/app/monitoring/monitorlib/clients/flight_planning/client_v1.py", line 156, in try_end_flight raise PlanningActivityError( ...<2 lines>... ) monitoring.monitorlib.clients.flight_planning.client.PlanningActivityError: Attempt to delete flight plan returned status 401 rather than 200 as expected |
⚠️ | |||||
| 131 | 🌐 |
|
🌐 | |||||
| 132 | ✅ | Successful flight deletion | ✅ | |||||