Курнат Андрей
394 lines
19 KiB
Gherkin
394 lines
19 KiB
Gherkin
@skipOnReva
|
|
Feature: update a public link share
|
|
As a user
|
|
I want to update a public link
|
|
So that I change permissions whenever I want
|
|
|
|
Background:
|
|
Given using OCS API version "1"
|
|
And user "Alice" has been created with default attributes
|
|
|
|
|
|
Scenario Outline: change expiration date of a public link share and get its info
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And user "Alice" has created folder "FOLDER"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
When user "Alice" updates the last public link share using the sharing API with
|
|
| expireDate | 2040-01-01T23:59:59+0100 |
|
|
Then the OCS status code should be "<ocs-status-code>"
|
|
And the OCS status message should be "OK"
|
|
And the HTTP status code should be "200"
|
|
And the fields of the last response to user "Alice" should include
|
|
| id | A_STRING |
|
|
| share_type | public_link |
|
|
| uid_owner | %username% |
|
|
| displayname_owner | %displayname% |
|
|
| permissions | read |
|
|
| stime | A_NUMBER |
|
|
| parent | |
|
|
| expiration | A_STRING |
|
|
| token | A_STRING |
|
|
| uid_file_owner | %username% |
|
|
| displayname_file_owner | %displayname% |
|
|
| additional_info_owner | %emailaddress% |
|
|
| additional_info_file_owner | %emailaddress% |
|
|
| item_type | folder |
|
|
| item_source | A_STRING |
|
|
| path | /FOLDER |
|
|
| mimetype | httpd/unix-directory |
|
|
| storage_id | A_STRING |
|
|
| storage | A_NUMBER |
|
|
| file_source | A_STRING |
|
|
| file_target | /FOLDER |
|
|
| mail_send | 0 |
|
|
| name | |
|
|
Examples:
|
|
| ocs-api-version | ocs-status-code |
|
|
| 1 | 100 |
|
|
| 2 | 200 |
|
|
|
|
@smokeTest
|
|
Scenario Outline: change expiration date of a newly created public link share and get its info
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And user "Alice" has created folder "FOLDER"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
And user "Alice" has updated the last resource link share with
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| expirationDateTime | 2033-01-31T23:59:59.000Z |
|
|
When user "Alice" gets the info of the last public link 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" should include
|
|
| id | A_STRING |
|
|
| item_type | folder |
|
|
| item_source | A_STRING |
|
|
| share_type | public_link |
|
|
| file_source | A_STRING |
|
|
| file_target | /FOLDER |
|
|
| permissions | read |
|
|
| stime | A_NUMBER |
|
|
| expiration | 2033-01-31 |
|
|
| token | A_TOKEN |
|
|
| storage | A_STRING |
|
|
| mail_send | 0 |
|
|
| uid_owner | %username% |
|
|
| displayname_owner | %displayname% |
|
|
| url | AN_URL |
|
|
| mimetype | httpd/unix-directory |
|
|
Examples:
|
|
| ocs-api-version | ocs-status-code |
|
|
| 1 | 100 |
|
|
| 2 | 200 |
|
|
|
|
@issue-9724 @issue-10331
|
|
Scenario Outline: creating a new public link share with password and adding an expiration date using public API
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | randomfile.txt |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
When user "Alice" updates the last public link share using the sharing API with
|
|
| expireDate | 2040-01-01T23:59:59+0100 |
|
|
Then the OCS status code should be "<ocs-status-code>"
|
|
And the HTTP status code should be "200"
|
|
And the public should be able to download file "randomfile.txt" from the last link share with password "%public%" and the content should be "Random data"
|
|
Examples:
|
|
| ocs-api-version | ocs-status-code |
|
|
| 1 | 100 |
|
|
| 2 | 200 |
|
|
|
|
|
|
Scenario Outline: creating a new public link share, updating its password and getting its info
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And user "Alice" has created folder "FOLDER"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
And user "Alice" has set the following password for the last link share:
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| password | %public% |
|
|
When user "Alice" gets the info of the last public link 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" should include
|
|
| id | A_STRING |
|
|
| item_type | folder |
|
|
| item_source | A_STRING |
|
|
| share_type | public_link |
|
|
| file_source | A_STRING |
|
|
| file_target | /FOLDER |
|
|
| permissions | read |
|
|
| stime | A_NUMBER |
|
|
| token | A_TOKEN |
|
|
| storage | A_STRING |
|
|
| mail_send | 0 |
|
|
| uid_owner | %username% |
|
|
| displayname_owner | %displayname% |
|
|
| url | AN_URL |
|
|
| mimetype | httpd/unix-directory |
|
|
Examples:
|
|
| ocs-api-version | ocs-status-code |
|
|
| 1 | 100 |
|
|
| 2 | 200 |
|
|
|
|
|
|
Scenario Outline: creating a new public link share, updating its permissions and getting its info
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And user "Alice" has created folder "FOLDER"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
And user "Alice" has updated the last resource link share with
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| permissionsRole | edit |
|
|
When user "Alice" gets the info of the last public link 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" should include
|
|
| id | A_STRING |
|
|
| item_type | folder |
|
|
| item_source | A_STRING |
|
|
| share_type | public_link |
|
|
| file_source | A_STRING |
|
|
| file_target | /FOLDER |
|
|
| permissions | read,update,create,delete |
|
|
| stime | A_NUMBER |
|
|
| token | A_TOKEN |
|
|
| storage | A_STRING |
|
|
| mail_send | 0 |
|
|
| uid_owner | %username% |
|
|
| displayname_owner | %displayname% |
|
|
| url | AN_URL |
|
|
| mimetype | httpd/unix-directory |
|
|
Examples:
|
|
| ocs-api-version | ocs-status-code |
|
|
| 1 | 100 |
|
|
| 2 | 200 |
|
|
|
|
|
|
Scenario Outline: creating a new public link share, updating its permissions to view download and upload and getting its info
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And user "Alice" has created folder "FOLDER"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
And user "Alice" has updated the last resource link share with
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| permissionsRole | upload |
|
|
When user "Alice" gets the info of the last public link 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" should include
|
|
| id | A_STRING |
|
|
| item_type | folder |
|
|
| item_source | A_STRING |
|
|
| share_type | public_link |
|
|
| file_source | A_STRING |
|
|
| file_target | /FOLDER |
|
|
| permissions | read,create |
|
|
| stime | A_NUMBER |
|
|
| token | A_TOKEN |
|
|
| storage | A_STRING |
|
|
| mail_send | 0 |
|
|
| uid_owner | %username% |
|
|
| displayname_owner | %displayname% |
|
|
| url | AN_URL |
|
|
| mimetype | httpd/unix-directory |
|
|
Examples:
|
|
| ocs-api-version | ocs-status-code |
|
|
| 1 | 100 |
|
|
| 2 | 200 |
|
|
|
|
@issue-1269 @issue-9724 @issue-10331
|
|
Scenario Outline: updating share permissions from change to read restricts public from deleting files using the public API
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And user "Alice" has created folder "PARENT"
|
|
And user "Alice" has created folder "PARENT/CHILD"
|
|
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/PARENT/CHILD/child.txt"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | PARENT |
|
|
| space | Personal |
|
|
| permissionsRole | edit |
|
|
| password | %public% |
|
|
And user "Alice" has updated the last resource link share with
|
|
| resource | PARENT |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
When the public deletes file "CHILD/child.txt" from the last link share with password "%public%" using the public WebDAV API
|
|
Then the HTTP status code of responses on all endpoints should be "403"
|
|
And as "Alice" file "PARENT/CHILD/child.txt" should exist
|
|
Examples:
|
|
| ocs-api-version |
|
|
| 1 |
|
|
| 2 |
|
|
|
|
@issue-9724 @issue-10331
|
|
Scenario Outline: updating share permissions from read to change allows public to delete files using the public API
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And user "Alice" has created folder "PARENT"
|
|
And user "Alice" has created folder "PARENT/CHILD"
|
|
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/PARENT/parent.txt"
|
|
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/PARENT/CHILD/child.txt"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | PARENT |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
And user "Alice" has updated the last resource link share with
|
|
| resource | PARENT |
|
|
| space | Personal |
|
|
| permissionsRole | edit |
|
|
When the public deletes file "CHILD/child.txt" from the last link share with password "%public%" using the public WebDAV API
|
|
And the public deletes file "parent.txt" from the last link share with password "%public%" using the public WebDAV API
|
|
Then the HTTP status code of responses on all endpoints should be "204"
|
|
And as "Alice" file "PARENT/CHILD/child.txt" should not exist
|
|
And as "Alice" file "PARENT/parent.txt" should not exist
|
|
Examples:
|
|
| ocs-api-version |
|
|
| 1 |
|
|
| 2 |
|
|
|
|
|
|
Scenario Outline: rename a folder with public link and get its info
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And using <dav-path-version> DAV path
|
|
And user "Alice" has created folder "FOLDER"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | FOLDER |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
And user "Alice" has moved folder "/FOLDER" to "/RENAMED_FOLDER"
|
|
When user "Alice" gets the info of the last public link 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" should include
|
|
| id | A_STRING |
|
|
| share_type | public_link |
|
|
| uid_owner | %username% |
|
|
| displayname_owner | %displayname% |
|
|
| permissions | read |
|
|
| stime | A_NUMBER |
|
|
| parent | |
|
|
| expiration | |
|
|
| token | A_STRING |
|
|
| uid_file_owner | %username% |
|
|
| displayname_file_owner | %displayname% |
|
|
| item_type | folder |
|
|
| item_source | A_STRING |
|
|
| path | /RENAMED_FOLDER |
|
|
| mimetype | httpd/unix-directory |
|
|
| storage_id | A_STRING |
|
|
| storage | A_STRING |
|
|
| file_source | A_STRING |
|
|
| file_target | /RENAMED_FOLDER |
|
|
| mail_send | 0 |
|
|
| name | |
|
|
Examples:
|
|
| dav-path-version | ocs-api-version | ocs-status-code |
|
|
| old | 1 | 100 |
|
|
| old | 2 | 200 |
|
|
| new | 1 | 100 |
|
|
| new | 2 | 200 |
|
|
| spaces | 1 | 100 |
|
|
| spaces | 2 | 200 |
|
|
|
|
|
|
Scenario Outline: rename a file with public link and get its info
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And using <dav-path-version> DAV path
|
|
And user "Alice" has uploaded file with content "some content" to "/lorem.txt"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | lorem.txt |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
And user "Alice" has moved file "/lorem.txt" to "/new-lorem.txt"
|
|
When user "Alice" gets the info of the last public link 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" should include
|
|
| id | A_STRING |
|
|
| share_type | public_link |
|
|
| uid_owner | %username% |
|
|
| displayname_owner | %displayname% |
|
|
| permissions | read |
|
|
| stime | A_NUMBER |
|
|
| parent | |
|
|
| expiration | |
|
|
| token | A_STRING |
|
|
| uid_file_owner | %username% |
|
|
| displayname_file_owner | %displayname% |
|
|
| item_type | file |
|
|
| item_source | A_STRING |
|
|
| path | /new-lorem.txt |
|
|
| mimetype | text/plain |
|
|
| storage_id | A_STRING |
|
|
| storage | A_STRING |
|
|
| file_source | A_STRING |
|
|
| file_target | /new-lorem.txt |
|
|
| mail_send | 0 |
|
|
| name | |
|
|
Examples:
|
|
| dav-path-version | ocs-api-version | ocs-status-code |
|
|
| old | 1 | 100 |
|
|
| old | 2 | 200 |
|
|
| new | 1 | 100 |
|
|
| new | 2 | 200 |
|
|
| spaces | 1 | 100 |
|
|
| spaces | 2 | 200 |
|
|
|
|
|
|
Scenario Outline: update the role of a public link to internal
|
|
Given using OCS API version "<ocs-api-version>"
|
|
And using <dav-path-version> DAV path
|
|
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile.txt"
|
|
And using SharingNG
|
|
And user "Alice" has created the following resource link share:
|
|
| resource | textfile.txt |
|
|
| space | Personal |
|
|
| permissionsRole | view |
|
|
| password | %public% |
|
|
When user "Alice" updates the last public link share using the sharing API with
|
|
| permissions | 0 |
|
|
Then the OCS status code should be "<ocs-status-code>"
|
|
And the HTTP status code should be "200"
|
|
Examples:
|
|
| dav-path-version | ocs-api-version | ocs-status-code |
|
|
| old | 1 | 100 |
|
|
| old | 2 | 200 |
|
|
| new | 1 | 100 |
|
|
| new | 2 | 200 |
|
|
| spaces | 1 | 100 |
|
|
| spaces | 2 | 200 |
|