mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-07-20 20:44:51 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #9418 from owncloud/move-file/folder-secure-view

Browse Source 
[tests-only][full-ci] extend test for trying to move file/folder within shared folder with secure view role
This commit is contained in:
Sawjan Gurung
2024-06-21 14:13:43 +05:45
committed by GitHub
parent 55400d665e 4f2bb0c68e
commit 981d94295f
1 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
tests/acceptance/features/coreApiShareManagementToShares/moveReceivedShare.feature
View File

@@ -201,15 +201,16 @@ Feature: sharing
But as "Alice" file "/folderToShare/fileInside" should not exist
Scenario: receiver tries to rename a received share with read permissions inside the Shares folder
Scenario Outline: receiver tries to rename a received share with read permissions inside the Shares folder
Given user "Alice" has created folder "folderToShare"
And user "Alice" has created folder "folderToShare/folderInside"
And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/folderToShare/fileInside"
And user "Alice" has sent the following resource share invitation:
| resource | folderToShare |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
| resource | folderToShare |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | <permissions-role> |
When user "Brian" moves folder "/Shares/folderToShare" to "/Shares/myFolder" using the WebDAV API
Then the HTTP status code should be "201"
And as "Brian" folder "/Shares/myFolder" should exist
@@ -218,6 +219,14 @@ Feature: sharing
Then the HTTP status code should be "403"
And as "Brian" file "/Shares/myFolder/renamedFile" should not exist
But as "Brian" file "Shares/myFolder/fileInside" should exist
When user "Brian" moves folder "/Shares/myFolder/folderInside" to "/Shares/myFolder/renamedFolder" using the WebDAV API
Then the HTTP status code should be "403"
And as "Brian" folder "/Shares/myFolder/renamedFolder" should not exist
But as "Brian" folder "Shares/myFolder/folderInside" should exist
Examples:
| permissions-role |
| Viewer |
| Secure viewer |
Scenario: receiver renames a received folder share to a different name on the same folder