Enhancements of the automated testing interfaces

The aim of this page is to compile a list of enhancements needed on the automated testing interfaces used by the monitoring tools, and implemented by the USSs.

• Repository containing the interfaces
• Embedded as a git submodule in this repository

SCD interface

SCD Automated Testing Interface OpenAPI Definition

Notification to other USSs after planning a conflicting flight

Requirements SCD0050-SCD0070 specify that if a first USS plans, activates or modifies a planned or activated intent, that conflicts with another intent of equal priority from a second USS, and that this conflict is permitted, then the first USS must send a notification to the second USS.
At the moment the testing interfaces do not allow checking that this notification has been properly sent.

Notification to operator after planning a conflicting flight

Requirements SCD0090-SCD0095 specify that if a USS creates or modifies, or becomes aware of new or modified conflicting operational intent, then this USS must sends to the operator or its automation system a notification. At the moment the testing interfaces do not allow checking that this notification has been properly sent.

RID interfaces

RID Injection Automated Testing Interface OpenAPI Definition
RID Observation Automated Testing Interface OpenAPI Definition

Handling of duplicate flight IDs

See issue #4