-
Notifications
You must be signed in to change notification settings - Fork 187
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
api test to set quota by users with different roles (#5854)
- Loading branch information
1 parent
264aacc
commit 27fa742
Showing
1 changed file
with
178 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,178 @@ | ||
| @api | ||
| Feature: Set quota | ||
| As a user | ||
| I want to set quota to different users | ||
| So that users can only take up a certain amount of storage space | ||
|
|
||
| Background: | ||
| Given these users have been created with default attributes and without skeleton files: | ||
| | username | | ||
| | Alice | | ||
| | Brian | | ||
|
|
||
|
|
||
| Scenario Outline: admin sets personal space quota of user with different role | ||
| Given the administrator has given "Alice" the role "Admin" using the settings api | ||
| 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 | ||
| """ | ||
| { | ||
| "type": "object", | ||
| "required": [ | ||
| "quota" | ||
| ], | ||
| "properties": { | ||
| "quota": { | ||
| "type": "object", | ||
| "required": [ | ||
| "total" | ||
| ], | ||
| "properties": { | ||
| "total" : { | ||
| "type": "number", | ||
| "enum": [100] | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
| """ | ||
| Examples: | ||
| | userRole | | ||
| | Admin | | ||
| | Space Admin | | ||
| | User | | ||
| | Guest | | ||
|
|
||
|
|
||
| Scenario Outline: non-admin user tries to set the personal space quota of other users | ||
| Given the administrator has given "Alice" the role "<role>" using the settings api | ||
| 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 "401" | ||
| 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 | | ||
| | Space Admin | Space Admin | | ||
| | Space Admin | User | | ||
| | Space Admin | Guest | | ||
| | User | Admin | | ||
| | User | Space Admin | | ||
| | User | User | | ||
| | User | Guest | | ||
| | Guest | Admin | | ||
| | Guest | Space Admin | | ||
| | Guest | User | | ||
| | Guest | Guest | | ||
|
|
||
|
|
||
| Scenario Outline: admin or space admin user sets a quota of a project 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" | ||
| 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 | ||
| """ | ||
| { | ||
| "type": "object", | ||
| "required": [ | ||
| "name", | ||
| "quota" | ||
| ], | ||
| "properties": { | ||
| "name": { | ||
| "type": "string", | ||
| "enum": ["Project Jupiter"] | ||
| }, | ||
| "quota": { | ||
| "type": "object", | ||
| "required": [ | ||
| "total" | ||
| ], | ||
| "properties": { | ||
| "total" : { | ||
| "type": "number", | ||
| "enum": [100] | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
| """ | ||
| Examples: | ||
| | userRole | | ||
| | Admin | | ||
| | Space Admin | | ||
|
|
||
|
|
||
| Scenario Outline: normal or guest 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" | ||
| And user "Alice" has shared a space "Project Jupiter" with settings: | ||
| | shareWith | Brian | | ||
| | role | <spaceRole> | | ||
| When user "Brian" changes the quota of the "Project Jupiter" space to "100" | ||
| Then the HTTP status code should be "401" | ||
| 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 | | ||
| | User | editor | | ||
| | User | manager | | ||
| | Guest | viewer | | ||
| | Guest | editor | | ||
| | Guest | manager | |