-
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.
[tests-only][full-ci]Extend tests coverage for different role capabil…
…ity for spaces (#5853) * Add tests related to different user role manipulating space * Review addressed * Refactor existing scenario
- Loading branch information
1 parent
1ddd06b
commit 4af7f1a
Showing
8 changed files
with
441 additions
and
302 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
156 changes: 156 additions & 0 deletions
156
tests/acceptance/features/apiSpaces/createSpace.feature
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,156 @@ | ||
| @api | ||
| Feature: create space | ||
| As an admin and space admin | ||
| I want to create new spaces | ||
| So that I can organize a set of resources in a hierarchical tree | ||
|
|
||
| Background: | ||
| Given user "Alice" has been created with default attributes and without skeleton files | ||
|
|
||
|
|
||
| Scenario Outline: user with role user and guest 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 | | ||
|
|
||
|
|
||
| Scenario Outline: an admin or space admin user can create a Space via the Graph API with a default quota | ||
| Given the administrator has given "Alice" the role "<role>" using the settings api | ||
| When user "Alice" creates a space "Project Mars" of type "project" with the default quota using the Graph API | ||
| Then the HTTP status code should be "201" | ||
| And the JSON response should contain space called "Project Mars" and match | ||
| """ | ||
| { | ||
| "type": "object", | ||
| "required": [ | ||
| "driveType", | ||
| "driveAlias", | ||
| "name", | ||
| "id", | ||
| "quota", | ||
| "root", | ||
| "webUrl" | ||
| ], | ||
| "properties": { | ||
| "name": { | ||
| "type": "string", | ||
| "enum": ["Project Mars"] | ||
| }, | ||
| "driveType": { | ||
| "type": "string", | ||
| "enum": ["project"] | ||
| }, | ||
| "driveAlias": { | ||
| "type": "string", | ||
| "enum": ["project/project-mars"] | ||
| }, | ||
| "id": { | ||
| "type": "string", | ||
| "enum": ["%space_id%"] | ||
| }, | ||
| "quota": { | ||
| "type": "object", | ||
| "required": [ | ||
| "total" | ||
| ], | ||
| "properties": { | ||
| "state": { | ||
| "type": "number", | ||
| "enum": [1000000000] | ||
| } | ||
| } | ||
| }, | ||
| "root": { | ||
| "type": "object", | ||
| "required": [ | ||
| "webDavUrl" | ||
| ], | ||
| "properties": { | ||
| "webDavUrl": { | ||
| "type": "string", | ||
| "enum": ["%base_url%/dav/spaces/%space_id%"] | ||
| } | ||
| } | ||
| }, | ||
| "webUrl": { | ||
| "type": "string", | ||
| "enum": ["%base_url%/f/%space_id%"] | ||
| } | ||
| } | ||
| } | ||
| """ | ||
| Examples: | ||
| | role | | ||
| | Admin | | ||
| | Space Admin | | ||
|
|
||
|
|
||
| Scenario Outline: an admin or space admin user can create a Space via the Graph API with certain quota | ||
| Given the administrator has given "Alice" the role "<role>" using the settings api | ||
| When user "Alice" creates a space "Project Venus" of type "project" with quota "2000" using the Graph API | ||
| Then the HTTP status code should be "201" | ||
| And the JSON response should contain space called "Project Venus" and match | ||
| """ | ||
| { | ||
| "type": "object", | ||
| "required": [ | ||
| "driveType", | ||
| "name", | ||
| "id", | ||
| "quota", | ||
| "root", | ||
| "webUrl" | ||
| ], | ||
| "properties": { | ||
| "name": { | ||
| "type": "string", | ||
| "enum": ["Project Venus"] | ||
| }, | ||
| "driveType": { | ||
| "type": "string", | ||
| "enum": ["project"] | ||
| }, | ||
| "id": { | ||
| "type": "string", | ||
| "enum": ["%space_id%"] | ||
| }, | ||
| "quota": { | ||
| "type": "object", | ||
| "required": [ | ||
| "total" | ||
| ], | ||
| "properties": { | ||
| "state": { | ||
| "type": "number", | ||
| "enum": [2000] | ||
| } | ||
| } | ||
| }, | ||
| "root": { | ||
| "type": "object", | ||
| "required": [ | ||
| "webDavUrl" | ||
| ], | ||
| "properties": { | ||
| "webDavUrl": { | ||
| "type": "string", | ||
| "enum": ["%base_url%/dav/spaces/%space_id%"] | ||
| } | ||
| } | ||
| }, | ||
| "webUrl": { | ||
| "type": "string", | ||
| "enum": ["%base_url%/f/%space_id%"] | ||
| } | ||
| } | ||
| } | ||
| """ | ||
| Examples: | ||
| | role | | ||
| | Admin | | ||
| | Space Admin | |
130 changes: 0 additions & 130 deletions
130
tests/acceptance/features/apiSpaces/deleteSpaces.feature
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.