fix: Assertion with EXCLUDE priority causing test result submit errors #1229
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.
Address #1228.
This seems to be a special case that happens when the assertion is excluded in tests the tests.csv and then included in *-commands.csv's
assertionExceptions
with a non-excluding priority. For example:navForwardsToMenuButton
test which excludesinteractionModeEnabled
by default and any of it's*-commands.csv
which then includesinteractionModeEnabled
usingassertionExceptions
.*-commands.csv
excludes an assertion through theassertionExceptions
instead, like in the case of modal-dialog.