tested_uss provided by instance 2 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 | sait | ||
|---|---|---|---|---|---|---|---|
| 1 | 📓 |
Tested USS: sait
|
|||||
| 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 | ✅ | Injection fidelity | ✅ | ||||
| 47 | ✅ | Successful planning | ✅ | ||||
| 48 | 🌐 |
|
🌐 | ||||
| 49 | ✅ | DSS responses | ✅ | ||||
| 50 | ✅ | Operational intent shared correctly | ✅ | ||||
| 51 | ✅ | Operational intent state is correct | ✅ | ||||
| 52 | 🌐 |
|
🌐 | ||||
| 53 | ✅ | Operational intent details retrievable | ✅ | ||||
| 54 | ✅ | Operational intent details data format | ✅ | ||||
| 55 | ✅ | Operational intent reference reported by USS matches the one published to the DSS | ✅ | ||||
| 56 | ✅ | Operational intent details have not changed without publishing a new version to the DSS | ✅ | ||||
| 57 | ✅ | Correct operational intent details | ✅ | ||||
| 58 | ✅ | Operational intent details extents are contained within reference extents | ✅ | ||||
| 59 | ✅ | Off-nominal volumes | ✅ | ||||
| 60 | ✅ | Vertices | ✅ | ||||
| Validate Flight 2 notification received by tested_uss | 61 | 🌐 |
|
🌐 | |||
| 62 | ✅ | Mock USS interactions logs retrievable | ✅ | ||||
| 63 | ✅ | Mock USS sends valid notification | ✅ | ||||
| 64 | ✅ | Tested USS receives valid notification | ✅ | ||||
| Modify Activated operational intent area and receive notification of relevant intent | Mock_uss modifies planned Flight 2 | 65 | 🌐 |
|
🌐 | ||
| 66 | ✅ | mock_uss clock time retrievable | ✅ | ||||
| 67 | 🌐 |
|
🌐 | ||||
| 68 | ✅ | DSS responses | ✅ | ||||
| 69 | 🌐 |
|
🌐 | ||||
| 70 | 🌐 |
|
🌐 | ||||
| 71 | 🛑 |
Failure
[70]
Flight planning activity PlanningActivityResult.Failed leaving flight plan FlightPlanStatus.Planned mock_uss indicated flight planning activity PlanningActivityResult.Failed leaving flight plan FlightPlanStatus.Planned rather than the expected (Activity Completed, flight plan Planned) or (Activity NotSupported, flight plan Planned) with notes "Unexpected response from remote server while sharing operational intent in DSS for flight 205c738c-b4ce-44c7-af6d-b18af4e6f8a4: updateOperationalIntentReference to /dss/v1/operational_intent_references/50cb8425-b5f5-4283-877e-b7bcbc9c0cde/WfnNExyUqtPHQZsuIeZe2dbXqmRBYF4WyDqGtnrJSVY_ failed 400: " |
🛑 | ||||
| 72 | ✅ | Successful modification | ✅ | ||||
| Cleanup | 73 | 🌐 |
|
🌐 | |||
| 74 | ⚠️ |
Successful flight deletion
[73]
Failed to clean up flight 205c738c-b4ce-44c7-af6d-b18af4e6f8a4 from mock_uss Deletion of flight 205c738c-b4ce-44c7-af6d-b18af4e6f8a4 returned a status of 'FlightPlanStatus.Planned' (Closed or NotPlanned wanted) |
⚠️ | ||||
| 75 | 🌐 |
|
🌐 | ||||
| 76 | ✅ | Successful flight deletion | ✅ | ||||