[Tests-Only] Acceptance tests for issue 37883 #37889
Merged
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.
Description
Add acceptance tests that define the good behavior and demonstrate the bad behavior for issue #37883
Add test scenarios that share into a
Shares
folder and examine the response fields when the share receiver accepts the share:the expected good behavior scenarios are in
acceptSharesToSharesFolder.feature
and are taggedskipOnOcV10
because they do not currently pass on oCV10. These will run on OCIS (and we will see if OCIS passes or not)the scenarios that demonstrate the bad behavior on oCV10 are in
acceptSharesToSharesFolderOc10Issue37883.feature
and are taggednotToImplementOnOCIS
because we do not want to imitate this behavior on OCIS. Putting these scenarios in a separate feature file means that we can delete them when the issue is fixed in oCV10 and the line numbers of the good behavior scenarios in the other file will not need to change.How Has This Been Tested?
CI
Types of changes
Checklist: