[uss_qualifier] CR/OIR sync: cleanup search/get-specific checks #1072
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
dd7cb87 to
74285ff
Compare
mickmis
approved these changes
Jul 16, 2025
| @@ -0,0 +1,58 @@ | |||
| # Synchronize operational intent reference fields test step fragment | |||
There was a problem hiding this comment.
This is now duplicated as monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/oir/sync.md still exists. I assume it was meant to rename sync.md to sync_fields.md just like for the constraint references?
There was a problem hiding this comment.
Yes this needs fixing, sync.md should be removed
74285ff to
e37385e
Compare
e37385e to
c283402
Compare
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.
OIR and CR synchronization scenarios check that entities are properly synchronized via direct access as well as via search (which additionally allows to check if the area of an entity is synchronized).
These checks happen in distinct steps which currently still reference the same documentation fragment, which leads to the situation we'd like to avoid that is described in #975.
This PR splits the
sync.mdfragment into fragments that respectively handle the direct query and the search, so no "documented but not tested" check is present in the reports for the relevant checks.Progress on #975