Merge pull request #6456 from owncloud/release-3.0.0

[full-ci] Release 3.0.0
This commit is contained in:
Michael Barz
2023-06-07 08:22:11 +02:00
committed by GitHub
138 changed files with 189 additions and 191 deletions
@@ -520,7 +520,7 @@ Feature: Change data of space
| Admin |
| Space Admin |
| User |
| Guest |
| User Light |
Scenario Outline: admin user set own quota of a personal space via the Graph API and upload resource
@@ -8,15 +8,15 @@ Feature: create space
Given user "Alice" has been created with default attributes and without skeleton files
@issue-5938
Scenario Outline: user with role user and guest can't create space via Graph API
Scenario Outline: user with role user and user light can't create space via Graph API
Given the administrator has given "Alice" the role "<role>" using the settings api
When user "Alice" tries to create a space "Project Mars" of type "project" with the default quota using the Graph API
Then the HTTP status code should be "403"
And the user "Alice" should not have a space called "share space"
Examples:
| role |
| User |
| Guest |
| role |
| User |
| User Light |
Scenario Outline: admin or space admin user can create a space via the Graph API with a default quota
@@ -35,19 +35,19 @@ Feature: Disabling and deleting space
| Admin |
| Space Admin |
| User |
| Guest |
| User Light |
Scenario Outline: user with role user and guest cannot disable other space via the Graph API
Scenario Outline: user with role user and user light cannot 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"
Then the HTTP status code should be "404"
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 |
| Guest |
| role |
| User |
| User Light |
Scenario: a space manager can disable and delete space in which files and folders exist via the webDav API
@@ -70,7 +70,7 @@ Feature: Disabling and deleting space
| Admin |
| Space Admin |
| User |
| Guest |
| User Light |
Scenario Outline: user can delete their own disabled space via the Graph API
@@ -84,7 +84,7 @@ Feature: Disabling and deleting space
| Admin |
| Space Admin |
| User |
| Guest |
| User Light |
Scenario Outline: an admin and space manager can disable other space via the Graph API
@@ -111,12 +111,12 @@ Feature: Disabling and deleting space
| Space Admin |
Scenario Outline: user with role user and guest cannot delete others disabled space via the Graph API
Scenario Outline: user with role user and user light cannot delete others disabled space via the Graph API
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"
Then the HTTP status code should be "404"
Examples:
| role |
| User |
| Guest |
| role |
| User |
| User Light |
@@ -1,4 +1,4 @@
@api
@api
Feature: List and create spaces
As a user
I want to be able to list project spaces
@@ -429,4 +429,4 @@ Feature: List and create spaces
| Admin |
| Space Admin |
| User |
| Guest |
| User Light |
@@ -1,4 +1,4 @@
@api
@api
Feature: Restoring space
As a manager of space
I want to be able to restore a disabled space
@@ -72,15 +72,15 @@ Feature: Restoring space
| editor |
Scenario Outline: user with role user and guest cannot restore space
Scenario Outline: user with role user and user light cannot restore space
Given the administrator has given "Brian" the role "<role>" using the settings api
And user "Alice" has disabled a space "restore a space"
When user "Brian" tries to restore a disabled space "restore a space" owned by user "Alice"
Then the HTTP status code should be "404"
Examples:
| role |
| User |
| Guest |
| role |
| User |
| User Light |
@issue-5872
Scenario Outline: admin and space admin can restore other space
@@ -44,7 +44,7 @@ Feature: Set quota
| Admin |
| Space Admin |
| User |
| Guest |
| User Light |
Scenario Outline: non-admin user tries to set the personal space quota of other users
@@ -57,15 +57,15 @@ Feature: Set quota
| Space Admin | Admin |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | Guest |
| Space Admin | User Light |
| User | Admin |
| User | Space Admin |
| User | User |
| User | Guest |
| Guest | Admin |
| Guest | Space Admin |
| Guest | User |
| Guest | Guest |
| User | User Light |
| User Light | Admin |
| User Light | Space Admin |
| User Light | User |
| User Light | User Light |
Scenario Outline: admin or space admin user sets a quota of a project space
@@ -108,7 +108,7 @@ Feature: Set quota
| Space Admin |
Scenario Outline: normal or guest user tries to set quota of a space
Scenario Outline: normal or user light user tries to set quota of a space
Given the administrator has given "Alice" the role "Space Admin" using the settings api
And the administrator has given "Brian" the role "<userRole>" using the settings api
And user "Alice" has created a space "Project Jupiter" of type "project" with quota "20"
@@ -118,13 +118,13 @@ Feature: Set quota
When user "Brian" changes the quota of the "Project Jupiter" space to "100"
Then the HTTP status code should be "403"
Examples:
| userRole | spaceRole |
| User | viewer |
| User | editor |
| User | manager |
| Guest | viewer |
| Guest | editor |
| Guest | manager |
| userRole | spaceRole |
| User | viewer |
| User | editor |
| User | manager |
| User Light | viewer |
| User Light | editor |
| User Light | manager |
Scenario: admin user can set their own personal space quota
@@ -164,4 +164,4 @@ Feature: Set quota
| userRole |
| Space Admin |
| User |
| Guest |
| User Light |