mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-03-31 13:52:10 -04:00
Code Issues Packages Projects Releases Wiki Activity

tests: add test cases for non-admin actions to admin resources

Browse Source
This commit is contained in:
Saw-jan
2024-07-18 16:17:52 +05:45
parent 81ef018b9f
commit dd8a3eb3d2
15 changed files with 273 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
tests/acceptance/features/apiGraph/changeRole.feature
View File

@@ -58,3 +58,15 @@ Feature: change role
| Space Admin |
| User |
| User Light |
Scenario Outline: non-admin user tries to change the role of nonexistent user
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
And user "Brian" has been created with default attributes and without skeleton files
When user "Alice" tries to change the role of user "nonexistent" to role "Admin" using the Graph API
Then the HTTP status code should be "403"
Examples:
| user-role |
| Space Admin |
| User |
| User Light |

30
tests/acceptance/features/apiGraph/assignRole.feature → tests/acceptance/features/apiGraph/getAssignedRole.feature
View File

@@ -3,10 +3,12 @@ Feature: assign role
I want to assign roles to users.
So that users without an admin role cannot get the list of roles, assignments list and assign roles to users
Scenario Outline: assign role to the user using graph api
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
Scenario Outline: get assigned role of a user
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
When the administrator retrieves the assigned role of user "Alice" using the Graph API
Then the HTTP status code should be "200"
And the Graph API response should have the role "<user-role>"
@@ -18,9 +20,8 @@ Feature: assign role
| User Light |
@issue-5032
Scenario Outline: assign role to the user with graph api and list role with setting api
Given user "Alice" has been created with default attributes and without skeleton files
And the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
Scenario Outline: get assigned role of a user via setting api
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
When user "Alice" tries to get list of assignment
Then the HTTP status code should be "<http-status-code>"
And the setting API response should have the role "<user-role>"
@@ -32,9 +33,8 @@ Feature: assign role
| User Light | 401 |
Scenario Outline: assign role to the user with setting api and list role with graph api
Given user "Alice" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "<user-role>" using the settings api
Scenario Outline: get role of a user assigned via setting api
Given the administrator has given "Alice" the role "<user-role>" using the settings api
When the administrator retrieves the assigned role of user "Alice" using the Graph API
Then the HTTP status code should be "200"
And the Graph API response should have the role "<user-role>"
@@ -44,3 +44,15 @@ Feature: assign role
| Space Admin |
| User |
| User Light |
Scenario: non-admin user tries to get assigned role of another user
Given user "Brian" has been created with default attributes and without skeleton files
When user "Alice" tries to get the assigned role of user "Brian" using the Graph API
Then the HTTP status code should be "403"
Scenario: non-admin user tries to get assigned role of nonexistent user
Given user "Brian" has been created with default attributes and without skeleton files
When user "Alice" tries to get the assigned role of user "nonexistent" using the Graph API
Then the HTTP status code should be "403"

12
tests/acceptance/features/apiGraph/unassignRole.feature
View File

@@ -29,3 +29,15 @@ Feature: unassign user role
When user "Alice" tries to unassign the role of user "Alice" using the Graph API
Then the HTTP status code should be "403"
And user "Alice" should have the role "Admin" assigned
Scenario: non-admin user tries to unassign role of another user
Given user "Brian" has been created with default attributes and without skeleton files
When user "Alice" tries to unassign the role of user "Brian" using the Graph API
Then the HTTP status code should be "403"
And user "Brian" should have the role "User" assigned
Scenario: non-admin user tries to unassign role of nonexistent user
When user "Alice" tries to unassign the role of user "nonexistent" using the Graph API
Then the HTTP status code should be "403"