[full-ci] [tests-only] Use sharing-ng in given steps for sharing (#9221)
* resharing.feature: Used sharingNG for sharing in given step * unlockFiles.feature: Used sharingNG for sharing in given step * apiSpacesShares suite: Used sharingNG for sharing in given step * acceptShares.feature: Used sharingNG for sharing in given step * uploadFile.feature: Used sharingNG for sharing in given step * coreApiWebdavUploadTUS suite: Used sharingNG for sharing in given step * tag.feature: Used sharingNG for sharing in given step * coreApiShareOperationsToShares2 suite: Used sharingNG for sharing in given step * updateShare.feature: Used sharingNG for sharing in given step * Fixed line numbers in expected failure
This commit is contained in:
@@ -160,7 +160,12 @@ Feature: copy file
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <space-role> |
|
||||
And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "1"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
When user "Alice" copies file "/project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And for user "Alice" folder "testshare" of the space "Shares" should not contain these files:
|
||||
|
||||
+6
-1
@@ -9,7 +9,12 @@ Feature: create file or folder named similar to Shares folder
|
||||
| Alice |
|
||||
| Brian |
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "read,update"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | FOLDER |
|
||||
| space | Personal |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
|
||||
|
||||
Scenario Outline: create a folder with a name similar to Shares
|
||||
|
||||
@@ -62,18 +62,22 @@ Feature: Share spaces
|
||||
|
||||
|
||||
Scenario: user unshares a space
|
||||
Given user "Alice" has shared a space "share space" with settings:
|
||||
| shareWith | Brian |
|
||||
| role | viewer |
|
||||
Given user "Alice" has sent the following space share invitation:
|
||||
| space | share space |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Space Viewer |
|
||||
When user "Alice" unshares a space "share space" to user "Brian"
|
||||
Then the HTTP status code should be "200"
|
||||
But the user "Brian" should not have a space called "share space"
|
||||
|
||||
|
||||
Scenario Outline: owner of a space cannot see the space after removing his access to the space
|
||||
Given user "Alice" has shared a space "share space" with settings:
|
||||
| shareWith | Brian |
|
||||
| role | manager |
|
||||
Given user "Alice" has sent the following space share invitation:
|
||||
| space | share space |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Manager |
|
||||
When user "<user>" unshares a space "share space" to user "Alice"
|
||||
Then the HTTP status code should be "200"
|
||||
But the user "Alice" should not have a space called "share space"
|
||||
|
||||
Reference in New Issue
Block a user