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

Used kebab case for example table header name

Browse Source
This commit is contained in:
Prarup Gurung
2024-03-21 10:04:25 +05:45
parent 84a14c5953
commit fcba2d34a4
26 changed files with 918 additions and 918 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiSpacesShares/shareSpacesViaLink.feature
+66 -66
View File
@@ -21,30 +21,30 @@ Feature: Share spaces via link
When user "Alice" creates a public link share of the space "share space" with settings:
| permissions | <permissions> |
| password | <password> |
| name | <linkName> |
| expireDate | <expireDate> |
| name | <link-name> |
| expireDate | <expire-date> |
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> |
| item_type | folder |
| mimetype | httpd/unix-directory |
| file_target | / |
| path | / |
| permissions | <expected-permissions> |
| share_type | public_link |
| displayname_owner | %displayname% |
| uid_owner | %username% |
| name | <link-name> |
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 | %public% | link | 2042-03-25T23:59:59+0100 |
| 5 | read,create | %public% | | 2042-03-25T23:59:59+0100 |
| 15 | read,update,create,delete | %public% | link | |
| permissions | expected-permissions | password | link-name | expire-date |
| 1 | read | %public% | link | 2042-03-25T23:59:59+0100 |
| 5 | read,create | %public% | | 2042-03-25T23:59:59+0100 |
| 15 | read,update,create,delete | %public% | link | |
Scenario: manager can create internal link without password
@@ -84,8 +84,8 @@ Feature: Share spaces via link
@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> |
| shareWith | Brian |
| role | <space-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"
@@ -93,9 +93,9 @@ Feature: Share spaces via link
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 |
| space-role |
| viewer |
| editor |
Scenario: user with manager role can share a space to public via link
@@ -131,7 +131,7 @@ Feature: Share spaces via link
Scenario Outline: space admin removes password of a public link share of a space (read/invite permission)
Given using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs-api-version>"
And user "Alice" has created a public link share of the space "share space" with settings:
| permissions | <permissions> |
| password | %public% |
@@ -139,10 +139,10 @@ Feature: Share spaces via link
| permissions | <permissions> |
| password | |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And the OCS status code should be "<ocs-status-code>"
And the OCS status message should be "OK"
Examples:
| ocs_api_version | ocs_status_code | permissions |
| ocs-api-version | ocs-status-code | permissions |
| 1 | 100 | 1 |
| 1 | 100 | 0 |
| 2 | 200 | 1 |
@@ -150,18 +150,18 @@ Feature: Share spaces via link
Scenario Outline: space admin tries to remove password of a public link share of a space (various permission)
Given using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs-api-version>"
And user "Alice" has created a public link share of the space "share space" with settings:
| permissions | <permissions> |
| password | %public% |
When user "Alice" updates the last public link share using the sharing API with
| permissions | <permissions> |
| password | |
Then the HTTP status code should be "<http_status_code>"
Then the HTTP status code should be "<http-status-code>"
And the OCS status code should be "400"
And the OCS status message should be "missing required password"
Examples:
| ocs_api_version | permissions | http_status_code |
| ocs-api-version | permissions | http-status-code |
| 1 | 5 | 200 |
| 2 | 5 | 400 |
| 1 | 15 | 200 |
@@ -171,7 +171,7 @@ Feature: Share spaces via link
Scenario Outline: space admin removes password of a public link share of a space (invite permission)
Given using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs-api-version>"
And user "Alice" has created a public link share of the space "share space" with settings:
| permissions | 1 |
| password | %public% |
@@ -179,16 +179,16 @@ Feature: Share spaces via link
| permissions | 0 |
| password | |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And the OCS status code should be "<ocs-status-code>"
And the OCS status message should be "OK"
Examples:
| ocs_api_version | ocs_status_code |
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: space manager tries to remove password of a public link share of a space (read permission)
Given using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared a space "share space" with settings:
| shareWith | Brian |
| role | manager |
@@ -198,17 +198,17 @@ Feature: Share spaces via link
When user "Brian" updates the last public link share using the sharing API with
| permissions | 1 |
| password | |
Then the HTTP status code should be "<http_status_code>"
Then the HTTP status code should be "<http-status-code>"
And the OCS status code should be "104"
And the OCS status message should be "user is not allowed to delete the password from the public link"
Examples:
| ocs_api_version | http_status_code |
| ocs-api-version | http-status-code |
| 1 | 200 |
| 2 | 403 |
Scenario Outline: space manager tries to remove password of a public link share of a space (various permission)
Given using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared a space "share space" with settings:
| shareWith | Brian |
| role | manager |
@@ -218,11 +218,11 @@ Feature: Share spaces via link
When user "Brian" updates the last public link share using the sharing API with
| permissions | <permissions> |
| password | |
Then the HTTP status code should be "<http_status_code>"
Then the HTTP status code should be "<http-status-code>"
And the OCS status code should be "400"
And the OCS status message should be "missing required password"
Examples:
| ocs_api_version | permissions | http_status_code |
| ocs-api-version | permissions | http-status-code |
| 1 | 5 | 200 |
| 2 | 5 | 400 |
| 1 | 15 | 200 |
@@ -232,7 +232,7 @@ Feature: Share spaces via link
Scenario Outline: space manager removes password of a public link share of a space (invite permission)
Given using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared a space "share space" with settings:
| shareWith | Brian |
| role | manager |
@@ -243,47 +243,47 @@ Feature: Share spaces via link
| permissions | 0 |
| password | |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And the OCS status code should be "<ocs-status-code>"
And the OCS status message should be "OK"
Examples:
| ocs_api_version | ocs_status_code |
| ocs-api-version | ocs-status-code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: space member tries to remove the password of a public link share of a space
Given using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs-api-version>"
And user "Alice" has shared a space "share space" with settings:
| shareWith | Brian |
| role | <role> |
| shareWith | Brian |
| role | <space-role> |
And user "Alice" has created a public link share of the space "share space" with settings:
| permissions | <permissions> |
| password | %public% |
| permissions | <permissions> |
| password | %public% |
When user "Brian" updates the last public link share using the sharing API with
| permissions | <permissions> |
| password | |
Then the HTTP status code should be "<http_status_code>"
| password | |
Then the HTTP status code should be "<http-status-code>"
And the OCS status code should be "997"
And the OCS status message should be "missing permissions to update share"
Examples:
| ocs_api_version | http_status_code | role | permissions |
| 1 | 200 | viewer | 1 |
| 2 | 401 | viewer | 1 |
| 1 | 200 | viewer | 5 |
| 2 | 401 | viewer | 5 |
| 1 | 200 | viewer | 15 |
| 2 | 401 | viewer | 15 |
| 1 | 200 | viewer | 4 |
| 2 | 401 | viewer | 4 |
| 1 | 200 | viewer | 0 |
| 2 | 401 | viewer | 0 |
| 1 | 200 | editor | 1 |
| 2 | 401 | editor | 1 |
| 1 | 200 | editor | 5 |
| 2 | 401 | editor | 5 |
| 1 | 200 | editor | 15 |
| 2 | 401 | editor | 15 |
| 1 | 200 | editor | 4 |
| 2 | 401 | editor | 4 |
| 1 | 200 | editor | 0 |
| 2 | 401 | editor | 0 |
| ocs-api-version | http-status-code | space-role | permissions |
| 1 | 200 | viewer | 1 |
| 2 | 401 | viewer | 1 |
| 1 | 200 | viewer | 5 |
| 2 | 401 | viewer | 5 |
| 1 | 200 | viewer | 15 |
| 2 | 401 | viewer | 15 |
| 1 | 200 | viewer | 4 |
| 2 | 401 | viewer | 4 |
| 1 | 200 | viewer | 0 |
| 2 | 401 | viewer | 0 |
| 1 | 200 | editor | 1 |
| 2 | 401 | editor | 1 |
| 1 | 200 | editor | 5 |
| 2 | 401 | editor | 5 |
| 1 | 200 | editor | 15 |
| 2 | 401 | editor | 15 |
| 1 | 200 | editor | 4 |
| 2 | 401 | editor | 4 |
| 1 | 200 | editor | 0 |
| 2 | 401 | editor | 0 |