flight_intents provided by conflicting_flights in top-level resource pooltested_uss provided by instance 4 in flight_planners in top-level resource pooldss provided by dss in top-level resource pool| Case | Step | Event | iart_dss | onesky | <None> | ||
|---|---|---|---|---|---|---|---|
| 1 | 📓 |
Tested USS: onesky
|
|||||
| 2 | 📓 |
Test CMSA: Will skip nonconforming and contingent test cases because CMSA is not available for provided DSS instance
|
|||||
| Setup | Resolve USS ID of virtual USS | 4 | 🌐 |
|
🌐 | ||
| 5 | ✅ | Successful dummy query | ✅ | ||||
| 6 | 📓 |
USS ID of virtual USS: DSS Qualifer1
|
|||||
| Restore virtual USS availability | 7 | 🌐 |
|
🌐 | |||
| 8 | ✅ | USS Availability can be requested | ✅ | ||||
| 9 | 🌐 |
|
🌐 | ||||
| 10 | ✅ | USS Availability can be updated | ✅ | ||||
| Clear operational intents created by virtual USS | 11 | 🌐 |
|
🌐 | |||
| 12 | ✅ | Successful operational intents cleanup | ✅ | ||||
| Verify area is clear | 13 | 🌐 |
|
🌐 | |||
| 14 | ✅ | DSS responses | ✅ | ||||
| 15 | ✅ | Area is clear of op intents | ✅ | ||||
| Plan Flight 2 in conflict with activated operational intent managed by down USS | Virtual USS creates conflicting operational intent | 16 | 🌐 |
|
🌐 | ||
| 17 | ✅ | Operational intent successfully created | ✅ | ||||
| Virtual USS activates conflicting operational intent | 18 | 🌐 |
|
🌐 | |||
| 19 | ✅ | Operational intent successfully activated | ✅ | ||||
| Declare virtual USS as down at DSS | 20 | 🌐 |
|
🌐 | |||
| 21 | ✅ | USS Availability can be requested | ✅ | ||||
| 22 | 🌐 |
|
🌐 | ||||
| 23 | ✅ | USS Availability can be updated | ✅ | ||||
| Tested USS attempts to plan Flight 2 | 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 | ✅ | USS Availability can be requested | ✅ | ||||
| 31 | 🌐 |
|
🌐 | ||||
| 32 | ✅ | USS Availability can be updated | ✅ | ||||
| 33 | 🌐 |
|
🌐 | ||||
| 34 | ✅ | Successful flight deletion | ✅ | ||||
| 35 | 🌐 |
|
🌐 | ||||
| 36 | 🌐 |
|
🌐 | ||||
| 37 | ✅ | Successful operational intents cleanup | ✅ | ||||