[tests-only][ci] split large API test suites (#8212)
* split large API test suites * remove 30s sleep * organize core-api test suites * organize core-api test suites * divide into 9 pipelines * organize core-api test suites * organize api-search suites * organize api-search suites * fix config file
This commit is contained in:
Sawjan Gurung
@@ -0,0 +1,479 @@
|
||||
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 and without skeleton files
|
||||
|
||||
|
||||
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 user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| 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 user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| password | %public% |
|
||||
And user "Alice" has updated the last public link share with
|
||||
| expireDate | 2033-01-31T23:59:59+0100 |
|
||||
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 |
|
||||
|
||||
|
||||
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 user "Alice" has created a public link share with settings
|
||||
| path | randomfile.txt |
|
||||
| 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 the last publicly shared file using the old public WebDAV API with password "%public%" and the content should be "Random data"
|
||||
And the public should be able to download the last publicly shared file using the new public WebDAV API 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 user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| password | %public% |
|
||||
And user "Alice" has updated the last public link share with
|
||||
| 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 user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| password | %public% |
|
||||
And user "Alice" has updated the last public link share with
|
||||
| permissions | read,update,create,delete |
|
||||
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 user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| password | %public% |
|
||||
And user "Alice" has updated the last public link share with
|
||||
| permissions | read,update,create,delete |
|
||||
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 publicUpload option and getting its info
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| password | %public% |
|
||||
And user "Alice" has updated the last public link share with
|
||||
| publicUpload | true |
|
||||
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 |
|
||||
|
||||
@skipOnReva
|
||||
Scenario Outline: adding public upload to a read only shared folder as recipient is not allowed using the public API
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "/test"
|
||||
And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
|
||||
And user "Brian" has created a public link share with settings
|
||||
| path | /Shares/test |
|
||||
| publicUpload | false |
|
||||
| password | %public% |
|
||||
When user "Brian" updates the last public link share using the sharing API with
|
||||
| publicUpload | true |
|
||||
Then the OCS status code should be "403"
|
||||
And the HTTP status code should be "<http_status_code>"
|
||||
And uploading a file should not work using the old public WebDAV API
|
||||
And uploading a file should not work using the new public WebDAV API
|
||||
Examples:
|
||||
| ocs_api_version | http_status_code |
|
||||
| 1 | 200 |
|
||||
| 2 | 403 |
|
||||
|
||||
@skipOnReva
|
||||
Scenario Outline:adding public upload to a shared folder as recipient is allowed with permissions using the public API
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "/test"
|
||||
And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
|
||||
And user "Brian" has created a public link share with settings
|
||||
| path | /Shares/test |
|
||||
| publicUpload | false |
|
||||
| password | %public% |
|
||||
When user "Brian" updates the last public link share using the sharing API with
|
||||
| publicUpload | true |
|
||||
Then the OCS status code should be "<ocs_status_code>"
|
||||
And the HTTP status code should be "200"
|
||||
And uploading a file with password "%public%" should work using the old public WebDAV API
|
||||
And uploading a file with password "%public%" should work using the new public WebDAV API
|
||||
Examples:
|
||||
| ocs_api_version | ocs_status_code |
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
|
||||
@skipOnReva
|
||||
Scenario Outline: adding public link with all permissions to a read only shared folder as recipient is not allowed using the public API
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "/test"
|
||||
And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
|
||||
And user "Brian" has created a public link share with settings
|
||||
| path | /Shares/test |
|
||||
| permissions | read |
|
||||
| password | %public% |
|
||||
When user "Brian" updates the last public link share using the sharing API with
|
||||
| permissions | read,update,create,delete |
|
||||
Then the OCS status code should be "403"
|
||||
And the HTTP status code should be "<http_status_code>"
|
||||
And uploading a file should not work using the old public WebDAV API
|
||||
And uploading a file should not work using the new public WebDAV API
|
||||
Examples:
|
||||
| ocs_api_version | http_status_code |
|
||||
| 1 | 200 |
|
||||
| 2 | 403 |
|
||||
|
||||
@skipOnReva
|
||||
Scenario Outline: adding public link with all permissions to a read only shared folder as recipient is allowed with permissions using the public API
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "/test"
|
||||
And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
|
||||
And user "Brian" has created a public link share with settings
|
||||
| path | /Shares/test |
|
||||
| permissions | read |
|
||||
| password | %public% |
|
||||
When user "Brian" updates the last public link share using the sharing API with
|
||||
| permissions | read,update,create,delete |
|
||||
Then the OCS status code should be "<ocs_status_code>"
|
||||
And the HTTP status code should be "200"
|
||||
And uploading a file with password "%public%" should work using the new public WebDAV API
|
||||
Examples:
|
||||
| ocs_api_version | ocs_status_code |
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
|
||||
@issue-1269
|
||||
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 user "Alice" has created a public link share with settings
|
||||
| path | /PARENT |
|
||||
| permissions | read,update,create,delete |
|
||||
| password | %public% |
|
||||
And user "Alice" has updated the last public link share with
|
||||
| permissions | read |
|
||||
And the public deletes file "CHILD/child.txt" from the last public link share using the password "%public%" and new public WebDAV API
|
||||
And 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 |
|
||||
|
||||
|
||||
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 user "Alice" has created a public link share with settings
|
||||
| path | /PARENT |
|
||||
| permissions | read |
|
||||
| password | %public% |
|
||||
And user "Alice" has updated the last public link share with
|
||||
| permissions | read,update,create,delete |
|
||||
When the public deletes file "CHILD/child.txt" from the last public link share using the password "%public%" and new public WebDAV API
|
||||
And the public deletes file "parent.txt" from the last public link share using the password "%public%" and new 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 user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| 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 |
|
||||
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path-version | ocs_api_version | ocs_status_code |
|
||||
| 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 user "Alice" has created a public link share with settings
|
||||
| path | lorem.txt |
|
||||
| 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 |
|
||||
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path-version | ocs_api_version | ocs_status_code |
|
||||
| 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 user "Alice" has created a public link share with settings
|
||||
| path | /textfile.txt |
|
||||
| permissions | read |
|
||||
| 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 |
|
||||
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path-version | ocs_api_version | ocs_status_code |
|
||||
| spaces | 1 | 100 |
|
||||
| spaces | 2 | 200 |
|
||||
@@ -0,0 +1,133 @@
|
||||
@issue-1276 @issue-1277
|
||||
|
||||
Feature: upload to a public link share
|
||||
As a user
|
||||
I want to create a public link with upload permission
|
||||
So that the recipient can upload resources
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
|
||||
@smokeTest @issue-1267
|
||||
Scenario: uploading same file to a public upload-only share multiple times via new API
|
||||
# The new API does the auto rename in upload-only folders
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | create |
|
||||
| password | %public% |
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test" using the new public WebDAV API
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test2" using the new public WebDAV API
|
||||
Then the HTTP status code of responses on all endpoints should be "201"
|
||||
And the following headers should match these regular expressions
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test"
|
||||
And the content of file "/FOLDER/test (2).txt" for user "Alice" should be "test2"
|
||||
|
||||
|
||||
Scenario Outline: uploading file to a public upload-only share using public API that was deleted does not work
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | create |
|
||||
| password | %public% |
|
||||
And user "Alice" has deleted folder "/FOLDER"
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test-file" using the new public WebDAV API
|
||||
And the HTTP status code should be "404"
|
||||
|
||||
@issue-1268
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| spaces |
|
||||
|
||||
@issue-1269
|
||||
Scenario: uploading file to a public read-only share folder with public API does not work
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | read |
|
||||
| password | %public% |
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test-file" using the new public WebDAV API
|
||||
And the HTTP status code should be "403"
|
||||
|
||||
|
||||
Scenario: uploading to a public upload-only share with public API
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | create |
|
||||
| password | %public% |
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test-file" using the new public WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
|
||||
And the following headers should match these regular expressions
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
|
||||
|
||||
Scenario: uploading to a public upload-only share with password with public API
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| password | %public% |
|
||||
| permissions | create |
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test-file" using the new public WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
|
||||
|
||||
|
||||
Scenario: uploading to a public read/write share with password with public API
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| password | %public% |
|
||||
| permissions | change |
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test-file" using the new public WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
|
||||
|
||||
|
||||
Scenario: uploading file to a public shared folder with read/write permission when the sharer has insufficient quota does not work with public API
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | change |
|
||||
| password | %public% |
|
||||
And the quota of user "Alice" has been set to "0"
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test2" using the new public WebDAV API
|
||||
Then the HTTP status code should be "507"
|
||||
|
||||
@issue-1290
|
||||
Scenario: uploading file to a public shared folder with upload-only permission when the sharer has insufficient quota does not work with public API
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | create |
|
||||
| password | %public% |
|
||||
And the quota of user "Alice" has been set to "0"
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test2" using the new public WebDAV API
|
||||
Then the HTTP status code should be "507"
|
||||
|
||||
@smokeTest
|
||||
Scenario: uploading to a public upload-write and no edit and no overwrite share with public API
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | uploadwriteonly |
|
||||
| password | %public% |
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test2" using the new public WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test2"
|
||||
|
||||
@smokeTest @issue-1267
|
||||
Scenario: uploading same file to a public upload-write and no edit and no overwrite share multiple times with new public API
|
||||
Given user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | uploadwriteonly |
|
||||
| password | %public% |
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test" using the new public WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the following headers should match these regular expressions
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test2" using the new public WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test"
|
||||
And the content of file "/FOLDER/test (2).txt" for user "Alice" should be "test2"
|
||||
Reference in New Issue
Block a user