tested_uss provided by instance 4 in flight_planners in top-level resource poolmock_uss provided by mock_uss in top-level resource pooldss provided by dss in top-level resource poolflight_intents provided by non_conflicting_flights in top-level resource pool| Case | Step | Event | iart_dss | mock_uss | onesky | ||
|---|---|---|---|---|---|---|---|
| 1 | 📓 |
Tested USS: onesky
|
|||||
| Successfully plan flight near an existing flight | mock_uss plans flight 2 | 2 | 🌐 |
|
🌐 | ||
| 3 | ✅ | mock_uss clock time retrievable | ✅ | ||||
| 4 | 🌐 |
|
🌐 | ||||
| 5 | ✅ | DSS responses | ✅ | ||||
| 6 | 🌐 |
|
🌐 | ||||
| 7 | ✅ | Failure | ✅ | ||||
| 8 | ✅ | Injection fidelity | ✅ | ||||
| 9 | ✅ | Successful planning | ✅ | ||||
| 10 | 🌐 |
|
🌐 | ||||
| 11 | ✅ | DSS responses | ✅ | ||||
| 12 | ✅ | Operational intent shared correctly | ✅ | ||||
| 13 | ✅ | Operational intent state is correct | ✅ | ||||
| 14 | 🌐 |
|
🌐 | ||||
| 15 | ✅ | Operational intent details retrievable | ✅ | ||||
| 16 | ✅ | Operational intent details data format | ✅ | ||||
| 17 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 18 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 19 | ✅ | Correct operational intent details | ✅ | ||||
| 20 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 21 | ✅ | Off-nominal volumes | ✅ | ||||
| 22 | ✅ | Vertices | ✅ | ||||
| tested_uss plans flight 1 | 23 | 🌐 |
|
🌐 | |||
| 24 | ✅ | mock_uss clock time retrievable | ✅ | ||||
| 25 | 🌐 |
|
🌐 | ||||
| 26 | ✅ | DSS responses | ✅ | ||||
| 27 | 🌐 |
|
🌐 | ||||
| 28 | 🌐 |
|
🌐 | ||||
| 29 | 🛑 |
Successful planning
[28]
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 | 30 | 🌐 |
|
🌐 | |||
| 31 | ✅ | Successful flight deletion | ✅ | ||||
| 32 | 🌐 |
|
🌐 | ||||
| 33 | ✅ | Successful flight deletion | ✅ | ||||