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

Merge pull request #9218 from owncloud/use-sharingNG-in-coreApiShareUpdateToShares

Browse Source 
[tests-only] [full-ci] Update given step using sharingNg in coreApiShareUpdateToShares
This commit is contained in:
Prarup Gurung
2024-05-21 12:33:19 +05:45
committed by GitHub
parent 12d2322366 1c4b5ef9cc
commit aef36cc7cb
4 changed files with 83 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/config/behat-core.yml
+1
View File
@@ -164,6 +164,7 @@ default:
- PublicWebDavContext: - PublicWebDavContext:
- TrashbinContext: - TrashbinContext:
- WebDavPropertiesContext: - WebDavPropertiesContext:
- SharingNgContext:
coreApiTrashbin: coreApiTrashbin:
paths: paths:
tests/acceptance/expected-failures-API-on-OCIS-storage.md
+2 -3
View File
@@ -138,9 +138,8 @@ cannot share a folder with create permission
#### [Edit user share response has a "name" field](https://github.com/owncloud/ocis/issues/1225) #### [Edit user share response has a "name" field](https://github.com/owncloud/ocis/issues/1225)
- [coreApiShareUpdateToShares/updateShare.feature:161](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L161) - [coreApiShareUpdateToShares/updateShare.feature:201](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L201)
- [coreApiShareUpdateToShares/updateShare.feature:162](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L162) - [coreApiShareUpdateToShares/updateShare.feature:202](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L202)
#### [deleting a share with wrong authentication returns OCS status 996 / HTTP 500](https://github.com/owncloud/ocis/issues/1229) #### [deleting a share with wrong authentication returns OCS status 996 / HTTP 500](https://github.com/owncloud/ocis/issues/1229)
tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature
+54 -8
View File
@@ -16,7 +16,13 @@ Feature: sharing
And group "grp1" has been created And group "grp1" has been created
And user "Brian" has been added to group "grp1" And user "Brian" has been added to group "grp1"
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
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 | File Editor |
And using SharingNG
And user "Brian" has moved file "/Shares/textfile0.txt" to "/Shares/textfile_new.txt" And user "Brian" has moved file "/Shares/textfile0.txt" to "/Shares/textfile_new.txt"
When user "Alice" updates the last share using the sharing API with When user "Alice" updates the last share using the sharing API with
| permissions | read | | permissions | read |
@@ -46,7 +52,13 @@ Feature: sharing
Given using OCS API version "<ocs-api-version>" Given using OCS API version "<ocs-api-version>"
And group "grp1" has been created And group "grp1" has been created
And user "Alice" has created folder "/FOLDER" And user "Alice" has created folder "/FOLDER"
And user "Alice" has shared folder "/FOLDER" with group "grp1" And user "Alice" has sent the following resource share invitation:
| resource | FOLDER |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Viewer |
And using SharingNG
When user "Alice" updates the last share using the sharing API with When user "Alice" updates the last share using the sharing API with
| permissions | 0 | | permissions | 0 |
Then the OCS status code should be "400" Then the OCS status code should be "400"
@@ -61,7 +73,13 @@ Feature: sharing
Given using OCS API version "<ocs-api-version>" Given using OCS API version "<ocs-api-version>"
And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has uploaded file "filesForUpload/textfile.txt" 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 "Alice" updates the last share using the sharing API with When user "Alice" updates the last share using the sharing API with
| permissions | <permissions> | | permissions | <permissions> |
Then the OCS status code should be "400" Then the OCS status code should be "400"
@@ -84,7 +102,13 @@ Feature: sharing
And group "grp1" has been created And group "grp1" has been created
And user "Brian" has been added to group "grp1" And user "Brian" has been added to group "grp1"
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
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 "Alice" updates the last share using the sharing API with When user "Alice" updates the last share using the sharing API with
| permissions | <permissions> | | permissions | <permissions> |
Then the OCS status code should be "400" Then the OCS status code should be "400"
@@ -109,8 +133,18 @@ Feature: sharing
And user "Alice" has created folder "/Alice-folder" And user "Alice" has created folder "/Alice-folder"
And user "Alice" has created folder "/Alice-folder/folder2" And user "Alice" has created folder "/Alice-folder/folder2"
And user "Carol" has created folder "/Carol-folder" And user "Carol" has created folder "/Carol-folder"
And user "Alice" has shared folder "/Alice-folder" with user "Brian" with permissions "all" And user "Alice" has sent the following resource share invitation:
And user "Carol" has shared folder "/Carol-folder" with user "Brian" with permissions "all" | resource | Alice-folder |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
And user "Carol" has sent the following resource share invitation:
| resource | Carol-folder |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
When user "Brian" moves folder "/Shares/Alice-folder/folder2" to "/Shares/Carol-folder/folder2" using the WebDAV API When user "Brian" moves folder "/Shares/Alice-folder/folder2" to "/Shares/Carol-folder/folder2" using the WebDAV API
Then the HTTP status code should be "502" Then the HTTP status code should be "502"
@@ -120,7 +154,13 @@ Feature: sharing
Given using OCS API version "<ocs-api-version>" Given using OCS API version "<ocs-api-version>"
And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has been created with default attributes and without skeleton files
And user "Alice" has created folder "/Alice-folder" And user "Alice" has created folder "/Alice-folder"
And user "Alice" has shared folder "/Alice-folder" with user "Brian" with permissions "read" And user "Alice" has sent the following resource share invitation:
| resource | Alice-folder |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
And using SharingNG
When user "Alice" updates the last share using the sharing API with When user "Alice" updates the last share using the sharing API with
| permissions | all | | permissions | all |
Then the OCS status code should be "<ocs-status-code>" Then the OCS status code should be "<ocs-status-code>"
@@ -170,7 +210,13 @@ Feature: sharing
And user "Brian" has been added to group "grp1" And user "Brian" has been added to group "grp1"
And user "Carol" has been added to group "grp1" And user "Carol" has been added to group "grp1"
And user "Carol" has created folder "/FOLDER" And user "Carol" has created folder "/FOLDER"
And user "Carol" has shared folder "/FOLDER" with group "grp1" And user "Carol" has sent the following resource share invitation:
| resource | FOLDER |
| space | Personal |
| sharee | grp1 |
| shareType | group |
| permissionsRole | Editor |
And using SharingNG
And user "Carol" has updated the last share with And user "Carol" has updated the last share with
| permissions | read | | permissions | read |
When user "Carol" updates the last share using the sharing API with When user "Carol" updates the last share using the sharing API with
tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature
+26 -4
View File
@@ -18,8 +18,19 @@ Feature: updating shares to users and groups that have the same name
Scenario Outline: update permissions of a user share with a user and a group having the same name Scenario Outline: update permissions of a user share with a user and a group having the same name
Given using OCS API version "<ocs-api-version>" Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared folder "/TMP" with group "Brian" And user "Alice" has sent the following resource share invitation:
And user "Alice" has shared folder "/TMP" with user "Brian" | resource | TMP |
| space | Personal |
| sharee | Brian |
| shareType | group |
| permissionsRole | Editor |
And user "Alice" has sent the following resource share invitation:
| resource | TMP |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
And using SharingNG
When user "Alice" updates the last share using the sharing API with When user "Alice" updates the last share using the sharing API with
| permissions | read | | permissions | read |
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
@@ -36,8 +47,19 @@ Feature: updating shares to users and groups that have the same name
Scenario Outline: update permissions of a group share with a user and a group having the same name Scenario Outline: update permissions of a group share with a user and a group having the same name
Given using OCS API version "<ocs-api-version>" Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared folder "/TMP" with user "Brian" And user "Alice" has sent the following resource share invitation:
And user "Alice" has shared folder "/TMP" with group "Brian" | resource | TMP |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
And user "Alice" has sent the following resource share invitation:
| resource | TMP |
| space | Personal |
| sharee | Brian |
| shareType | group |
| permissionsRole | Editor |
And using SharingNG
When user "Alice" updates the last share using the sharing API with When user "Alice" updates the last share using the sharing API with
| permissions | read | | permissions | read |
Then the HTTP status code should be "200" Then the HTTP status code should be "200"