mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-05-05 11:00:12 -05:00
Code Issues Packages Projects Releases Wiki Activity

[test-only] ApiTest. deleteTag test. increase coverage (#5417)

Browse Source
This commit is contained in:
Viktor Scharf
2023-01-23 04:41:59 +01:00
committed by GitHub
parent 6af8988403
commit 8aff14751b
2 changed files with 209 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiSpaces/tag.feature
+163
View File
@@ -78,3 +78,166 @@ Feature: Tag
| important |
| fileTag |
| tag with symbol @^$#^%$@%!_+) |
Scenario Outline: Member of the space tries to create tag
Given user "Alice" has shared a space "use-tag" to user "Brian" with role "<role>"
When user "Brian" creates the following tags for folder "folderMain/insideTheFolder.txt" of space "use-tag":
| tag level#1 |
| tag with symbols @^$#^%$@%!_+) |
Then the HTTP status code should be "<code>"
When user "Alice" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response <shouldOrNot> contain following tags:
| tag level#1 |
| tag with symbols @^$#^%$@%!_+) |
Examples:
| role | code | shouldOrNot |
| viewer | 403 | should not |
| editor | 200 | should |
| manager | 200 | should |
Scenario: The recipient has a created tags if share is accepted
Given user "Alice" has created the following tags for folder "folderMain" of the space "use-tag":
| folderTag |
| marketing |
And user "Alice" has shared the following entity "folderMain" inside of space "use-tag" with user "Brian" with role "viewer"
When user "Brian" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response should not contain following tags:
| folderTag |
| marketing |
When user "Brian" accepts share "/folderMain" offered by user "Alice" using the sharing API
And user "Brian" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response should contain following tags:
| folderTag |
| marketing |
Scenario Outline: The recipient of the shared resource tries to create a tag
Given user "Alice" has shared the following entity "folderMain" inside of space "use-tag" with user "Brian" with role "<role>"
And user "Brian" has accepted share "/folderMain" offered by user "Alice"
When user "Brian" creates the following tags for <resource> "<resourceName>" of space "Shares":
| tag in a shared resource |
| second tag |
Then the HTTP status code should be "<code>"
When user "Alice" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response <shouldOrNot> contain following tags:
| tag in a shared resource |
| second tag |
Examples:
| role | resource | resourceName | code | shouldOrNot |
| viewer | file | folderMain/insideTheFolder.txt | 403 | should not |
| editor | file | folderMain/insideTheFolder.txt | 200 | should |
| manager | file | folderMain/insideTheFolder.txt | 200 | should |
| viewer | folder | folderMain | 403 | should not |
| editor | folder | folderMain | 200 | should |
| manager | folder | folderMain | 200 | should |
Scenario Outline: The recipient of the shared resource tries to remove a tag
Given user "Alice" has shared the following entity "folderMain" inside of space "use-tag" with user "Brian" with role "<role>"
And user "Alice" has created the following tags for <resource> "<resourceName>" of the space "use-tag":
| tag in a shared resource |
| second tag |
And user "Brian" has accepted share "/folderMain" offered by user "Alice"
When user "Brian" removes the following tags for <resource> "<resourceName>" of space "Shares":
| tag in a shared resource |
| second tag |
Then the HTTP status code should be "<code>"
When user "Alice" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response <shouldOrNot> contain following tags:
| tag in a shared resource |
| second tag |
Examples:
| role | resource | resourceName | code | shouldOrNot |
| viewer | file | folderMain/insideTheFolder.txt | 403 | should |
| editor | file | folderMain/insideTheFolder.txt | 200 | should not |
| manager | file | folderMain/insideTheFolder.txt | 200 | should not |
| viewer | folder | folderMain | 403 | should |
| editor | folder | folderMain | 200 | should not |
| manager | folder | folderMain | 200 | should not |
Scenario: User removes folder tags
Given user "Alice" has created the following tags for folder "folderMain" of the space "use-tag":
| folderTag |
| marketing |
| development |
When user "Alice" removes the following tags for folder "folderMain" of space "use-tag":
| folderTag |
| marketing |
And user "Alice" sends PROPFIND request from the space "use-tag" to the resource "folderMain" using the WebDAV API
Then the HTTP status code should be "207"
And the "PROPFIND" response should contain a space "use-tag" with these key and value pairs:
| key | value |
| oc:tags | development |
Scenario: User lists tags after deleting some folder tags
Given user "Alice" has created the following tags for folder "folderMain" of the space "use-tag":
| folderTag |
| marketing |
| development |
When user "Alice" removes the following tags for folder "folderMain" of space "use-tag":
| folderTag |
| marketing |
Then the HTTP status code should be "200"
When user "Alice" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response should contain following tags:
| development |
And the response should not contain following tags:
| folderTag |
| marketing |
Scenario: User lists the tags after deleting a folder
Given user "Alice" has created the following tags for folder "folderMain" of the space "use-tag":
| folderTag |
| marketing |
When user "Alice" removes the folder "folderMain" from space "use-tag"
Then the HTTP status code should be "204"
When user "Alice" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response should not contain following tags:
| folderTag |
| marketing |
Scenario: User lists the tags after deleting a space
Given user "Alice" has created the following tags for folder "folderMain" of the space "use-tag":
| folderTag |
| marketing |
When user "Alice" disables a space "use-tag"
Then the HTTP status code should be "204"
When user "Alice" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response should contain following tags:
| folderTag |
| marketing |
When user "Alice" deletes a space "use-tag"
Then the HTTP status code should be "204"
When user "Alice" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response should not contain following tags:
| folderTag |
| marketing |
Scenario: User lists the tags after restoring a deleted folder
Given user "Alice" has created the following tags for folder "folderMain" of the space "use-tag":
| folderTag |
| marketing |
And user "Alice" has removed the folder "folderMain" from space "use-tag"
When user "Alice" restores the folder "folderMain" from the trash of the space "use-tag" to "/folderMain"
Then the HTTP status code should be "201"
When user "Alice" lists all available tags via the GraphApi
Then the HTTP status code should be "200"
And the response should contain following tags:
| folderTag |
| marketing |