tested_uss provided by instance 1 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 | airmarket | iart_dss | mock_uss | ||
|---|---|---|---|---|---|---|---|
| 1 | 📓 |
Tested USS: airmarket
|
|||||
| 2 | 📓 |
Mock USS: mock_uss
|
|||||
| Activated operational intent receives notification of relevant intent | Tested_uss plans and activates Flight 1 | 3 | 🌐 |
|
🌐 | ||
| 4 | ✅ | DSS responses | ✅ | ||||
| 5 | 🌐 |
|
🌐 | ||||
| 6 | ✅ | Failure | ✅ | ||||
| 7 | ✅ | Successful planning | ✅ | ||||
| 8 | 🌐 |
|
🌐 | ||||
| 9 | ✅ | DSS responses | ✅ | ||||
| 10 | ✅ | Operational intent shared correctly | ✅ | ||||
| 11 | ✅ | Operational intent state is correct | ✅ | ||||
| 12 | 🌐 |
|
🌐 | ||||
| 13 | ✅ | Operational intent details retrievable | ✅ | ||||
| 14 | ✅ | Operational intent details data format | ✅ | ||||
| 15 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 16 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 17 | ✅ | Correct operational intent details | ✅ | ||||
| 18 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 19 | ✅ | Off-nominal volumes | ✅ | ||||
| 20 | ✅ | Vertices | ✅ | ||||
| 21 | 🌐 |
|
🌐 | ||||
| 22 | ✅ | DSS responses | ✅ | ||||
| 23 | 🌐 |
|
🌐 | ||||
| 24 | ✅ | Failure | ✅ | ||||
| 25 | ✅ | Successful activation | ✅ | ||||
| 26 | 🌐 |
|
🌐 | ||||
| 27 | ✅ | DSS responses | ✅ | ||||
| 28 | ✅ | Operational intent for active flight not deleted | ✅ | ||||
| 29 | ✅ | Operational intent shared correctly | ✅ | ||||
| 30 | ✅ | Operational intent state is correct | ✅ | ||||
| 31 | 🌐 |
|
🌐 | ||||
| 32 | ✅ | Operational intent details retrievable | ✅ | ||||
| 33 | ✅ | Operational intent details data format | ✅ | ||||
| 34 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 35 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 36 | ✅ | Correct operational intent details | ✅ | ||||
| 37 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 38 | ✅ | Off-nominal volumes | ✅ | ||||
| 39 | ✅ | Vertices | ✅ | ||||
| Mock_uss plans Flight 2 | 40 | 🌐 |
|
🌐 | |||
| 41 | ✅ | mock_uss clock time retrievable | ✅ | ||||
| 42 | 🌐 |
|
🌐 | ||||
| 43 | ✅ | DSS responses | ✅ | ||||
| 44 | 🌐 |
|
🌐 | ||||
| 45 | ✅ | Failure | ✅ | ||||
| 46 | 🛑 |
Successful planning
[44]
Flight planning activity unexpectedly PlanningActivityResult.Rejected leaving flight plan FlightPlanStatus.NotPlanned mock_uss indicated flight planning activity PlanningActivityResult.Rejected leaving flight plan FlightPlanStatus.NotPlanned rather than the expected (Activity Completed, flight plan Planned) with notes "Requested flight (priority 0) intersected Mock USS's operational intent 3954d227-8aad-44c1-9f64-a348c8aba4bf (priority 0)" |
🛑 | ||||
| Cleanup | 47 | 🌐 |
|
🌐 | |||
| 48 | ✅ | Successful flight deletion | ✅ | ||||