sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[test-only] update share without permission (#8748)

Browse Source 
* update share without permission

* Update resharing.feature

* Update resharing.feature
This commit is contained in:
Viktor Scharf
2024-03-28 10:15:13 +01:00
committed by GitHub
parent e3e0a7ae39
commit 65b48d3460
4 changed files with 67 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiSpacesShares/shareSubItemOfSpace.feature
+15 -48
View File
@@ -124,6 +124,7 @@ Feature: Share a file or folder that is inside a space
| expireDate | 2042-01-01T23:59:59+0100 |
When user "Alice" changes the last share with settings:
| expireDate | 2044-01-01T23:59:59.999+01:00 |
| role | viewer |
Then the HTTP status code should be "200"
And the information about the last share for user "Brian" should include
| expiration | 2044-01-01 |
@@ -136,12 +137,25 @@ Feature: Share a file or folder that is inside a space
| role | viewer |
| expireDate | 2042-01-01T23:59:59+0100 |
When user "Alice" changes the last share with settings:
| expireDate | |
| expireDate | |
| role | viewer |
Then the HTTP status code should be "200"
And the information about the last share for user "Brian" should include
| expiration | |
Scenario: user cannot delete share role
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created a share inside of space "share sub-item" with settings:
| path | folder |
| shareWith | Brian |
| role | viewer |
| expireDate | 2042-01-01T23:59:59+0100 |
When user "Alice" changes the last share with settings:
| role | |
Then the HTTP status code should be "400"
Scenario: check the end of expiration date in user share
Given user "Alice" has created a share inside of space "share sub-item" with settings:
| path | folder |
@@ -165,50 +179,3 @@ Feature: Share a file or folder that is inside a space
When user "Alice" expires the last share
Then the HTTP status code should be "200"
And as "Brian" folder "Shares/folder" should not exist
@issue-enterprise-6423 @env-config
Scenario Outline: user cannot share items in the project space with share permission if resharing is denied
Given the config "OCIS_ENABLE_RESHARING" has been set to "false"
And user "Alice" has shared a space "share sub-item" with settings:
| shareWith | Brian |
| role | viewer |
When user "Alice" creates a share inside of space "share sub-item" with settings:
| path | folder |
| shareWith | Bob |
| role | custom |
| permissions | <permissions> |
Then the HTTP status code should be "400"
And the OCS status code should be "400"
And the OCS status message should be "resharing not supported"
Examples:
| permissions | description |
| 19 | view + edit |
| 21 | view + create |
| 23 | view + create + edit |
| 25 | view + delete |
| 27 | view + edit + delete |
| 29 | view + create + delete |
| 31 | view + create + edit +delete |
@issue-enterprise-6423 @env-config
Scenario Outline: user cannot share items in the personal space with share permission if resharing is denied
Given the config "OCIS_ENABLE_RESHARING" has been set to "false"
And user "Alice" has uploaded file with content "some content" to "/file.txt"
When user "Alice" creates a share inside of space "Alice Hansen" with settings:
| path | file.txt |
| shareWith | Bob |
| role | custom |
| permissions | <permissions> |
Then the HTTP status code should be "400"
And the OCS status code should be "400"
And the OCS status message should be "resharing not supported"
Examples:
| permissions | description |
| 19 | view + edit |
| 21 | view + create |
| 23 | view + create + edit |
| 25 | view + delete |
| 27 | view + edit + delete |
| 29 | view + create + delete |
| 31 | view + create + edit +delete |