[uss_qualifier] Generate dynamic test documentation before scenario execution #1235
Conversation
This file contains hidden or 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
barroco
approved these changes
Oct 20, 2025
|
#1241 should have resolved the shell linter issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
InterUSS geospatial map comprehension and general flight authorization test scenarios perform test steps according to a resource provided in the test configuration. This is accomplished by, mid-scenario, dynamically beginning a test step not declared in the original documentation using
begin_dynamic_test_step. This mid-scenario behavior is unnecessary, however, and confusing. This PR migrates to a simpler approach where these two scenarios simply rewrite their initial parsed documentation based on the resources they receive. With this simpler approach, "dynamic" test steps are no longer needed and are therefore removed from the codebase to simplify maintenance.