-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[uss_qualifier / flight planning] Add modify flight intent test steps (…
…#50) * [uss_qualifier / flight planning] Add modify flight intents steps * align with error handling update
- Loading branch information
Showing
3 changed files
with
86 additions
and
0 deletions.
There are no files selected for viewing
17 changes: 17 additions & 0 deletions
17
...oring/uss_qualifier/scenarios/flight_planning/modify_activated_flight_intent.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Modify activated flight test step | ||
|
||
This page describes the content of a common test case where a valid user flight intent in activated state should be | ||
successfully modified by a flight planner. See `modify_activated_flight_intent` in [test_steps.py](test_steps.py). | ||
|
||
## Successful modification check | ||
|
||
All flight intent data provided is correct and valid and free of conflict in space and time, therefore it should have | ||
been modified by the USS per **interuss.automated_testing.flight_planning.ExpectedBehavior**. | ||
If the USS fails to modify the flight, wrongly indicates a conflict, or wrongly indicates the activated state of the | ||
flight, this check will fail. | ||
|
||
## Failure check | ||
|
||
All flight intent data provided was complete and correct. It should have been processed successfully, allowing the USS | ||
to reject or accept the flight. If the USS indicates that the injection attempt failed, this check will fail per | ||
**[interuss.automated_testing.flight_planning.ExpectedBehavior](../../requirements/interuss/automated_testing/flight_planning.md)**. |
17 changes: 17 additions & 0 deletions
17
monitoring/uss_qualifier/scenarios/flight_planning/modify_planned_flight_intent.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Modify planned flight test step | ||
|
||
This page describes the content of a common test case where a valid user flight intent in planned state should be | ||
successfully modified by a flight planner. See `modify_planned_flight_intent` in [test_steps.py](test_steps.py). | ||
|
||
## Successful modification check | ||
|
||
All flight intent data provided is correct and valid and free of conflict in space and time, therefore it should have | ||
been modified by the USS per **interuss.automated_testing.flight_planning.ExpectedBehavior**. | ||
If the USS fails to modify the flight, wrongly indicates a conflict, or wrongly indicates the planned state of the | ||
flight, this check will fail. | ||
|
||
## Failure check | ||
|
||
All flight intent data provided was complete and correct. It should have been processed successfully, allowing the USS | ||
to reject or accept the flight. If the USS indicates that the injection attempt failed, this check will fail per | ||
**[interuss.automated_testing.flight_planning.ExpectedBehavior](../../requirements/interuss/automated_testing/flight_planning.md)**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters