[uss_qualifier] Add documentation for solo happy path scenario #752
Conversation
| flight_planners_source: flight_planners | ||
| roles: | ||
| - tested_uss | ||
| on_failure: Continue |
There was a problem hiding this comment.
Shouldn't it stop since this would mean a USS is not able to simply plan a flight ?
There was a problem hiding this comment.
It would probably be nice to take a specific USS out of the test if they couldn't do this basic thing (but we can't do that currently), but Abort would abort the entire test and therefore one problematic USS would prevent test coverage for other USSs even when the test coverage of the other USSs should be manageable even in the presence of the non-functional USS.
| </tr> | ||
| </table> | ||
|
|
||
| Because the scenario involves activation of intents, all activated intents must be active during the execution of the |
There was a problem hiding this comment.
This sentence is not totally clear to me. Could you please clarify?
There was a problem hiding this comment.
This text was copied over from our two existing planning scenarios -- I've updated it in all 3 places.
* Add documentation for solo happy path scenario * Improve intent timing notes 688869b
This PR begins to address #751 by adding scenario documentation for a simple, solo, happy-path flight planning test scenario. The empty test scenario implementation parses/processes inputs, but the core implementation is left to a follow-up PR.
Sequence view generation is also fixed to correctly handle a test scenario with no events.
The other .md changes are via autogeneration in
make format.