-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tests-Only] refactor permission tests for shares folder #4104
Conversation
aa9a60a
to
7ac50b0
Compare
@phil-davis I have added all permission tests on the root folder to one suite and removed all scenario outlines. So there is only one test for each condition. These suites check the different combinations of permissions. So I thought it was wise not to run those 2 times. The tests for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to solve this discussion #4103 (comment)
two points in the discussion:
- creating a new
When
step withusing the API
- moving the "accept" steps up to the other Whens
7ac50b0
to
2540bc7
Compare
Then custom permissions "<displayed-permissions>" should be set for user "grp2" for folder "simple-folder" on the webUI | ||
And custom permissions "<displayed-permissions>" should be set for user "User Three" for folder "simple-folder" on the webUI | ||
And group "grp2" should be listed as "<displayed-role>" in the collaborators list for folder "simple-folder" on the webUI | ||
And user "User Three" should be listed as "<displayed-role>" in the collaborators list for folder "simple-folder" on the webUI | ||
And user "user2" should have received a share with these details: | ||
Then user "user2" should have received a share with these details: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then user "user2" should have received a share with these details: | |
And user "user2" should have received a share with these details: |
But not a big deal.
And as "user1" folder "simple-folder (2)" should not exist | ||
Examples: | ||
| role | displayed-role | extra-permissions | displayed-permissions | actual-permissions | | ||
# | Advanced permissions | Advanced permissions | delete | delete | read, delete | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: the detailed combinations of permissions are being done in webUISharingFolderAdvancedPermissionsGroups/shareAdvancePermissionsGroup.feature
which also has the share_folder set to Shares
- that is OK.
And as "user4" file "lorem(2).txt" should not exist | ||
Examples: | ||
| role | displayed-role | extra-permissions | displayed-permissions | actual-permissions | | ||
# | Viewer | Viewer | share | share | read, share | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: the detailed example cases are now done in the suite that has share_folder set to Shares
, so they can run on OCIS.
And as "user4" folder "simple-folder (2)" should not exist | ||
Examples: | ||
| role | displayed-role | extra-permissions | displayed-permissions | actual-permissions | | ||
# | Viewer | Viewer | share | share | read, share | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: the detailed example cases are now done in the suite that has share_folder set to Shares, so they can run on OCIS.
And as "user1" file "lorem (2).txt" should not exist | ||
Examples: | ||
| role | displayed-role | extra-permissions | displayed-permissions | actual-permissions | | ||
# | Viewer | Viewer | share | share | read, share | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: the detailed example cases are now done in the suite that has share_folder set to Shares, so they can run on OCIS.
And as "user1" folder "simple-folder (2)" should not exist | ||
Examples: | ||
| role | displayed-role | extra-permissions | displayed-permissions | actual-permissions | | ||
# | Viewer | Viewer | share | share | read, share | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: the detailed example cases are now done in the suite that has share_folder set to Shares, so they can run on OCIS.
And as "user4" folder "simple-folder (2)" should not exist | ||
Examples: | ||
| role | displayed-role | extra-permissions | displayed-permissions | actual-permissions | | ||
# | Advanced permissions | Advanced permissions | delete | delete | read, delete | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: the detailed example cases are now done in the suite that has share_folder set to Shares, so they can run on OCIS.
Then user "User One" should be listed as "<displayed-role>" in the collaborators list for folder "simple-folder" on the webUI | ||
And custom permissions "<displayed-permissions>" should be set for user "User One" for folder "simple-folder" on the webUI | ||
And user "user1" should have received a share with these details: | ||
Then user "user1" should have received a share with these details: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then user "user1" should have received a share with these details: | |
And user "user1" should have received a share with these details: |
Then user "User One" should be listed as "<displayed-role>" in the collaborators list for file "lorem.txt" on the webUI | ||
And custom permissions "<displayed-permissions>" should be set for user "User One" for file "lorem.txt" on the webUI | ||
And user "user1" should have received a share with these details: | ||
Then user "user1" should have received a share with these details: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then user "user1" should have received a share with these details: | |
And user "user1" should have received a share with these details: |
|
Description
Refactor webui test scenarios for using the Shares folder and root folder for shares.
Related Issue
Motivation and Context
Shares in ocis are received in Shares folder by default. To test that we need this refactor.
How Has This Been Tested?
🤖
Screenshots (if appropriate):
Types of changes
Checklist:
Open tasks: