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

[tests-only] [full-ci] Refactor scenario related to checking json response (#6034)

Browse Source 
* Separate positive and negative testing in different scenario

* Remove duplicate scenario

* Refactor json step graamer

* Remove unnecessary steps

* Add step to check space disable state
This commit is contained in:
Amrita
2023-05-04 18:40:11 +05:45
committed by GitHub
parent 5c3c7278dc
commit 517a177057
11 changed files with 131 additions and 851 deletions
Download Patch File Download Diff File Expand all files Collapse all files

234
tests/acceptance/features/apiSpaces/changeSpaces.feature
View File

@@ -16,7 +16,7 @@ Feature: Change data of space
And the administrator has given "Alice" the role "Space Admin" using the settings api
And user "Alice" has created a space "Project Jupiter" of type "project" with quota "20"
And user "Alice" has shared a space "Project Jupiter" with settings:
| shareWith | Brian |
| shareWith | Brian |
| role | editor |
And user "Alice" has shared a space "Project Jupiter" with settings:
| shareWith | Bob |
@@ -24,10 +24,10 @@ Feature: Change data of space
And using spaces DAV path
Scenario Outline: only space admin user can change the name of a space via the Graph API
When user "<user>" changes the name of the "Project Jupiter" space to "<expectedName>"
Then the HTTP status code should be "<code>"
And for user "<user>" the JSON response should contain space called "<expectedName>" and match
Scenario: user with space manager role can change the name of a space via the Graph API
When user "Alice" changes the name of the "Project Jupiter" space to "Project Death Star"
Then the HTTP status code should be "200"
And the JSON data of the response should match
"""
{
"type": "object",
@@ -38,7 +38,7 @@ Feature: Change data of space
"properties": {
"name": {
"type": "string",
"enum": ["<expectedName>"]
"enum": ["Project Death Star"]
},
"driveType": {
"type": "string",
@@ -47,17 +47,21 @@ Feature: Change data of space
}
}
"""
Scenario Outline: user other than space manager role can't change the name of a Space via the Graph API
When user "<user>" changes the name of the "Project Jupiter" space to "Project Jupiter"
Then the HTTP status code should be "403"
Examples:
| user | code | expectedName |
| Alice | 200 | Project Death Star |
| Brian | 403 | Project Jupiter |
| Bob | 403 | Project Jupiter |
| user |
| Brian |
| Bob |
Scenario: only space admin user can change the description(subtitle) of a space via the Graph API
Scenario: user with space manager role can change the description(subtitle) of a space via the Graph API
When user "Alice" changes the description of the "Project Jupiter" space to "The Death Star is a fictional mobile space station"
Then the HTTP status code should be "200"
And for user "Alice" the JSON response should contain space called "Project Jupiter" and match
And the JSON data of the response should match
"""
{
"type": "object",
@@ -86,58 +90,26 @@ Feature: Change data of space
Scenario Outline: viewer and editor cannot change the description(subtitle) of a space via the Graph API
When user "<user>" changes the description of the "Project Jupiter" space to "The Death Star is a fictional mobile space station"
Then the HTTP status code should be "<code>"
Then the HTTP status code should be "403"
Examples:
| user | code |
| Brian | 403 |
| Bob | 403 |
| user |
| Brian |
| Bob |
Scenario Outline: user tries to increase the quota of a Space via the Graph API
Scenario Outline: user with normal space permission can't increase the quota of a Space via the Graph API
When user "<user>" changes the quota of the "Project Jupiter" space to "100"
Then the HTTP status code should be "<code>"
And for user "<user>" the JSON response should contain space called "Project Jupiter" and match
"""
{
"type": "object",
"required": [
"name",
"quota"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Jupiter"]
},
"quota": {
"type": "object",
"required": [
"total"
],
"properties": {
"total" : {
"type": "number",
"enum": [<expectedQuotaValue>]
}
}
}
}
}
"""
Then the HTTP status code should be "403"
Examples:
| user | code | expectedQuotaValue |
| Alice | 200 | 100 |
| Brian | 403 | 20 |
| Bob | 403 | 20 |
| user |
| Brian |
| Bob |
Scenario Outline: space admin user set no restriction quota of a Space via the Graph API
When user "Alice" changes the quota of the "Project Jupiter" space to "<quotaValue>"
Then the HTTP status code should be "200"
When user "Alice" uploads a file inside space "Project Jupiter" with content "some content" to "file.txt" using the WebDAV API
Then the HTTP status code should be "201"
And for user "Alice" the JSON response should contain space called "Project Jupiter" and match
And the JSON data of the response should match
"""
{
"type": "object",
@@ -159,7 +131,7 @@ Feature: Change data of space
"properties": {
"used" : {
"type": "number",
"enum": [12]
"enum": [0]
},
"total" : {
"type": "number",
@@ -181,7 +153,7 @@ Feature: Change data of space
And user "Alice" has uploaded a file inside space "Project Jupiter" with content "space description" to ".space/readme.md"
When user "Alice" sets the file ".space/readme.md" as a description in a special section of the "Project Jupiter" space
Then the HTTP status code should be "200"
And for user "Alice" the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/readme.md" and match
And the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/readme.md" and match
"""
{
"type": "object",
@@ -264,85 +236,13 @@ Feature: Change data of space
And user "Alice" has set the file ".space/readme.md" as a description in a special section of the "Project Jupiter" space
When user "<user>" uploads a file inside space "Project Jupiter" with content "new description" to ".space/readme.md" using the WebDAV API
Then the HTTP status code should be "<code>"
And for user "Alice" the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/readme.md" and match
"""
{
"type": "object",
"required": [
"name",
"special"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Jupiter"]
},
"special": {
"type": "array",
"items": [
{
"type": "object",
"required": [
"size",
"name",
"specialFolder",
"file",
"id",
"eTag"
],
"properties": {
"size": {
"type": "number",
"enum": [<size>]
},
"name": {
"type": "string",
"enum": ["readme.md"]
},
"specialFolder": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"enum": ["readme"]
}
}
},
"file": {
"type": "object",
"required": [
"mimeType"
],
"properties": {
"type": "string",
"enum": ["text/markdown"]
}
},
"id": {
"type": "string",
"enum": ["%file_id%"]
},
"tag": {
"type": "string",
"enum": ["%eTag%"]
}
}
}
]
}
}
}
"""
And for user "<user>" folder ".space/" of the space "Project Jupiter" should contain these entries:
| readme.md |
And for user "<user>" the content of the file ".space/readme.md" of the space "Project Jupiter" should be "<content>"
Examples:
| user | code | size | content |
| Brian | 204 | 15 | new description |
| Bob | 403 | 17 | space description |
| user | code | content |
| Brian | 204 | new description |
| Bob | 403 | space description |
Scenario Outline: user space admin and editor set image file as space image of the space via the Graph API
@@ -350,7 +250,7 @@ Feature: Change data of space
And user "<user>" has uploaded a file inside space "Project Jupiter" with content "" to ".space/<fileName>"
When user "<user>" sets the file ".space/<fileName>" as a space image in a special section of the "Project Jupiter" space
Then the HTTP status code should be "200"
And for user "Alice" the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/<fileName>" and match
And the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/<fileName>" and match
"""
{
"type": "object",
@@ -444,7 +344,7 @@ Feature: Change data of space
When user "<user>" uploads a file inside space "Project Jupiter" owned by the user "Alice" with content "new content" to ".space/readme.md" using the WebDAV API
Then the HTTP status code should be "<code>"
And for user "<user>" the content of the file ".space/readme.md" of the space "Project Jupiter" should be "<expectedContent>"
And for user "<user>" the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/readme.md" and match
And the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/readme.md" and match
"""
{
"type": "object",
@@ -530,7 +430,7 @@ Feature: Change data of space
When user "<user>" has uploaded a file inside space "Project Jupiter" with content "" to ".space/newSpaceImage.png"
And user "<user>" sets the file ".space/newSpaceImage.png" as a space image in a special section of the "Project Jupiter" space
Then the HTTP status code should be "200"
And for user "<user>" the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/newSpaceImage.png" and match
And the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/newSpaceImage.png" and match
"""
{
"type": "object",
@@ -608,63 +508,47 @@ Feature: Change data of space
| Brian |
Scenario Outline: admin user set own quota of a personal space via the Graph API
Scenario Outline: user can't upload resource greater than set quota
Given the administrator has given "Alice" the role "<userRole>" using the settings api
And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "15"
When user "Alice" uploads a file inside space "Alice Hansen" with content "file is more than 15 bytes" to "file.txt" using the WebDAV API
Then the HTTP status code should be "507"
And for user "Alice" the space "Personal" should not contain these entries:
| file.txt |
Examples:
| userRole |
| Admin |
| Space Admin |
| User |
| Guest |
Scenario Outline: admin user set own quota of a personal space via the Graph API and upload resource
When user "Admin" changes the quota of the "Admin" space to "<quotaValue>"
Then the HTTP status code should be "200"
When user "Admin" uploads a file inside space "Admin" with content "file is more than 15 bytes" to "file.txt" using the WebDAV API
Then the HTTP status code should be <code>
And for user "Admin" the space "Personal" should contain these entries:
| file.txt |
Examples:
| quotaValue | code |
| 15 | "507" |
| 10000 | between "201" and "204" |
| 0 | between "201" and "204" |
| -1 | between "201" and "204" |
Scenario Outline: admin user set an user personal space quota of via the Graph API
Scenario Outline: admin user set an user personal space quota of via the Graph API and upload resource
When user "Admin" changes the quota of the "Brian Murphy" space to "<quotaValue>"
Then the HTTP status code should be "200"
When user "Brian" uploads a file inside space "Brian Murphy" with content "file is more than 15 bytes" to "file.txt" using the WebDAV API
Then the HTTP status code should be <code>
And for user "Brian" the JSON response should contain space called "Brian Murphy" and match
"""
{
"type": "object",
"required": [
"name",
"quota"
],
"properties": {
"name": {
"type": "string",
"enum": ["Brian Murphy"]
},
"quota": {
"type": "object",
"required": [
"used",
"total"
],
"properties": {
"used" : {
"type": "number",
"enum": [<used>]
},
"total" : {
"type": "number",
"enum": [<total>]
}
}
}
}
}
"""
And for user "Brian" the space "Personal" should contain these entries:
| file.txt |
Examples:
| quotaValue | code | total | used |
| 15 | "507" | 15 | 0 |
| 10000 | between "201" and "204" | 10000 | 26 |
| 0 | between "201" and "204" | 0 | 26 |
| -1 | between "201" and "204" | 0 | 26 |
| quotaValue | code |
| 10000 | between "201" and "204" |
| 0 | between "201" and "204" |
| -1 | between "201" and "204" |
Scenario: user sends invalid space uuid via the graph API

126
tests/acceptance/features/apiSpaces/disableAndDeleteSpaces.feature
View File

@@ -28,42 +28,6 @@ Feature: Disabling and deleting space
Given the administrator has given "Alice" the role "<role>" using the settings api
When user "Alice" disables a space "Project Moon"
Then the HTTP status code should be "204"
And for user "Alice" the JSON response should contain space called "Project Moon" and match
"""
{
"type": "object",
"required": [
"name",
"root"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Moon"]
},
"root": {
"type": "object",
"required": [
"deleted"
],
"properties": {
"deleted": {
"type": "object",
"required": [
"state"
],
"properties": {
"state": {
"type": "string",
"enum": ["trashed"]
}
}
}
}
}
}
}
"""
And the user "Brian" should not have a space called "Project Moon"
And the user "Bob" should not have a space called "Project Moon"
Examples:
@@ -78,36 +42,8 @@ Feature: Disabling and deleting space
Given the administrator has given "Carol" the role "<role>" using the settings api
When user "Carol" tries to disable a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "403"
And for user "Brian" the JSON response should contain space called "Project Moon" and match
"""
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Moon"]
}
}
}
"""
And for user "Bob" the JSON response should contain space called "Project Moon" and match
"""
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Moon"]
}
}
}
"""
And the user "Brian" should have a space called "Project Moon"
And the user "Bob" should have a space called "Project Moon"
Examples:
| role |
| User |
@@ -128,21 +64,7 @@ Feature: Disabling and deleting space
Given the administrator has given "Alice" the role "<role>" using the settings api
When user "Alice" deletes a space "Project Moon"
Then the HTTP status code should be "400"
And for user "Alice" the JSON response should contain space called "Project Moon" and match
"""
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Moon"]
}
}
}
"""
And the user "Alice" should have a space called "Project Moon"
Examples:
| role |
| Admin |
@@ -167,44 +89,9 @@ Feature: Disabling and deleting space
Scenario Outline: an admin and space manager can disable other space via the Graph API
Given the administrator has given "Carol" the role "<role>" using the settings api
When user "Carol" tries to disable a space "Project Moon" owned by user "Alice"
When user "Carol" disables a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "204"
And for user "Alice" the JSON response should contain space called "Project Moon" and match
"""
{
"type": "object",
"required": [
"name",
"root"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Moon"]
},
"root": {
"type": "object",
"required": [
"deleted"
],
"properties": {
"deleted": {
"type": "object",
"required": [
"state"
],
"properties": {
"state": {
"type": "string",
"enum": ["trashed"]
}
}
}
}
}
}
}
"""
And the user "Carol" should not have a space called "Project Moon"
Examples:
| role |
| Admin |
@@ -214,9 +101,10 @@ Feature: Disabling and deleting space
Scenario Outline: an admin and space manager can delete other disabled Space
Given the administrator has given "Carol" the role "<role>" using the settings api
And user "Alice" has disabled a space "Project Moon"
When user "Carol" tries to delete a space "Project Moon" owned by user "Alice"
When user "Carol" deletes a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "204"
And the user "Alice" should not have a space called "Project Moon"
And the user "Carol" should not have a space called "Project Moon"
Examples:
| role |
| Admin |

25
tests/acceptance/features/apiSpaces/listSpaces.feature
View File

@@ -83,31 +83,6 @@ Feature: List and create spaces
And user "Brian" has created folder "folder"
And user "Brian" has shared folder "folder" with user "Alice" with permissions "31"
And user "Alice" has accepted share "/folder" offered by user "Brian"
Then for user "Alice" the JSON response should contain space called "Shares" and match
"""
{
"type": "object",
"required": [
"driveType",
"id",
"name"
],
"properties": {
"driveType": {
"type": "string",
"enum": ["virtual"]
},
"id": {
"type": "string",
"enum": ["%space_id%"]
},
"name": {
"type": "string",
"enum": ["Shares"]
}
}
}
"""
When user "Alice" lists all available spaces via the GraphApi with query "$filter=driveType eq 'personal'"
Then the HTTP status code should be "200"
And the JSON response should contain space called "Alice Hansen" and match

5
tests/acceptance/features/apiSpaces/quota.feature
View File

@@ -4,7 +4,7 @@ Feature: State of the quota
I want to be able to see the state of the quota
So that I will not let the quota overrun
quota state indication:
| 0 - 75% | normal |
| 76 - 90% | nearing |
@@ -23,7 +23,8 @@ Feature: State of the quota
Scenario Outline: quota information is returned in the list of spaces returned via the Graph API
Given user "Alice" has created a space "<spaceName>" of type "project" with quota "<total>"
When user "Alice" uploads a file inside space "<spaceName>" with content "<fileContent>" to "test.txt" using the WebDAV API
Then for user "Alice" the JSON response should contain space called "<spaceName>" and match
And user "Alice" lists all available spaces via the GraphApi
Then the JSON response should contain space called "<spaceName>" and match
"""
{
"type": "object",

45
tests/acceptance/features/apiSpaces/removeSpaceObjects.feature
View File

@@ -64,34 +64,6 @@ Feature: Remove files, folder
And for user "<user>" the space "delete objects" <shouldOrNotBeInSpace> contain these entries:
| text.txt |
And as "<user>" file "text.txt" <shouldOrNotBeInTrash> exist in the trashbin of the space "delete objects"
And for user "<user>" the JSON response should contain space called "delete objects" and match
"""
{
"type": "object",
"required": [
"name",
"quota"
],
"properties": {
"name": {
"type": "string",
"enum": ["delete objects"]
},
"quota": {
"type": "object",
"required": [
"used"
],
"properties": {
"used": {
"type": "number",
"enum": [<quotaValue>]
}
}
}
}
}
"""
Examples:
| user | role | code | shouldOrNotBeInSpace | shouldOrNotBeInTrash | quotaValue |
| Alice | manager | 204 | should not | should | 0 |
@@ -100,21 +72,6 @@ Feature: Remove files, folder
| Brian | viewer | 403 | should | should not | 12 |
Scenario: user is unable to delete a space via the webDav API
Scenario: try to delete an empty string folder from a space
When user "Alice" removes the folder "" from space "delete objects"
Then the HTTP status code should be "405"
And for user "Alice" the JSON response should contain space called "delete objects" and match
"""
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"enum": ["delete objects"]
}
}
}
"""

34
tests/acceptance/features/apiSpaces/restoreSpaceObjects.feature
View File

@@ -82,37 +82,3 @@ Feature: Restore files, folder
When user "Brian" restores version index "1" of file "/file.txt" using the WebDAV API
Then the HTTP status code should be "204"
And the content of file "/file.txt" for user "Brian" should be "file is less than 30 bytes"
And for user "Brian" the JSON response should contain space called "Brian Murphy" and match
"""
{
"type": "object",
"required": [
"quota"
],
"properties": {
"quota": {
"type": "object",
"required": [
"state",
"total",
"remaining",
"used"
],
"properties": {
"state" : {
"type": "string",
"enum": ["exceeded"]
},
"total" : {
"type": "number",
"enum": [30]
},
"used": {
"type": "number",
"enum": [38]
}
}
}
}
}
"""

80
tests/acceptance/features/apiSpaces/setQuota.feature
View File

@@ -16,7 +16,7 @@ Feature: Set quota
And the administrator has given "Brian" the role "<userRole>" using the settings api
When user "Alice" changes the quota of the "Brian Murphy" space to "100" owned by user "Brian"
Then the HTTP status code should be "200"
And for user "Brian" the JSON response should contain space called "Brian Murphy" and match
And the JSON data of the response should match
"""
{
"type": "object",
@@ -52,29 +52,6 @@ Feature: Set quota
And the administrator has given "Brian" the role "<userRole>" using the settings api
When user "Alice" changes the quota of the "Brian Murphy" space to "100" owned by user "Brian"
Then the HTTP status code should be "403"
And for user "Brian" the JSON response should contain space called "Brian Murphy" and match
"""
{
"type": "object",
"required": [
"quota"
],
"properties": {
"quota": {
"type": "object",
"required": [
"total"
],
"properties": {
"total" : {
"type": "number",
"enum": [0]
}
}
}
}
}
"""
Examples:
| role | userRole |
| Space Admin | Admin |
@@ -97,7 +74,7 @@ Feature: Set quota
And user "Alice" has created a space "Project Jupiter" of type "project" with quota "20"
When user "Brian" changes the quota of the "Project Jupiter" space to "100" owned by user "Alice"
Then the HTTP status code should be "200"
And for user "Alice" the JSON response should contain space called "Project Jupiter" and match
And the JSON data of the response should match
"""
{
"type": "object",
@@ -140,34 +117,6 @@ Feature: Set quota
| role | <spaceRole> |
When user "Brian" changes the quota of the "Project Jupiter" space to "100"
Then the HTTP status code should be "403"
And for user "Alice" the JSON response should contain space called "Project Jupiter" and match
"""
{
"type": "object",
"required": [
"name",
"quota"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Jupiter"]
},
"quota": {
"type": "object",
"required": [
"total"
],
"properties": {
"total" : {
"type": "number",
"enum": [20]
}
}
}
}
}
"""
Examples:
| userRole | spaceRole |
| User | viewer |
@@ -182,7 +131,7 @@ Feature: Set quota
Given the administrator has given "Alice" the role "Admin" using the settings api
When user "Alice" changes the quota of the "Alice Hansen" space to "100" owned by user "Alice"
Then the HTTP status code should be "200"
And for user "Alice" the JSON response should contain space called "Alice Hansen" and match
And the JSON data of the response should match
"""
{
"type": "object",
@@ -211,29 +160,6 @@ Feature: Set quota
Given the administrator has given "Alice" the role "<userRole>" using the settings api
When user "Alice" changes the quota of the "Alice Hansen" space to "100" owned by user "Alice"
Then the HTTP status code should be "403"
And for user "Alice" the JSON response should contain space called "Alice Hansen" and match
"""
{
"type": "object",
"required": [
"quota"
],
"properties": {
"quota": {
"type": "object",
"required": [
"total"
],
"properties": {
"total" : {
"type": "number",
"enum": [0]
}
}
}
}
}
"""
Examples:
| userRole |
| Space Admin |

145
tests/acceptance/features/apiSpaces/spaceManagement.feature
View File

@@ -94,7 +94,7 @@ Feature: Space management
Scenario: space admin user changes the name of the project space
When user "Brian" changes the name of the "Project" space to "New Name" owned by user "Alice"
Then the HTTP status code should be "200"
And for user "Alice" the JSON response should contain space called "New Name" and match
And the JSON data of the response should match
"""
{
"type": "object",
@@ -114,27 +114,13 @@ Feature: Space management
Scenario: user without space admin permission tries to change the name of the project space
When user "Carol" tries to change the name of the "Project" space to "New Name" owned by user "Alice"
Then the HTTP status code should be "403"
And for user "Alice" the JSON response should contain space called "Project" and match
"""
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project"]
}
}
}
"""
And the user "Alice" should have a space called "Project"
@skipOnStable2.0
Scenario: space admin user changes the description of the project space
When user "Brian" changes the description of the "Project" space to "New description" owned by user "Alice"
Then the HTTP status code should be "200"
And for user "Alice" the JSON response should contain space called "Project" and match
And the JSON data of the response should match
"""
{
"type": "object",
@@ -155,62 +141,12 @@ Feature: Space management
Given user "Alice" has changed the description of the "Project" space to "old description"
When user "Carol" tries to change the description of the "Project" space to "New description" owned by user "Alice"
Then the HTTP status code should be "403"
And for user "Alice" the JSON response should contain space called "Project" and match
"""
{
"type": "object",
"required": [
"description"
],
"properties": {
"description": {
"type": "string",
"enum": ["old description"]
}
}
}
"""
@skipOnStable2.0
Scenario: space admin user disables the project space
When user "Brian" disables a space "Project" owned by user "Alice"
Then the HTTP status code should be "204"
And for user "Alice" the JSON response should contain space called "Project" and match
"""
{
"type": "object",
"required": [
"name",
"root"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project"]
},
"root": {
"type": "object",
"required": [
"deleted"
],
"properties": {
"deleted": {
"type": "object",
"required": [
"state"
],
"properties": {
"state": {
"type": "string",
"enum": ["trashed"]
}
}
}
}
}
}
}
"""
And the user "Brian" should not have a space called "Project"
Scenario: user without space admin permission tries to disable the project space
@@ -238,42 +174,6 @@ Feature: Space management
Given user "Alice" has disabled a space "Project"
When user "Carol" tries to delete a space "Project" owned by user "Alice"
Then the HTTP status code should be "403"
And for user "Alice" the JSON response should contain space called "Project" and match
"""
{
"type": "object",
"required": [
"name",
"root"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project"]
},
"root": {
"type": "object",
"required": [
"deleted"
],
"properties": {
"deleted": {
"type": "object",
"required": [
"state"
],
"properties": {
"state": {
"type": "string",
"enum": ["trashed"]
}
}
}
}
}
}
}
"""
@skipOnStable2.0
Scenario: space admin user enables the project space
@@ -286,39 +186,4 @@ Feature: Space management
Given user "Alice" has disabled a space "Project"
When user "Carol" tries to restore a disabled space "Project" owned by user "Alice"
Then the HTTP status code should be "404"
And for user "Alice" the JSON response should contain space called "Project" and match
"""
{
"type": "object",
"required": [
"name",
"root"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project"]
},
"root": {
"type": "object",
"required": [
"deleted"
],
"properties": {
"deleted": {
"type": "object",
"required": [
"state"
],
"properties": {
"state": {
"type": "string",
"enum": ["trashed"]
}
}
}
}
}
}
}
"""
And the user "Alice" should have a space "Project" in the disable state

36
tests/acceptance/features/apiSpaces/uploadSpaces.feature
View File

@@ -41,39 +41,11 @@ Feature: Upload files into a space
Then the HTTP status code should be "<code>"
And for user "Brian" the space "Project Ceres" <shouldOrNot> contain these entries:
| test.txt |
And for user "Brian" the JSON response should contain space called "Project Ceres" and match
"""
{
"type": "object",
"required": [
"name",
"quota"
],
"properties": {
"name": {
"type": "string",
"enum": ["Project Ceres"]
},
"quota": {
"type": "object",
"required": [
"used"
],
"properties": {
"used": {
"type": "number",
"enum": [<usedQuota>]
}
}
}
}
}
"""
Examples:
| role | code | shouldOrNot | usedQuota |
| manager | 201 | should | 4 |
| editor | 201 | should | 4 |
| viewer | 403 | should not | 0 |
| role | code | shouldOrNot |
| manager | 201 | should |
| editor | 201 | should |
| viewer | 403 | should not |
Scenario: user can create subfolders in a space via the Graph API

180
tests/acceptance/features/apiSpacesShares/shareSpaces.feature
View File

@@ -25,31 +25,7 @@ Feature: Share spaces
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 for user "Brian" the JSON response should contain space called "share space" and match
"""
{
"type": "object",
"required": [
"name",
"driveType",
"id"
],
"properties": {
"name": {
"type": "string",
"enum": ["share space"]
},
"driveType": {
"type": "string",
"enum": ["project"]
},
"id": {
"type": "string",
"pattern": "^%space_id_pattern%$"
}
}
}
"""
And the user "Brian" should have a space called "share space"
Examples:
| role |
| manager |
@@ -90,31 +66,6 @@ Feature: Share spaces
Given user "Alice" has shared a space "share space" with settings:
| shareWith | Brian |
| role | viewer |
And for user "Brian" the JSON response should contain space called "share space" and match
"""
{
"type": "object",
"required": [
"name",
"driveType",
"id"
],
"properties": {
"name": {
"type": "string",
"enum": ["share space"]
},
"driveType": {
"type": "string",
"enum": ["project"]
},
"id": {
"type": "string",
"pattern": "^%space_id_pattern%$"
}
}
}
"""
When user "Alice" unshares a space "share space" to user "Brian"
Then the HTTP status code should be "200"
But the user "Brian" should not have a space called "share space"
@@ -126,31 +77,6 @@ Feature: Share spaces
| role | manager |
When user "<user>" unshares a space "share space" to user "Alice"
Then the HTTP status code should be "200"
And for user "Brian" the JSON response should contain space called "share space" owned by "Alice" and match
"""
{
"type": "object",
"required": [
"name",
"driveType",
"id"
],
"properties": {
"name": {
"type": "string",
"enum": ["share space"]
},
"driveType": {
"type": "string",
"enum": ["project"]
},
"id": {
"type": "string",
"pattern": "^%space_id_pattern%$"
}
}
}
"""
But the user "Alice" should not have a space called "share space"
Examples:
| user |
@@ -198,31 +124,7 @@ Feature: Share spaces
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 for user "Brian" the JSON response should contain space called "share space" and match
"""
{
"type": "object",
"required": [
"name",
"driveType",
"id"
],
"properties": {
"name": {
"type": "string",
"enum": ["share space"]
},
"driveType": {
"type": "string",
"enum": ["project"]
},
"id": {
"type": "string",
"pattern": "^%space_id_pattern%$"
}
}
}
"""
And the user "Bob" should have a space called "share space"
Examples:
| role |
| manager |
@@ -301,56 +203,8 @@ Feature: Share spaces
| shareType | 8 |
| role | <role> |
Then the HTTP status code should be "200"
And for user "Brian" the JSON response should contain space called "share space" and match
"""
{
"type": "object",
"required": [
"name",
"driveType",
"id"
],
"properties": {
"name": {
"type": "string",
"enum": ["share space"]
},
"driveType": {
"type": "string",
"enum": ["project"]
},
"id": {
"type": "string",
"pattern": "^%space_id_pattern%$"
}
}
}
"""
And for user "Bob" the JSON response should contain space called "share space" and match
"""
{
"type": "object",
"required": [
"name",
"driveType",
"id"
],
"properties": {
"name": {
"type": "string",
"enum": ["share space"]
},
"driveType": {
"type": "string",
"enum": ["project"]
},
"id": {
"type": "string",
"pattern": "^%space_id_pattern%$"
}
}
}
"""
And the user "Brian" should have a space called "share space"
And the user "Bob" should have a space called "share space"
Examples:
| role |
| manager |
@@ -388,31 +242,7 @@ Feature: Share spaces
| Brian | group2 |
Then the HTTP status code of responses on all endpoints should be "204"
And the user "Brian" should not have a space called "share space"
But for user "Bob" the JSON response should contain space called "share space" and match
"""
{
"type": "object",
"required": [
"name",
"driveType",
"id"
],
"properties": {
"name": {
"type": "string",
"enum": ["share space"]
},
"driveType": {
"type": "string",
"enum": ["project"]
},
"id": {
"type": "string",
"pattern": "^%space_id_pattern%$"
}
}
}
"""
But the user "Bob" should have a space called "share space"
@skipOnStable2.0
Scenario: users don't have access to the space if the group has been deleted

72
tests/acceptance/features/bootstrap/SpacesContext.php
View File

@@ -876,6 +876,7 @@ class SpacesContext implements Context {
?PyStringNode $schemaString = null
): void {
Assert::assertNotNull($schemaString, 'schema is not valid JSON');
if (isset($this->featureContext->getJsonDecodedResponseBodyContent()->value)) {
$responseBody = $this->featureContext->getJsonDecodedResponseBodyContent()->value;
foreach ($responseBody as $value) {
@@ -919,38 +920,13 @@ class SpacesContext implements Context {
null,
$userName,
);
JsonAssertions::assertJsonDocumentMatchesSchema(
$responseBody,
$this->featureContext->getJSONSchema($schemaString)
);
}
/**
* @Then /^for user "([^"]*)" the JSON response of space project should match$/
* @Then /^for user "([^"]*)" the JSON response should contain space called "([^"]*)" and match$/
* @Then /^for user "([^"]*)" the JSON response should contain space called "([^"]*)" (?:owned by|granted to) "([^"]*)" and match$/
* @Then /^for user "([^"]*)" the JSON response should contain space called "([^"]*)" (?:owned by|granted to) "([^"]*)" (?:with description file|with space image) "([^"]*)" and match$/
*
* @param string $user
* @param string|null $spaceName
* @param string|null $grantedUser
* @param string|null $fileName
* @param PyStringNode|null $schemaString
*
* @return void
* @throws GuzzleException
*/
public function forUserTheJSONDataOfTheResponseShouldMatch(
string $user,
?string $spaceName = null,
?string $grantedUser = null,
?string $fileName = null,
?PyStringNode $schemaString = null
): void {
$this->theUserListsAllHisAvailableSpacesUsingTheGraphApi($user);
$this->theJsonDataFromLastResponseShouldMatch($spaceName, $grantedUser, $fileName, $schemaString);
}
/**
* @Then /^the user "([^"]*)" should have a space called "([^"]*)" granted to "([^"]*)" with role "([^"]*)"$/
*
@@ -1003,15 +979,42 @@ class SpacesContext implements Context {
}
/**
* @Then /^the user "([^"]*)" should not have a space called "([^"]*)"$/
* @Then /^the user "([^"]*)" should (not |)have a space called "([^"]*)"$/
*
* @param string $user
* @param string $shouldOrNot
* @param string $spaceName
*
* @return void
* @throws Exception
*/
public function userShouldNotHaveSpace(
string $user,
string $shouldOrNot,
string $spaceName
): void {
$this->theUserListsAllHisAvailableSpacesUsingTheGraphApi($user);
$this->featureContext->theHTTPStatusCodeShouldBe(
200,
"Expected response status code should be 200"
);
if (\trim($shouldOrNot) === "not") {
$this->jsonRespondedShouldNotContain($spaceName);
} else {
Assert::assertNotEmpty($this->getSpaceByNameFromResponse($spaceName), "space '$spaceName' should be available for a user '$user' but not found");
}
}
/**
* @Then /^the user "([^"]*)" should have a space "([^"]*)" in the disable state$/
*
* @param string $user
* @param string $spaceName
*
* @return mixed
* @throws Exception
*/
public function theUserShouldHaveASpaceInTheDisableState(
string $user,
string $spaceName
): void {
@@ -1020,7 +1023,20 @@ class SpacesContext implements Context {
200,
"Expected response status code should be 200"
);
$this->jsonRespondedShouldNotContain($spaceName);
$response = json_decode((string)$this->featureContext->getResponse()->getBody(), true, 512, JSON_THROW_ON_ERROR);
if (isset($response["value"])) {
foreach ($response["value"] as $spaceCandidate) {
if ($spaceCandidate['name'] === $spaceName) {
if ($spaceCandidate['root']['deleted']['state'] !== 'trashed') {
throw new \Exception(
"space $spaceName should be in disable state but it's not "
);
}
return;
}
}
}
throw new \Exception("space '$spaceName' should be available for a user '$user' but not found");
}
/**