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

update given step using sharingNg in getWebDAVSharePermissions.feature

Browse Source
This commit is contained in:
Salipa-Gurung
2024-05-20 10:50:06 +05:45
parent 25b7c7c98a
commit dc0dd9b343
2 changed files with 55 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/config/behat-core.yml
+1
View File
@@ -128,6 +128,7 @@ default:
- PublicWebDavContext: - PublicWebDavContext:
- TrashbinContext: - TrashbinContext:
- WebDavPropertiesContext: - WebDavPropertiesContext:
- SharingNgContext:
coreApiSharePublicLink1: coreApiSharePublicLink1:
paths: paths:
tests/acceptance/features/coreApiShareOperationsToShares2/getWebDAVSharePermissions.feature
+54 -8
View File
@@ -34,7 +34,12 @@ Feature: sharing
Scenario Outline: check webdav share-permissions for received file with edit Scenario Outline: check webdav share-permissions for received file with edit
Given using <dav-path-version> DAV path Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "foo" to "/tmp.txt" And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
And user "Alice" has shared file "/tmp.txt" with user "Brian" And user "Alice" has sent the following resource share invitation:
| resource | tmp.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | File Editor |
When user "Brian" gets the following properties of file "/Shares/tmp.txt" using the WebDAV API When user "Brian" gets the following properties of file "/Shares/tmp.txt" using the WebDAV API
| propertyName | | propertyName |
| ocs:share-permissions | | ocs:share-permissions |
@@ -70,7 +75,13 @@ Feature: sharing
Scenario Outline: check webdav share-permissions for received file with edit permissions but no reshare permissions Scenario Outline: check webdav share-permissions for received file with edit permissions but no reshare permissions
Given using <dav-path-version> DAV path Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "foo" to "/tmp.txt" And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
And user "Alice" has shared file "tmp.txt" with user "Brian" And user "Alice" has sent the following resource share invitation:
| resource | tmp.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 | update,read | | permissions | update,read |
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
@@ -105,7 +116,13 @@ Feature: sharing
Scenario Outline: check webdav share-permissions for received file without edit permissions Scenario Outline: check webdav share-permissions for received file without edit permissions
Given using <dav-path-version> DAV path Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "foo" to "/tmp.txt" And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
And user "Alice" has shared file "tmp.txt" with user "Brian" And user "Alice" has sent the following resource share invitation:
| resource | tmp.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 | read | | permissions | read |
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
@@ -159,7 +176,12 @@ Feature: sharing
Scenario Outline: check webdav share-permissions for received folder with all permissions Scenario Outline: check webdav share-permissions for received folder with all permissions
Given using <dav-path-version> DAV path Given using <dav-path-version> DAV path
And user "Alice" has created folder "/tmp" And user "Alice" has created folder "/tmp"
And user "Alice" has shared file "/tmp" with user "Brian" And user "Alice" has sent the following resource share invitation:
| resource | tmp |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Editor |
When user "Brian" gets the following properties of folder "/Shares/tmp" using the WebDAV API When user "Brian" gets the following properties of folder "/Shares/tmp" using the WebDAV API
| propertyName | | propertyName |
| ocs:share-permissions | | ocs:share-permissions |
@@ -194,7 +216,13 @@ Feature: sharing
Scenario Outline: check webdav share-permissions for received folder with all permissions but edit Scenario Outline: check webdav share-permissions for received folder with all permissions but edit
Given using <dav-path-version> DAV path Given using <dav-path-version> DAV path
And user "Alice" has created folder "/tmp" And user "Alice" has created folder "/tmp"
And user "Alice" has shared file "/tmp" with user "Brian" And user "Alice" has sent the following resource share invitation:
| resource | tmp |
| 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 | delete,create,read | | permissions | delete,create,read |
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
@@ -229,7 +257,13 @@ Feature: sharing
Scenario Outline: check webdav share-permissions for received folder with all permissions but create Scenario Outline: check webdav share-permissions for received folder with all permissions but create
Given using <dav-path-version> DAV path Given using <dav-path-version> DAV path
And user "Alice" has created folder "/tmp" And user "Alice" has created folder "/tmp"
And user "Alice" has shared file "/tmp" with user "Brian" And user "Alice" has sent the following resource share invitation:
| resource | tmp |
| 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 | delete,update,read | | permissions | delete,update,read |
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
@@ -264,7 +298,13 @@ Feature: sharing
Scenario Outline: check webdav share-permissions for received folder with all permissions but delete Scenario Outline: check webdav share-permissions for received folder with all permissions but delete
Given using <dav-path-version> DAV path Given using <dav-path-version> DAV path
And user "Alice" has created folder "/tmp" And user "Alice" has created folder "/tmp"
And user "Alice" has shared file "/tmp" with user "Brian" And user "Alice" has sent the following resource share invitation:
| resource | tmp |
| 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 | create,update,read | | permissions | create,update,read |
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
@@ -299,7 +339,13 @@ Feature: sharing
Scenario Outline: check webdav share-permissions for received folder with all permissions but share Scenario Outline: check webdav share-permissions for received folder with all permissions but share
Given using <dav-path-version> DAV path Given using <dav-path-version> DAV path
And user "Alice" has created folder "/tmp" And user "Alice" has created folder "/tmp"
And user "Alice" has shared file "/tmp" with user "Brian" And user "Alice" has sent the following resource share invitation:
| resource | tmp |
| 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 | change | | permissions | change |
Then the HTTP status code should be "200" Then the HTTP status code should be "200"