Skip to content

[uss_qualifier/conflict_equal_priority] Test conflicts with planned flight - #1854

Open
the-glu wants to merge 1 commit into
interuss:mainfrom
Orbitalize:fix_1836
Open

the-glu wants to merge 1 commit into
interuss:mainfrom
Orbitalize:fix_1836

Conversation

@the-glu

@the-glu the-glu commented Oct 27, 2026

Copy link
Copy Markdown
Member

This PR fixes #1836 by running 'conflict_equal_priority' tests with a planned flight.

This is mostly a copy-paste of existing tests and descriptions of the part with an activated flight, with slightly changed wording.

Tested with a special mock-uss that ignores planned flights for conflicts and works as expected.


self.begin_test_step("Activate Flight 2")
flight2_activated = self.resolve_flight(self.equal_prio_flight2_activated)
if activate_flight2:

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note to reviewers: the diff is strange but that only a tabulated block for the if.

## Attempt to plan flight into conflict test case

## Attempt to plan flight into conflict with planned flight test case
![Test case summary illustration](assets/attempt_to_plan_flight_into_conflict.svg)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of the subtle distinctions between different cases/steps are hard to keep track of or understand, so I think the accuracy of the pictures is very important. The convention for the pictures is that a planned/Accepted flight is colored gray while an Activated flight is colored green. So, most of the pictures in the additions of this PR should be new ones with Flight 2 as gray.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

SCD Test Automation: Gap regarding Conflicting Operation State Permutations

2 participants