flight_intents provided by che_conflicting_flights in top-level resource pooltested_uss for uss1 provided by instance 1 in all_flight_planners in top-level resource pooldss for uss1 provided by scd_dss in top-level resource poolshared_asset_coordinator provided by shared_asset_coordinator in top-level resource pool| Execution characteristic | Value |
|---|---|
| Start time | 2026-11-20 08:44:34 UTC |
| End time | 2026-11-20 08:44:34 UTC |
| Duration | 0:01 |
| Case | Step | Event | uss1 | <None> | ||
|---|---|---|---|---|---|---|
| 1 | 📓 |
Tested USS: uss1
|
||||
| Setup | Acquire exclusive DSS availability access | 2 | ✅ | DSS availability access acquired | ✅ | |
| Resolve USS ID of virtual USS | 4 | 🌐 |
|
🌐 | ||
| 5 | ✅ | Successful dummy query | ✅ | |||
| 6 | 📓 |
USS ID of virtual USS: uss_qualifier
|
||||
| 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 1 in conflict with accepted operational intent managed by down USS | Virtual USS creates conflicting operational intent | 16 | 🌐 |
|
🌐 | |
| 17 | ✅ | Operational intent successfully created | ✅ | |||
| Declare virtual USS as down at DSS | 18 | 🌐 |
|
🌐 | ||
| 19 | ✅ | USS Availability can be requested | ✅ | |||
| 20 | 🌐 |
|
🌐 | |||
| 21 | ✅ | USS Availability can be updated | ✅ | |||
| Tested USS attempts to plan Flight 1 | 22 | 🌐 |
|
🌐 | ||
| 23 | ✅ | DSS responses | ✅ | |||
| 24 | 🌐 |
|
🌐 | |||
| 25 | ✅ | Failure | ✅ | |||
| 26 | ✅ | Injection fidelity | ✅ | |||
| 27 | ✅ | Successful planning | ✅ | |||
| 28 | ✅ | Rejected planning | ✅ | |||
| 29 | 🌐 |
|
🌐 | |||
| 30 | ✅ | DSS responses | ✅ | |||
| 31 | ✅ | Operational intent shared correctly | ✅ | |||
| 32 | ✅ | Operational intent state is correct | ✅ | |||
| 33 | 🌐 |
|
🌐 | |||
| 34 | ✅ | Operational intent details retrievable | ✅ | |||
| 35 | ✅ | Operational intent details data format | ✅ | |||
| 36 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | |||
| 37 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | |||
| 38 | ✅ | Correct operational intent details | ✅ | |||
| 39 | ✅ | Operational intent details extents are contained within reference extents | ✅ | |||
| 40 | ✅ | Off-nominal volumes | ✅ | |||
| 41 | ✅ | Vertices | ✅ | |||
| Cleanup | 42 | 🌐 |
|
🌐 | ||
| 43 | ✅ | USS Availability can be requested | ✅ | |||
| 44 | 🌐 |
|
🌐 | |||
| 45 | ✅ | USS Availability can be updated | ✅ | |||
| 46 | 🌐 |
|
🌐 | |||
| 47 | ✅ | Successful flight deletion | ✅ | |||
| 48 | 🌐 |
|
🌐 | |||
| 49 | 🌐 |
|
🌐 | |||
| 50 | ✅ | Successful operational intents cleanup | ✅ | |||