[uss_qualifier] subscription sync scenario: run content validation checks and remove not-runned ones #1071
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
Shastick
force-pushed
the
sub-sync-run-more-checks
branch
from
aac6305 to
c87de18
Compare
Shastick
changed the title
Shastick
force-pushed
the
sub-sync-run-more-checks
branch
from
c87de18 to
ac8bddc
Compare
Contributor
Author
|
For DSS0005,5, in synchronization scenarios, the report now looks like this: 
(the notification index check is handled in a separate PR) |
Shastick
force-pushed
the
sub-sync-run-more-checks
branch
from
ac8bddc to
d77d751
Compare
…checks and remove not-runned ones # Conflicts: # monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/crud/read_correct.md # monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md
Shastick
force-pushed
the
sub-sync-run-more-checks
branch
from
d77d751 to
da61bcb
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.
Some documented checks in subscription sync scenarios were documented but not verified.
For two of them the check is now conducted:
The documentation for Created Subscription is in search results is removed, it was included because the incorrect fragment was imported in the documentation. The intent of the scenario was to check for search query success, and to run synchronization-specific checks afterwards.
Progress on #975