| Case | Step | Event | airmarket | iart_dss | <None> | ||
|---|---|---|---|---|---|---|---|
| 1 | 📓 |
Tested USS: airmarket
|
|||||
| 2 | 📓 |
Control USS: airmarket
|
|||||
| 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 | 🌐 |
|
🌐 | ||||
| 10 | ✅ | Failure | ✅ | ||||
| 11 | ✅ | Successful planning | ✅ | ||||
| 12 | 🌐 |
|
🌐 | ||||
| 13 | ✅ | DSS responses | ✅ | ||||
| 14 | ✅ | Operational intent shared correctly | ✅ | ||||
| 15 | ✅ | Operational intent state is correct | ✅ | ||||
| 16 | 🌐 |
|
🌐 | ||||
| 17 | ✅ | Operational intent details retrievable | ✅ | ||||
| 18 | ✅ | Operational intent details data format | ✅ | ||||
| 19 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 20 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 21 | ✅ | Correct operational intent details | ✅ | ||||
| 22 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 23 | ✅ | Off-nominal volumes | ✅ | ||||
| 24 | ✅ | Vertices | ✅ | ||||
| Attempt to plan Flight 1 | 25 | 🌐 |
|
🌐 | |||
| 26 | ✅ | DSS responses | ✅ | ||||
| 27 | 🌐 |
|
🌐 | ||||
| 28 | ✅ | Failure | ✅ | ||||
| 29 | ✅ | Incorrectly planned | ✅ | ||||
| 30 | 🌐 |
|
🌐 | ||||
| 31 | ✅ | DSS responses | ✅ | ||||
| 32 | ✅ | Operational intent not shared | ✅ | ||||
| Delete Flight 2 | 33 | 🌐 |
|
🌐 | |||
| 34 | ✅ | Successful deletion | ✅ | ||||
| Attempt to modify planned flight in conflict | Plan Flight 1 | 35 | 🌐 |
|
🌐 | ||
| 36 | ✅ | DSS responses | ✅ | ||||
| 37 | 🌐 |
|
🌐 | ||||
| 38 | 🌐 |
|
🌐 | ||||
| 39 | ✅ | Failure | ✅ | ||||
| 40 | ✅ | Successful planning | ✅ | ||||
| 41 | 🌐 |
|
🌐 | ||||
| 42 | ✅ | DSS responses | ✅ | ||||
| 43 | ✅ | Operational intent shared correctly | ✅ | ||||
| 44 | ✅ | Operational intent state is correct | ✅ | ||||
| 45 | 🌐 |
|
🌐 | ||||
| 46 | ✅ | Operational intent details retrievable | ✅ | ||||
| 47 | ✅ | Operational intent details data format | ✅ | ||||
| 48 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 49 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 50 | ✅ | Correct operational intent details | ✅ | ||||
| 51 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 52 | ✅ | Off-nominal volumes | ✅ | ||||
| 53 | ✅ | Vertices | ✅ | ||||
| Plan Flight 2 | 54 | 🌐 |
|
🌐 | |||
| 55 | ✅ | Retrieve pre-existing notifications | ✅ | ||||
| 56 | 🌐 |
|
🌐 | ||||
| 57 | ✅ | Retrieve pre-existing notifications | ✅ | ||||
| 58 | 🌐 |
|
🌐 | ||||
| 59 | ✅ | DSS responses | ✅ | ||||
| 60 | 🌐 |
|
🌐 | ||||
| 61 | 🌐 |
|
🌐 | ||||
| 62 | ✅ | Failure | ✅ | ||||
| 63 | ✅ | Successful planning | ✅ | ||||
| 64 | 🌐 |
|
🌐 | ||||
| 65 | ✅ | DSS responses | ✅ | ||||
| 66 | ✅ | Operational intent shared correctly | ✅ | ||||
| 67 | ✅ | Operational intent state is correct | ✅ | ||||
| 68 | 🌐 |
|
🌐 | ||||
| 69 | ✅ | Operational intent details retrievable | ✅ | ||||
| 70 | ✅ | Operational intent details data format | ✅ | ||||
| 71 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 72 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 73 | ✅ | Correct operational intent details | ✅ | ||||
| 74 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 75 | ✅ | Off-nominal volumes | ✅ | ||||
| 76 | ✅ | Vertices | ✅ | ||||
| Check for conflict notifications | 79 | 🌐 |
|
🌐 | |||
| 80 | ✅ | Retrieve notifications | ✅ | ||||
| 81 | 📓 |
scd0090_notification: airmarket notification latency: >0s
|
|||||
| 82 | 📓 |
scd0095_notification: airmarket notification latency: >0s
|
|||||
| Attempt to modify planned Flight 1 in conflict | 83 | 🌐 |
|
🌐 | |||
| 84 | ✅ | DSS responses | ✅ | ||||
| 85 | 🌐 |
|
🌐 | ||||
| 86 | ✅ | Failure | ✅ | ||||
| 87 | ✅ | Incorrectly modified | ✅ | ||||
| 88 | 🌐 |
|
🌐 | ||||
| 89 | ✅ | DSS responses | ✅ | ||||
| 90 | ✅ | Operational intent shared correctly | ✅ | ||||
| 91 | ✅ | Operational intent state is correct | ✅ | ||||
| 92 | 🌐 |
|
🌐 | ||||
| 93 | ✅ | Operational intent details retrievable | ✅ | ||||
| 94 | ✅ | Operational intent details data format | ✅ | ||||
| 95 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 96 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 97 | ✅ | Correct operational intent details | ✅ | ||||
| 98 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 99 | ✅ | Off-nominal volumes | ✅ | ||||
| 100 | ✅ | Vertices | ✅ | ||||
| Attempt to activate flight in conflict | Attempt to activate conflicting Flight 1 | 101 | 🌐 |
|
🌐 | ||
| 102 | ✅ | DSS responses | ✅ | ||||
| 103 | 🌐 |
|
🌐 | ||||
| 104 | ✅ | Failure | ✅ | ||||
| 105 | ✅ | Incorrectly activated | ✅ | ||||
| 106 | 🌐 |
|
🌐 | ||||
| 107 | ✅ | DSS responses | ✅ | ||||
| 108 | ✅ | Operational intent shared correctly | ✅ | ||||
| 109 | ✅ | Operational intent state is correct | ✅ | ||||
| 110 | 🌐 |
|
🌐 | ||||
| 111 | ✅ | Operational intent details retrievable | ✅ | ||||
| 112 | ✅ | Operational intent details data format | ✅ | ||||
| 113 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 114 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 115 | ✅ | Correct operational intent details | ✅ | ||||
| 116 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 117 | ✅ | Off-nominal volumes | ✅ | ||||
| 118 | ✅ | Vertices | ✅ | ||||
| Modify activated flight with pre-existing conflict | Delete Flight 2 | 119 | 🌐 |
|
🌐 | ||
| 120 | ✅ | Successful deletion | ✅ | ||||
| Activate Flight 1 | 121 | 🌐 |
|
🌐 | |||
| 122 | ✅ | DSS responses | ✅ | ||||
| 123 | 🌐 |
|
🌐 | ||||
| 124 | ✅ | Failure | ✅ | ||||
| 125 | ✅ | Successful activation | ✅ | ||||
| 126 | 🌐 |
|
🌐 | ||||
| 127 | ✅ | DSS responses | ✅ | ||||
| 128 | ✅ | Operational intent for active flight not deleted | ✅ | ||||
| 129 | ✅ | Operational intent shared correctly | ✅ | ||||
| 130 | ✅ | Operational intent state is correct | ✅ | ||||
| 131 | 🌐 |
|
🌐 | ||||
| 132 | ✅ | Operational intent details retrievable | ✅ | ||||
| 133 | ✅ | Operational intent details data format | ✅ | ||||
| 134 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 135 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 136 | ✅ | Correct operational intent details | ✅ | ||||
| 137 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 138 | ✅ | Off-nominal volumes | ✅ | ||||
| 139 | ✅ | Vertices | ✅ | ||||
| Plan Flight 2 | 140 | 🌐 |
|
🌐 | |||
| 141 | ✅ | DSS responses | ✅ | ||||
| 142 | 🌐 |
|
🌐 | ||||
| 143 | 🌐 |
|
🌐 | ||||
| 144 | 🛑 |
Successful planning
[143]
Error from airmarket when attempting to submit a flight intent (flight ID: None) Attempt to plan flight returned status 999 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 999 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 999 rather than 200 as expected |
🛑 | ||||
| Cleanup | 145 | 🌐 |
|
🌐 | |||
| 146 | ✅ | Successful flight deletion | ✅ | ||||
| 147 | 🌐 |
|
🌐 | ||||
| 148 | ✅ | Successful flight deletion | ✅ | ||||