[tests-only] Adjust scenarios in sharedFolderWithMultipleUsersAdvancedPermissions #4419
Conversation
This file contains 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
…now that issue-product-203 is fixed
phil-davis
changed the title
|
Note: this is the first thing that I noticed, and caused me to raise issue #4418 |
This was referenced Dec 4, 2020
individual-it
approved these changes
Dec 4, 2020
delete-merged-branch
bot
deleted the
adjust-scenario-for-issue-product-203-20201204
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…now that issue-product-203 is fixed
Description
PR #4413 moved to an OCIS commit id where issue-product-203 is fixed (or at least improved). The scenario concerned was adjusted to the new correct behaviour. Actually the good scenario above it should now be used.
This PR put the Examples that pass on both oC10 and OCIS into a single "good behaviour" scenario outline.
Examples that still only pass on oC10 are in a 2nd scenario tagged
skipOnOCISExamples of bad behaviour on OCIS due to issue-ocis-717 are in a 3rd scenario tagged
skipOnOC10Related Issue
#4418
How Has This Been Tested?
CI
Types of changes
Checklist: