| Case | Step | Event | airmarket | iart_dss | onesky | <None> | ||
|---|---|---|---|---|---|---|---|---|
| 1 | 📓 |
Tested USS: onesky
|
||||||
| 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 | ✅ | 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 | 🌐 |
|
🌐 | |||||
| 28 | 🛑 |
Incorrectly planned
[27]
Error from onesky 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 | 29 | 🌐 |
|
🌐 | ||||
| 30 | ✅ | Successful flight deletion | ✅ | |||||
| 31 | 🌐 |
|
🌐 | |||||
| 32 | ✅ | Successful flight deletion | ✅ | |||||