mirror of
https://github.com/opencloud-eu/opencloud.git
synced 2026-01-24 05:51:33 -05:00
73 lines
3.8 KiB
Gherkin
73 lines
3.8 KiB
Gherkin
Feature: Report test
|
|
As a user
|
|
I want to check the share REPORT response
|
|
So that I can make sure that the response contains all the relevant details for shares
|
|
|
|
Note - this feature is run in CI with ACCOUNTS_HASH_DIFFICULTY set to the default for production
|
|
See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839
|
|
|
|
Background:
|
|
Given these users have been created with default attributes and without skeleton files:
|
|
| username |
|
|
| Alice |
|
|
| Brian |
|
|
And using spaces DAV path
|
|
And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
|
|
And user "Alice" has created a space "find data" with the default quota using the Graph API
|
|
And user "Alice" has created a folder "folderMain/SubFolder1/subFOLDER2" in space "find data"
|
|
And user "Alice" has uploaded a file inside space "find data" with content "some content" to "folderMain/SubFolder1/subFOLDER2/insideTheFolder.txt"
|
|
And using new DAV path
|
|
|
|
|
|
Scenario: check the response of the found folder
|
|
Given user "Alice" has created a share inside of space "find data" with settings:
|
|
| path | folderMain |
|
|
| shareWith | Brian |
|
|
| role | viewer |
|
|
When user "Brian" searches for "SubFolder1" using the WebDAV API
|
|
Then the HTTP status code should be "207"
|
|
And the following headers should match these regular expressions
|
|
| X-Request-Id | /^[a-zA-Z]+\/[a-zA-Z]+\.feature:\d+(-\d+)?$/ |
|
|
And the "REPORT" response to user "Brian" should contain a mountpoint "folderMain" with these key and value pairs:
|
|
| key | value |
|
|
| oc:fileid | UUIDof:SubFolder1 |
|
|
| oc:file-parent | UUIDof:folderMain |
|
|
| oc:shareroot | /folderMain |
|
|
| oc:name | SubFolder1 |
|
|
| d:getcontenttype | httpd/unix-directory |
|
|
| oc:permissions | S |
|
|
| oc:size | 12 |
|
|
|
|
|
|
Scenario: check the response of the found file
|
|
Given user "Alice" has created a share inside of space "find data" with settings:
|
|
| path | folderMain |
|
|
| shareWith | Brian |
|
|
| role | editor |
|
|
When user "Brian" searches for "insideTheFolder.txt" using the WebDAV API
|
|
Then the HTTP status code should be "207"
|
|
And the following headers should match these regular expressions
|
|
| X-Request-Id | /^[a-zA-Z]+\/[a-zA-Z]+\.feature:\d+(-\d+)?$/ |
|
|
And the "REPORT" response to user "Brian" should contain a mountpoint "folderMain" with these key and value pairs:
|
|
| key | value |
|
|
| oc:fileid | UUIDof:SubFolder1/subFOLDER2/insideTheFolder.txt |
|
|
| oc:file-parent | UUIDof:SubFolder1/subFOLDER2 |
|
|
| oc:shareroot | /folderMain |
|
|
| oc:name | insideTheFolder.txt |
|
|
| d:getcontenttype | text/plain |
|
|
| oc:permissions | SD |
|
|
| d:getcontentlength | 12 |
|
|
|
|
|
|
Scenario: search for the shared folder when the share is not accepted
|
|
Given user "Brian" has disabled auto-accepting
|
|
And user "Alice" has created a share inside of space "find data" with settings:
|
|
| path | folderMain |
|
|
| shareWith | Brian |
|
|
| role | viewer |
|
|
When user "Brian" searches for "folderMain" using the WebDAV API
|
|
Then the HTTP status code should be "207"
|
|
And the following headers should match these regular expressions
|
|
| X-Request-Id | /^[a-zA-Z]+\/[a-zA-Z]+\.feature:\d+(-\d+)?$/ |
|
|
And the search result should contain "0" entries
|