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

Initial QSfera import

Browse Source
This commit is contained in:
Курнат Андрей
2026-06-07 10:20:04 +03:00
commit 2315f25754
16485 changed files with 4826827 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Server/tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature
+110
View File
@@ -0,0 +1,110 @@
@skipOnReva
Feature: sharing
As a user
I want to share resources with other users
So that they can have access to the resources
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
@smokeTest
Scenario Outline: sharee can see the share
Given using OCS API version "<ocs-api-version>"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And using SharingNG
And user "Brian" has a share "textfile0.txt" synced
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"
And the last share_id should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
@smokeTest
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 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
And user "Brian" has a share "textfile1.txt" synced
And user "Brian" has a share "textfile0.txt" synced
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"
And the last share_id should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-1257
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 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
And user "Brian" has a share "textfile0.txt" synced
And user "Brian" has a share "textfile1.txt" synced
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"
And the last share id should not be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-1289
Scenario Outline: sharee can see the group share
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 sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And using SharingNG
And user "Brian" has a share "textfile0.txt" synced
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"
And the last share_id should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Server/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature
+67
View File
@@ -0,0 +1,67 @@
@skipOnReva @issue-1289 @issue-1328
Feature: sharing
As a user
I want to move shares that I received
So that I can organise them according to my needs
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
Scenario Outline: move files between shares by same user
Given using <dav-path-version> DAV path
And user "Alice" has created folder "share1"
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 sent the following resource share invitation:
| resource | /share1 |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
And user "Brian" has a share "share1" synced
And user "Alice" has sent the following resource share invitation:
| resource | /share2 |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
And user "Brian" has a share "share2" synced
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
And as "Alice" file "share1/textfile0.txt" should exist
But as "Brian" file "/Shares/share2/textfile0.txt" should not exist
And as "Alice" file "share2/textfile0.txt" should not exist
Examples:
| dav-path-version |
| old |
| new |
| spaces |
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 sent the following resource share invitation:
| resource | textfile1.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | File Editor |
And user "Brian" has a share "textfile1.txt" synced
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
And the content of file "Shares/textfile1.txt" for user "Brian" should be "this is a new content"
And the content of file "textfile1.txt" for user "Alice" should be "this is a new content"
Examples:
| dav-path-version |
| old |
| new |
| spaces |
Server/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature
+197
View File
@@ -0,0 +1,197 @@
@skipOnReva
Feature: sharing
As a user
I want to get all the shares
So that I can know I have proper access to them
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
@smokeTest @issue-1258
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 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"
And file "/Shares/file_to_share.txt" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
@issue-1319
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 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"
And file "/Shares/textfile0.txt" should not be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
@smokeTest
Scenario Outline: getting all shares of a file
Given using OCS API version "<ocs-api-version>"
And these users have been created with default attributes:
| username |
| Carol |
| David |
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
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"
And user "Brian" should be included in the response
And user "Carol" should be included in the response
And user "David" should not be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-1226 @issue-1270 @issue-1271
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 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"
And the fields of the last response to user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| item_type | file |
| item_source | A_STRING |
| share_type | user |
| share_with | %username% |
| file_source | A_STRING |
| file_target | /Shares/file_to_share.txt |
| path | /file_to_share.txt |
| permissions | read,update |
| stime | A_NUMBER |
| storage | A_STRING |
| mail_send | 0 |
| uid_owner | %username% |
| share_with_displayname | %displayname% |
| displayname_owner | %displayname% |
| mimetype | text/plain |
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
@issue-1233
Scenario Outline: get a share with a user that didn't receive the share
Given using OCS API version "<ocs-api-version>"
And user "Carol" has been created with default attributes
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
And user "Alice" has sent the following resource share invitation:
| resource | textfile0.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And user "Brian" has a share "textfile0.txt" synced
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>"
Examples:
| ocs-api-version | http_status_code |
| 1 | 200 |
| 2 | 404 |
@issue-1289
Scenario: share a folder to a group, and remove user from that group
Given using OCS API version "1"
And user "Carol" has been created with default attributes
And group "group0" has been created
And user "Brian" has been added to group "group0"
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 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
| /Shares/PARENT |
| /Shares/PARENT/parent.txt |
But user "Carol" should not see the following elements
| /Shares/PARENT |
| /Shares/PARENT/parent.txt |
@smokeTest @issue-1226 @issue-1270 @issue-1271 @issue-1231
Scenario Outline: getting share info of a share shared from inside folder
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 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"
And the fields of the last response to user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| item_type | file |
| item_source | A_STRING |
| share_type | user |
| share_with | %username% |
| file_source | A_STRING |
| file_target | /Shares/file_to_share.txt |
| path | /PARENT/file_to_share.txt |
| permissions | read,update |
| stime | A_NUMBER |
| storage | A_STRING |
| mail_send | 0 |
| uid_owner | %username% |
| share_with_displayname | %displayname% |
| displayname_owner | %displayname% |
| mimetype | text/plain |
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Server/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature
+82
View File
@@ -0,0 +1,82 @@
@skipOnReva
Feature: get the pending shares filtered by type (user, group etc)
As a user
I want to filter the pending shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
And group "grp1" has been created
And user "Brian" has disabled auto-accepting
And user "Brian" has been added to group "grp1"
And user "Alice" has created folder "/folderToShareWithUser"
And user "Alice" has created folder "/folderToShareWithGroup"
And user "Alice" has created folder "/folderToShareWithPublic"
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 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 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 the following resource link share:
| resource | fileToShareWithPublic.txt |
| space | Personal |
| permissionsRole | view |
| password | %public% |
Scenario Outline: getting pending shares received from users
Given using OCS API version "<ocs-api-version>"
When user "Brian" gets the pending 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"
And exactly 1 file or folder should be included in the response
And folder "/Shares/folderToShareWithUser" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting pending shares received from groups
Given using OCS API version "<ocs-api-version>"
When user "Brian" gets the pending 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"
And exactly 1 file or folder should be included in the response
And folder "/Shares/folderToShareWithGroup" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Server/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFiltered.feature
+81
View File
@@ -0,0 +1,81 @@
@skipOnReva
Feature: get the received shares filtered by type (user, group etc)
As a user
I want to filter the shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
And group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has created folder "/folderToShareWithUser"
And user "Alice" has created folder "/folderToShareWithGroup"
And user "Alice" has created folder "/folderToShareWithPublic"
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 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
Given using OCS API version "<ocs-api-version>"
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"
And exactly 2 files or folders should be included in the response
And folder "/Shares/folderToShareWithUser" should be included in the response
And file "/Shares/fileToShareWithUser.txt" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting shares received from groups
Given using OCS API version "<ocs-api-version>"
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"
And exactly 2 files or folders should be included in the response
And folder "/Shares/folderToShareWithGroup" should be included in the response
And folder "/Shares/fileToShareWithGroup.txt" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Server/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature
+136
View File
@@ -0,0 +1,136 @@
@skipOnReva
Feature: get the received shares filtered by type (user, group etc)
As a user
I want to filter the shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
And group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has created folder "/folderToShareWithUser"
And user "Alice" has created folder "/folderToShareWithGroup"
And user "Alice" has created folder "/folderToShareWithPublic"
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"
Scenario Outline: getting shares received from users when there are none
Given using OCS API version "<ocs-api-version>"
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"
And no files or folders should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting shares received from groups when there are none
Given using OCS API version "<ocs-api-version>"
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"
And no files or folders should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting shares received from public links when there are none
# Note: public links are purposely created in this scenario
# 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 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"
And no files or folders should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Server/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFiltered.feature
+111
View File
@@ -0,0 +1,111 @@
@skipOnReva
Feature: get shares filtered by type (user, group etc)
As a user
I want to filter the shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
And group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has created folder "/folderToShareWithUser"
And user "Alice" has created folder "/folderToShareWithGroup"
And user "Alice" has created folder "/folderToShareWithPublic"
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 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
Given using OCS API version "<ocs-api-version>"
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"
And exactly 2 files or folders should be included in the response
And folder "/Shares/folderToShareWithUser" should be included in the response
And file "/Shares/fileToShareWithUser.txt" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting shares shared to groups
Given using OCS API version "<ocs-api-version>"
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"
And exactly 2 files or folders should be included in the response
And folder "/Shares/folderToShareWithGroup" should be included in the response
And folder "/Shares/fileToShareWithGroup.txt" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting shares shared to public links
Given using OCS API version "<ocs-api-version>"
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"
And exactly 2 files or folders should be included in the response
And folder "/folderToShareWithPublic" should be included in the response
And folder "/fileToShareWithPublic.txt" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting shares shared to users and groups
Given using OCS API version "<ocs-api-version>"
When user "Alice" gets the user and 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"
And exactly 4 files or folders should be included in the response
And folder "/Shares/folderToShareWithUser" should be included in the response
And file "/Shares/fileToShareWithUser.txt" should be included in the response
And folder "/Shares/folderToShareWithGroup" should be included in the response
And folder "/Shares/fileToShareWithGroup.txt" should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Server/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature
+123
View File
@@ -0,0 +1,123 @@
@skipOnReva
Feature: get shares filtered by type (user, group etc)
As a user
I want to filter the shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
And group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has created folder "/folderToShareWithUser"
And user "Alice" has created folder "/folderToShareWithGroup"
And user "Alice" has created folder "/folderToShareWithPublic"
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"
Scenario Outline: getting shares shared to users when there are none
Given using OCS API version "<ocs-api-version>"
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"
And no files or folders should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting shares shared to groups when there are none
Given using OCS API version "<ocs-api-version>"
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"
And no files or folders should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: getting shares shared to public links when there are none
Given using OCS API version "<ocs-api-version>"
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"
And no files or folders should be included in the response
Examples:
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |