mirror of
https://github.com/opencloud-eu/opencloud.git
synced 2026-03-22 17:31:56 -04:00
a6964c2d3d
refactored given steps refactored some when stepa refactored remaining when and then steps use of when step for the action changed line no in expected failure remove and add same kind of steps in the scenario and refactored function names adressing reviews
117 lines
6.0 KiB
Gherkin
117 lines
6.0 KiB
Gherkin
Feature: Share spaces via link
|
|
As the manager of a space
|
|
I want to be able to share a space via public link
|
|
So that an anonymous user can have access to certain resources
|
|
|
|
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 "share space" with the default quota using the GraphApi
|
|
And user "Alice" has uploaded a file inside space "share space" with content "some content" to "test.txt"
|
|
|
|
|
|
Scenario Outline: manager can share a space to public via link with different permissions
|
|
When user "Alice" creates a public link share of the space "share space" with settings:
|
|
| permissions | <permissions> |
|
|
| password | <password> |
|
|
| name | <linkName> |
|
|
| expireDate | <expireDate> |
|
|
Then the HTTP status code should be "200"
|
|
And the OCS status code should be "200"
|
|
And the OCS status message should be "OK"
|
|
And the fields of the last response to user "Alice" should include
|
|
| item_type | folder |
|
|
| mimetype | httpd/unix-directory |
|
|
| file_target | / |
|
|
| path | / |
|
|
| permissions | <expectedPermissions> |
|
|
| share_type | public_link |
|
|
| displayname_owner | %displayname% |
|
|
| uid_owner | %username% |
|
|
| name | <linkName> |
|
|
When the public downloads file "/test.txt" from inside the last public link shared folder with password "<password>" using the new public WebDAV API
|
|
Then the HTTP status code should be "200"
|
|
And the downloaded content should be "some content"
|
|
But the public should not be able to download file "/test.txt" from inside the last public link shared folder using the new public WebDAV API with password "wrong pass"
|
|
Examples:
|
|
| permissions | expectedPermissions | password | linkName | expireDate |
|
|
| 1 | read | 123234 | link | 2042-03-25T23:59:59+0100 |
|
|
| 5 | read,create | qwerty 123 | | 2042-03-25T23:59:59+0100 |
|
|
| 15 | read,update,create,delete | d*V^o*Y03R9n8Z | link | |
|
|
|
|
|
|
Scenario: uploader should be able to upload a file
|
|
When user "Alice" creates a public link share of the space "share space" with settings:
|
|
| permissions | 4 |
|
|
| password | 123 |
|
|
| name | forUpload |
|
|
| expireDate | 2042-03-25T23:59:59+0100 |
|
|
Then the HTTP status code should be "200"
|
|
And the OCS status code should be "200"
|
|
And the OCS status message should be "OK"
|
|
And the fields of the last response to user "Alice" should include
|
|
| item_type | folder |
|
|
| mimetype | httpd/unix-directory |
|
|
| file_target | / |
|
|
| path | / |
|
|
| permissions | create |
|
|
| share_type | public_link |
|
|
| displayname_owner | %displayname% |
|
|
| uid_owner | %username% |
|
|
| name | forUpload |
|
|
And the public should be able to upload file "lorem.txt" into the last public link shared folder using the new public WebDAV API with password "123"
|
|
And for user "Alice" the space "share space" should contain these entries:
|
|
| lorem.txt |
|
|
|
|
@skipOnRevaMaster
|
|
Scenario Outline: user without manager role cannot share a space to public via link
|
|
Given user "Alice" has shared a space "share space" with settings:
|
|
| shareWith | Brian |
|
|
| role | <role> |
|
|
When user "Brian" creates a public link share of the space "share space" with settings:
|
|
| permissions | 1 |
|
|
Then the HTTP status code should be "403"
|
|
And the OCS status code should be "403"
|
|
And the OCS status message should be "No share permission"
|
|
And for user "Alice" the space "share space" should not contain the last created public link
|
|
Examples:
|
|
| role |
|
|
| viewer |
|
|
| editor |
|
|
|
|
|
|
Scenario: user with manager role can share a space to public via link
|
|
Given user "Alice" has shared a space "share space" with settings:
|
|
| shareWith | Brian |
|
|
| role | manager |
|
|
When user "Brian" creates a public link share of the space "share space" with settings:
|
|
| permissions | 1 |
|
|
Then the HTTP status code should be "200"
|
|
And the OCS status code should be "200"
|
|
And for user "Alice" the space "share space" should contain the last created public link
|
|
|
|
|
|
Scenario: user cannot share a disabled space to public via link
|
|
Given user "Alice" has disabled a space "share space"
|
|
When user "Alice" creates a public link share of the space "share space" with settings:
|
|
| permissions | 1 |
|
|
Then the HTTP status code should be "404"
|
|
And the OCS status code should be "404"
|
|
And the OCS status message should be "Wrong path, file/folder doesn't exist"
|
|
And for user "Alice" the space "share space" should not contain the last created public link
|
|
|
|
|
|
Scenario: user cannot create a public link from the personal space
|
|
When user "Alice" creates a public link share of the space "Alice Hansen" with settings:
|
|
| permissions | 1 |
|
|
Then the HTTP status code should be "400"
|
|
And the OCS status message should be "Can not share space root"
|
|
And for user "Alice" the space "Alice Hansen" should not contain the last created public link
|