mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-03-11 16:32:31 -05:00
Code Issues Packages Projects Releases Wiki Activity

[tests-only] [full-ci] Use sharingNg in coreApiShareOperationsToShares1 (#9162)

Browse Source 
* update given step using sharingNg in accessToShare.feature

* update given step using sharingNg in changingFilesShare.feature

* update given step using sharingNg in gettingShares.feature

* update given step using sharingNg in gettingSharesPendingFiltered.feature

* update given step using sharingNg in gettingSharesReceivedFiltered.feature

* update given step using sharingNg in gettingSharesReceivedFilteredEmpty.feature

* update given step using sharingNg in gettingSharesSharedFiltered.feature

* update given step using sharingNg in gettingSharesSharedFilteredEmpty.feature
This commit is contained in:
Salipa Gurung
2024-05-15 15:20:58 +05:45
committed by GitHub
parent 3949dd5385
commit 20eda8b6e2
10 changed files with 360 additions and 112 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
tests/acceptance/config/behat-core.yml
View File

@@ -114,6 +114,7 @@ default:
- TrashbinContext:
- WebDavPropertiesContext:
- SettingsContext:
- SharingNgContext:
coreApiShareOperationsToShares2:
paths:

6
tests/acceptance/features/bootstrap/Sharing.php
View File

@@ -1783,7 +1783,7 @@ trait Sharing {
* @throws Exception
*/
public function userGetsInfoOfLastShareUsingTheSharingApi(string $user, ?string $language = null):void {
$shareId = $this->getLastCreatedUserGroupShareId();
$shareId = $this->isUsingSharingNg() ? $this->shareNgGetLastCreatedUserGroupShareID() : $this->getLastCreatedUserGroupShareId();
$language = TranslationHelper::getLanguage($language);
$this->setResponse($this->getShareData($user, $shareId, $language));
$this->pushToLastStatusCodesArrays();
@@ -2254,7 +2254,7 @@ trait Sharing {
* @throws Exception
*/
public function checkingLastShareIDIsIncluded():void {
$shareId = $this->getLastCreatedUserGroupShareId();
$shareId = ($this->isUsingSharingNG()) ? $this->shareNgGetLastCreatedUserGroupShareID() : $this->getLastCreatedUserGroupShareId();
if (!$this->isFieldInResponse('id', $shareId)) {
Assert::fail(
"Share id $shareId not found in response"
@@ -2269,7 +2269,7 @@ trait Sharing {
* @throws Exception
*/
public function checkLastShareIDIsNotIncluded():void {
$shareId = $this->getLastCreatedUserGroupShareId();
$shareId = $this->isUsingSharingNG() ? $this->shareNgGetLastCreatedUserGroupShareID() : $this->getLastCreatedUserGroupShareId();
if ($this->isFieldInResponse('id', $shareId, false)) {
Assert::fail(
"Share id $shareId has been found in response"

46
tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature
View File

@@ -14,7 +14,13 @@ Feature: sharing
@smokeTest
Scenario Outline: sharee can see the share
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And using SharingNG
When user "Brian" gets all the shares shared with him using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -28,8 +34,19 @@ Feature: sharing
Scenario Outline: sharee can see the filtered share
Given using OCS API version "<ocs-api-version>"
And user "Alice" has uploaded file with content "some data" to "/textfile1.txt"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
And user "Alice" has shared file "textfile1.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | textfile1.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And using SharingNG
When user "Brian" gets all the shares shared with him that are received as file "/Shares/textfile1.txt" using the provisioning API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -43,8 +60,19 @@ Feature: sharing
Scenario Outline: sharee can't see the share that is filtered out
Given using OCS API version "<ocs-api-version>"
And user "Alice" has uploaded file with content "some data" to "/textfile1.txt"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
And user "Alice" has shared file "textfile1.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | textfile1.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And using SharingNG
When user "Brian" gets all the shares shared with him that are received as file "/Shares/textfile0.txt" using the provisioning API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -59,7 +87,13 @@ Feature: sharing
Given using OCS API version "<ocs-api-version>"
And group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has shared file "textfile0.txt" with group "grp1"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And using SharingNG
When user "Brian" gets all the shares shared with him using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"

21
tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature
View File

@@ -17,8 +17,18 @@ Feature: sharing
And user "Alice" has created folder "share2"
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
And user "Alice" has moved file "textfile0.txt" to "share1/textfile0.txt"
And user "Alice" has shared folder "/share1" with user "Brian"
And user "Alice" has shared folder "/share2" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | /share1 |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
And user "Alice" has sent the following resource share invitation:
| resource | /share2 |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
When user "Brian" moves file "/Shares/share1/textfile0.txt" to "/Shares/share2/textfile0.txt" using the WebDAV API
Then the HTTP status code should be "502"
And as "Brian" file "/Shares/share1/textfile0.txt" should exist
@@ -34,7 +44,12 @@ Feature: sharing
Scenario Outline: overwrite a received file share
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "this is the old content" to "/textfile1.txt"
And user "Alice" has shared file "/textfile1.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | textfile1.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | File Editor |
When user "Brian" uploads file with content "this is a new content" to "/Shares/textfile1.txt" using the WebDAV API
Then the HTTP status code should be "204"
And as "Brian" file "Shares/textfile1.txt" should exist

58
tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature
View File

@@ -14,7 +14,12 @@ Feature: sharing
Scenario Outline: getting all shares from a user
Given using OCS API version "<ocs-api-version>"
And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt"
And user "Alice" has shared file "file_to_share.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | file_to_share.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
When user "Alice" gets all shares shared by her using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -28,7 +33,12 @@ Feature: sharing
Scenario Outline: getting all shares of a user using another user
Given using OCS API version "<ocs-api-version>"
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
When the administrator gets all shares shared by him using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -46,8 +56,18 @@ Feature: sharing
| Carol |
| David |
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
And user "Alice" has shared file "textfile0.txt" with user "Carol"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Carol |
| shareType | user |
| permissionsRole | Viewer |
When user "Alice" gets all the shares of the file "textfile0.txt" using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -63,7 +83,13 @@ Feature: sharing
Scenario Outline: getting share info of a share
Given using OCS API version "<ocs-api-version>"
And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt"
And user "Alice" has shared file "file_to_share.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | file_to_share.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | File Editor |
And using SharingNG
When user "Alice" gets the info of the last share using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -94,7 +120,13 @@ Feature: sharing
Given using OCS API version "<ocs-api-version>"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And using SharingNG
When user "Carol" gets the info of the last share using the sharing API
Then the OCS status code should be "404"
And the HTTP status code should be "<http_status_code>"
@@ -112,7 +144,12 @@ Feature: sharing
And user "Carol" has been added to group "group0"
And user "Alice" has created folder "/PARENT"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
And user "Alice" has shared folder "/PARENT" with group "group0"
And user "Alice" has sent the following resource share invitation:
| resource | /PARENT |
| space | Personal |
| sharee | group0 |
| shareType | group |
| permissionsRole | Viewer |
When the administrator removes user "Carol" from group "group0" using the provisioning API
Then the HTTP status code should be "204"
And user "Brian" should see the following elements
@@ -127,7 +164,12 @@ Feature: sharing
Given using OCS API version "<ocs-api-version>"
And user "Alice" has created folder "/PARENT"
And user "Alice" has uploaded file with content "some data" to "/PARENT/file_to_share.txt"
And user "Alice" has shared file "/PARENT/file_to_share.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | /PARENT/file_to_share.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | File Editor |
When user "Alice" gets all shares shared by her using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"

46
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature
View File

@@ -18,20 +18,42 @@ Feature: get the pending shares filtered by type (user, group etc)
And user "Alice" has uploaded file with content "file to share with user" to "/fileToShareWithUser.txt"
And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt"
And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt"
And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /folderToShareWithPublic |
| permissions | read |
| password | %public% |
And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithUser |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithGroup |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | folderToShareWithPublic |
| space | Personal |
| permissionsRole | view |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithUser.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
And user "Alice" has sent the following resource share invitation:
| resource | /fileToShareWithGroup.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
| password | %public% |
And user "Alice" has created the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
Scenario Outline: getting pending shares received from users

46
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFiltered.feature
View File

@@ -17,18 +17,40 @@ Feature: get the received shares filtered by type (user, group etc)
And user "Alice" has uploaded file with content "file to share with user" to "/fileToShareWithUser.txt"
And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt"
And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt"
And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /folderToShareWithPublic |
| permissions | read |
| password | %public% |
And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithUser |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithGroup |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | folderToShareWithPublic |
| space | Personal |
| permissionsRole | view |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithUser.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithGroup.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
Scenario Outline: getting shares received from users

110
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature
View File

@@ -21,16 +21,28 @@ Feature: get the received shares filtered by type (user, group etc)
Scenario Outline: getting shares received from users when there are none
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /folderToShareWithPublic |
| permissions | read |
| password | %public% |
And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithGroup |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | folderToShareWithPublic |
| space | Personal |
| permissionsRole | view |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithGroup.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
When user "Brian" gets the user shares shared with him using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -43,16 +55,28 @@ Feature: get the received shares filtered by type (user, group etc)
Scenario Outline: getting shares received from groups when there are none
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
And user "Alice" has created a public link share with settings
| path | /folderToShareWithPublic |
| permissions | read |
| password | %public% |
And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithUser |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | folderToShareWithPublic |
| space | Personal |
| permissionsRole | view |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithUser.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
When user "Brian" gets the group shares shared with him using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -68,18 +92,40 @@ Feature: get the received shares filtered by type (user, group etc)
# users do not receive public links, so asking for a list of public links
# that are "shared with me" should always return an empty list.
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /folderToShareWithPublic |
| permissions | read |
| password | %public% |
And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithUser |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithGroup |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | folderToShareWithPublic |
| space | Personal |
| permissionsRole | view |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithUser.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithGroup.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
When user "Brian" gets the public link shares shared with him using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"

46
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFiltered.feature
View File

@@ -17,18 +17,40 @@ Feature: get shares filtered by type (user, group etc)
And user "Alice" has uploaded file with content "file to share with user" to "/fileToShareWithUser.txt"
And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt"
And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt"
And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /folderToShareWithPublic |
| permissions | read |
| password | %public% |
And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithUser |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithGroup |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | folderToShareWithPublic |
| space | Personal |
| permissionsRole | view |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithUser.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithGroup.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
Scenario Outline: getting shares shared to users

92
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature
View File

@@ -21,16 +21,28 @@ Feature: get shares filtered by type (user, group etc)
Scenario Outline: getting shares shared to users when there are none
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /folderToShareWithPublic |
| permissions | read |
| password | %public% |
And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithGroup |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | folderToShareWithPublic |
| space | Personal |
| permissionsRole | view |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithGroup.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
When user "Alice" gets the user shares shared by her using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -43,16 +55,28 @@ Feature: get shares filtered by type (user, group etc)
Scenario Outline: getting shares shared to groups when there are none
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
And user "Alice" has created a public link share with settings
| path | /folderToShareWithPublic |
| permissions | read |
| password | %public% |
And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithUser |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | folderToShareWithPublic |
| space | Personal |
| permissionsRole | view |
| password | %public% |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithUser.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has created the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
When user "Alice" gets the group shares shared by her using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"
@@ -65,10 +89,30 @@ Feature: get shares filtered by type (user, group etc)
Scenario Outline: getting shares shared to public links when there are none
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithUser |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | folderToShareWithGroup |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithUser.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Alice" has sent the following resource share invitation:
| resource | fileToShareWithGroup.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
When user "Alice" gets the public link shares shared by her using the sharing API
Then the OCS status code should be "<ocs-status-code>"
And the HTTP status code should be "200"