mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-04-23 20:49:13 -05:00
Code Issues Packages Projects Releases Wiki Activity

using Graph instead Of Setting Method In Tests

Browse Source
This commit is contained in:
Viktor Scharf
2023-06-15 15:56:48 +02:00
parent 3cdc3bc485
commit 5867dae18f
44 changed files with 170 additions and 170 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiGraph/addUserToGroup.feature
+17 -17
View File
@@ -121,7 +121,7 @@ Feature: add users to group
@issue-5938
Scenario Outline: user other than the admin tries to add herself to a group
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
And group "groupA" has been created
When user "Alice" tries to add herself to group "groupA" using the Graph API
Then the HTTP status code should be "403"
@@ -155,7 +155,7 @@ Feature: add users to group
@issue-5938
Scenario Outline: user other than the admin tries to add other user to a group
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "groupA" has been created
When user "Alice" tries to add user "Brian" to group "groupA" using the Graph API
Then the HTTP status code should be "403"
@@ -194,7 +194,7 @@ Feature: add users to group
@issue-5939
Scenario Outline: user other than the admin tries to add user to a nonexistent group
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Alice" using the Graph API
When the user "Alice" tries to add user "Brian" to a nonexistent group using the Graph API
Then the HTTP status code should be "404"
Examples:
@@ -216,7 +216,7 @@ Feature: add users to group
Scenario: add multiple users to a group at once
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -234,7 +234,7 @@ Feature: add users to group
Scenario: admin tries to add users to a nonexistent group at once
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -247,7 +247,7 @@ Feature: add users to group
Scenario: admin tries to add multiple nonexistent users to a group at once
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And user "Alice" has created a group "grp1" using the Graph API
When the administrator "Alice" tries to add the following nonexistent users to a group "grp1" at once using the Graph API
| username |
@@ -257,7 +257,7 @@ Feature: add users to group
Scenario: admin tries to add nonexistent and existing users to a group at once
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -284,7 +284,7 @@ Feature: add users to group
@issue-5702
Scenario: try to add users to a group twice
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -306,7 +306,7 @@ Feature: add users to group
@issue-5793
Scenario: try to add a group to another group with PATCH request
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -320,7 +320,7 @@ Feature: add users to group
@issue-5793
Scenario: try to add a group to another group with POST request
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -334,7 +334,7 @@ Feature: add users to group
Scenario Outline: admin tries to add a user to a group with invalid JSON
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -349,7 +349,7 @@ Feature: add users to group
Scenario Outline: admin tries to add multiple users to a group at once with invalid JSON
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -368,7 +368,7 @@ Feature: add users to group
@issue-5871
Scenario: admin tries to add multiple users with wrong host
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -382,7 +382,7 @@ Feature: add users to group
@issue-5871
Scenario: admin tries to add single user with wrong host
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
@@ -392,7 +392,7 @@ Feature: add users to group
Scenario Outline: try to add invalid user id to a group
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And user "Alice" has created a group "grp1" using the Graph API
When the administrator "Alice" tries to add an invalid user id "<invalid-uuidv4>" to a group "grp1" using the Graph API
Then the HTTP status code should be "404"
@@ -404,7 +404,7 @@ Feature: add users to group
Scenario Outline: try to add invalid user ids to a group at once
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And user "Alice" has created a group "grp1" using the Graph API
When the administrator "Alice" tries to add the following invalid user ids to a group "grp1" at once using the Graph API
| user-id |
@@ -419,7 +419,7 @@ Feature: add users to group
@issue-5855
Scenario: add same user twice to a group at once
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
| username |
| Brian |
tests/acceptance/features/apiGraph/assignRole.feature
+1 -1
View File
@@ -35,7 +35,7 @@ Feature: assign role
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 "<userRole>" using the settings api
And the administrator has assigned the role "<userRole>" 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 "<userRole>"
tests/acceptance/features/apiGraph/createGroup.feature
+2 -2
View File
@@ -6,7 +6,7 @@ Feature: create group
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
Scenario Outline: admin user creates a group
@@ -34,7 +34,7 @@ Feature: create group
@issue-5938
Scenario Outline: user other than the admin can't create a group
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<userRole>" using the settings api
And the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
When user "Brian" tries to create a group "mygroup" using the Graph API
Then the HTTP status code should be "403"
And group "mygroup" should not exist
tests/acceptance/features/apiGraph/createUser.feature
+5 -5
View File
@@ -12,7 +12,7 @@ Feature: create user
@issue-3516
Scenario Outline: admin creates a user
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When the user "Alice" creates a new user using GraphAPI with the following settings:
| userName | <userName> |
| displayName | <displayName> |
@@ -42,7 +42,7 @@ Feature: create user
Scenario: user cannot be created with empty name
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When the user "Alice" creates a new user using GraphAPI with the following settings:
| userName | |
| displayName | emptyName |
@@ -53,7 +53,7 @@ Feature: create user
Scenario Outline: user without admin right cannot create a user
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
When the user "Alice" creates a new user using GraphAPI with the following settings:
| userName | user |
| displayName | user |
@@ -71,7 +71,7 @@ Feature: create user
Scenario: user cannot be created with the name of the disabled user
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the user "Alice" has disabled user "Brian" using the Graph API
When the user "Alice" creates a new user using GraphAPI with the following settings:
| userName | Brian |
@@ -84,7 +84,7 @@ Feature: create user
@skipOnStable2.0
Scenario: user can be created with the name of the deleted user
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the user "Alice" has deleted a user "Brian" using the Graph API
When the user "Alice" creates a new user using GraphAPI with the following settings:
| userName | Brian |
tests/acceptance/features/apiGraph/deleteGroup.feature
+2 -2
View File
@@ -6,7 +6,7 @@ Feature: delete groups
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
Scenario Outline: admin user deletes a group
@@ -53,7 +53,7 @@ Feature: delete groups
@issue-5938
Scenario Outline: user other than the admin can't delete a group
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "new-group" has been created
When user "Brian" tries to delete group "new-group" using the Graph API
Then the HTTP status code should be "403"
tests/acceptance/features/apiGraph/deleteUser.feature
+14 -14
View File
@@ -12,7 +12,7 @@ Feature: delete user
Scenario Outline: admin user deletes a user
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the user "Alice" has created a new user using the Graph API with the following settings:
| userName | <userName> |
| displayName | <displayName> |
@@ -30,7 +30,7 @@ Feature: delete user
Scenario: delete a user and specify the user name in different case
Given user "brand-new-user" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When the user "Alice" deletes a user "Brand-New-User" using the Graph API
Then the HTTP status code should be "204"
And user "brand-new-user" should not exist
@@ -38,8 +38,8 @@ Feature: delete user
Scenario Outline: admin user deletes another user with different role
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
When the user "Alice" deletes a user "Brian" using the Graph API
Then the HTTP status code should be "204"
And user "Brian" should not exist
@@ -52,14 +52,14 @@ Feature: delete user
Scenario: admin user tries to delete his/her own account
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When the user "Alice" deletes a user "Alice" using the Graph API
Then the HTTP status code should be "403"
And user "Alice" should exist
Scenario Outline: non-admin user tries to delete his/her own account
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
When the user "Alice" deletes a user "Alice" using the Graph API
Then the HTTP status code should be "401"
And user "Alice" should exist
@@ -71,13 +71,13 @@ Feature: delete user
Scenario: admin user tries to delete a nonexistent user
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When the user "Alice" tries to delete a nonexistent user using the Graph API
Then the HTTP status code should be "404"
Scenario Outline: non-admin user tries to delete a nonexistent user
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
When the user "Alice" tries to delete a nonexistent user using the Graph API
Then the HTTP status code should be "401"
Examples:
@@ -89,8 +89,8 @@ Feature: delete user
Scenario Outline: non-admin user tries to delete another user with different role
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has given "Alice" the role "<userRole>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
When the user "Alice" deletes a user "Brian" using the Graph API
Then the HTTP status code should be "401"
And user "Brian" should exist
@@ -111,7 +111,7 @@ Feature: delete user
Scenario: admin user deletes a disabled user
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And user "Brian" has been created with default attributes and without skeleton files
And the user "Alice" has disabled user "Brian" using the Graph API
When the user "Alice" deletes a user "Brian" using the Graph API
@@ -120,11 +120,11 @@ Feature: delete user
Scenario Outline: normal user tries to delete a disabled user
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And user "Brian" has been created with default attributes and without skeleton files
And user "Carol" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has given "Carol" the role "<userRole>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<userRole>" to user "Carol" using the Graph API
And the user "Alice" has disabled user "Brian" using the Graph API
When the user "Carol" deletes a user "Brian" using the Graph API
Then the HTTP status code should be "401"
tests/acceptance/features/apiGraph/editGroup.feature
+2 -2
View File
@@ -6,7 +6,7 @@ Feature: edit group name
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
@issue-5977
Scenario Outline: admin user renames a group
@@ -26,7 +26,7 @@ Feature: edit group name
@issue-5938
Scenario Outline: user other than the admin can't rename a group
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
And group "grp1" has been created
When user "Alice" tries to rename group "grp1" to "grp101" using the Graph API
Then the HTTP status code should be "403"
tests/acceptance/features/apiGraph/editUser.feature
+11 -11
View File
@@ -9,7 +9,7 @@ Feature: edit user
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the user "Alice" has created a new user using the Graph API with the following settings:
| userName | Brian |
| displayName | Brian Murphy |
@@ -124,7 +124,7 @@ Feature: edit user
Scenario Outline: normal user should not be able to change their email address
Given the administrator has given "Brian" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Brian" using the Graph API
When the user "Brian" tries to change the email of user "Brian" to "newemail@example.com" using the Graph API
Then the HTTP status code should be "401"
And the user information of "Brian" should match this JSON schema
@@ -150,13 +150,13 @@ Feature: edit user
Scenario Outline: normal user should not be able to edit another user's email
Given the administrator has given "Brian" the role "<userRole>" using the settings api
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
And the user "Alice" has created a new user using the Graph API with the following settings:
| userName | Carol |
| displayName | Carol King |
| email | carol@example.com |
| password | 1234 |
And the administrator has given "Carol" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Carol" using the Graph API
When the user "Brian" tries to change the email of user "Carol" to "newemail@example.com" using the Graph API
Then the HTTP status code should be "401"
And the user information of "Carol" should match this JSON schema
@@ -217,7 +217,7 @@ Feature: edit user
Scenario Outline: normal user should not be able to change his/her own display name
Given the administrator has given "Brian" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Brian" using the Graph API
When the user "Brian" tries to change the display name of user "Brian" to "Brian Murphy" using the Graph API
Then the HTTP status code should be "401"
And the user information of "Alice" should match this JSON schema
@@ -243,13 +243,13 @@ Feature: edit user
Scenario Outline: normal user should not be able to edit another user's display name
Given the administrator has given "Brian" the role "<userRole>" using the settings api
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
And the user "Alice" has created a new user using the Graph API with the following settings:
| userName | Carol |
| displayName | Carol King |
| email | carol@example.com |
| password | 1234 |
And the administrator has given "Carol" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Carol" using the Graph API
When the user "Brian" tries to change the display name of user "Carol" to "Alice Hansen" using the Graph API
Then the HTTP status code should be "401"
And the user information of "Carol" should match this JSON schema
@@ -291,13 +291,13 @@ Feature: edit user
Scenario Outline: normal user should not be able to reset the password of another user
Given the administrator has given "Brian" the role "<userRole>" using the settings api
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
And the user "Alice" has created a new user using the Graph API with the following settings:
| userName | Carol |
| displayName | Carol King |
| email | carol@example.com |
| password | 1234 |
And the administrator has given "Carol" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Carol" using the Graph API
And user "Carol" has uploaded file with content "test file for reset password" to "/resetpassword.txt"
When the user "Brian" resets the password of user "Carol" to "newpassword" using the Graph API
Then the HTTP status code should be "401"
@@ -363,7 +363,7 @@ Feature: edit user
@skipOnStable2.0
Scenario Outline: normal user should not be able to disable another user
Given user "Carol" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
When the user "Brian" tries to disable user "Carol" using the Graph API
Then the HTTP status code should be "401"
When user "Alice" gets information of user "Carol" using Graph API
@@ -456,7 +456,7 @@ Feature: edit user
Scenario Outline: normal user should not be able to enable another user
Given user "Carol" has been created with default attributes and without skeleton files
And the user "Alice" has disabled user "Carol" using the Graph API
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
When the user "Brian" tries to enable user "Carol" using the Graph API
Then the HTTP status code should be "401"
When user "Alice" gets information of user "Carol" using Graph API
tests/acceptance/features/apiGraph/getApplications.feature
+1 -1
View File
@@ -9,7 +9,7 @@ Feature: get applications
Scenario Outline: admin user lists all the groups
Given the administrator has given "Alice" the role "<role>" using the settings api
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
When user "Alice" gets all applications using the Graph API
Then the HTTP status code should be "200"
And the user API response should contain the following application information:
tests/acceptance/features/apiGraph/getGroup.feature
+6 -6
View File
@@ -6,9 +6,9 @@ Feature: get groups and their members
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
Scenario: admin user lists all the groups
Given group "tea-lover" has been created
And group "coffee-lover" has been created
@@ -23,7 +23,7 @@ Feature: get groups and their members
@issue-5938
Scenario Outline: user other than the admin shouldn't get the groups list
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "tea-lover" has been created
And group "coffee-lover" has been created
And group "h2o-lover" has been created
@@ -74,7 +74,7 @@ Feature: get groups and their members
@issue-5938
Scenario Outline: user other than the admin shouldn't get users of a group
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "tea-lover" has been created
When user "Brian" gets all the members of group "tea-lover" using the Graph API
Then the HTTP status code should be "403"
@@ -235,7 +235,7 @@ Feature: get groups and their members
@issue-5938
Scenario Outline: user other than the admin shouldn't get all groups along with its member's information
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "tea-lover" has been created
And group "coffee-lover" has been created
And user "Alice" has been added to group "tea-lover"
@@ -350,7 +350,7 @@ Feature: get groups and their members
@issue-5604
Scenario Outline: user other than the admin gets a group along with its member's information
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "tea-lover" has been created
And user "Alice" has been added to group "tea-lover"
And user "Brian" has been added to group "tea-lover"
tests/acceptance/features/apiGraph/getUser.feature
+19 -19
View File
@@ -12,7 +12,7 @@ Feature: get users
@skipOnStable2.0
Scenario: admin user gets the information of a user
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When user "Alice" gets information of user "Brian" using Graph API
Then the HTTP status code should be "200"
And the JSON data of the response should match
@@ -53,8 +53,8 @@ Feature: get users
@issue-5125
Scenario Outline: non-admin user tries to get the information of a user
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
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
And the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
When user "Brian" tries to get information of user "Alice" using Graph API
Then the HTTP status code should be "401"
And the JSON data of the response should match
@@ -95,7 +95,7 @@ Feature: get users
@skipOnStable2.0
Scenario: admin user gets all users
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When user "Alice" gets all users using the Graph API
Then the HTTP status code should be "200"
And the JSON data of the response should contain the user "Alice Hansen" in the item 'value', the user-details should match
@@ -161,7 +161,7 @@ Feature: get users
@skipOnStable2.0
Scenario: admin user gets all users include disabled users
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the user "Alice" has disabled user "Brian" using the Graph API
When user "Alice" gets all users using the Graph API
Then the HTTP status code should be "200"
@@ -228,7 +228,7 @@ Feature: get users
Scenario Outline: non-admin user tries to get all users
Given the administrator has given "Alice" the role "<userRole>" using the settings api
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
When user "Brian" tries to get all users using the Graph API
Then the HTTP status code should be "401"
And the JSON data of the response should match
@@ -260,7 +260,7 @@ Feature: get users
@skipOnStable2.0
Scenario: admin user gets the drive information of a user
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When the user "Alice" gets user "Brian" along with his drive information using Graph API
Then the HTTP status code should be "200"
And the JSON data of the response should match
@@ -383,7 +383,7 @@ Feature: get users
@skipOnStable2.0
Scenario Outline: non-admin user gets his/her own drive information
Given the administrator has given "Brian" the role "<userRole>" using the settings api
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
When the user "Brian" gets his drive information using Graph API
Then the HTTP status code should be "200"
And the JSON data of the response should match
@@ -511,7 +511,7 @@ Feature: get users
@skipOnStable2.0
Scenario: admin user gets the group information of a user
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And group "tea-lover" has been created
And group "coffee-lover" has been created
And user "Brian" has been added to group "tea-lover"
@@ -575,8 +575,8 @@ Feature: get users
@issue-5125
Scenario Outline: non-admin user tries to get the group information of a user
Given the administrator has given "Alice" the role "<userRole>" using the settings api
And the administrator has given "Brian" the role "<role>" using the settings api
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "coffee-lover" has been created
And user "Brian" has been added to group "coffee-lover"
When the user "Alice" gets user "Brian" along with his group information using Graph API
@@ -619,7 +619,7 @@ Feature: get users
@skipOnStable2.0
Scenario: admin user gets all users of certain groups
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And user "Carol" has been created with default attributes and without skeleton files
And the user "Alice" has disabled user "Carol" using the Graph API
And group "tea-lover" has been created
@@ -753,7 +753,7 @@ Feature: get users
@skipOnStable2.0
Scenario: admin user gets all users of two groups
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And user "Carol" has been created with default attributes and without skeleton files
And group "tea-lover" has been created
And group "coffee-lover" has been created
@@ -827,8 +827,8 @@ Feature: get users
@skipOnStable2.0
Scenario Outline: non admin user tries to get users of certain groups
Given the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has given "Brian" the role "<role>" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "tea-lover" has been created
And user "Alice" has been added to group "tea-lover"
When the user "Brian" gets all users of the group "tea-lover" using the Graph API
@@ -862,10 +862,10 @@ Feature: get users
@skipOnStable2.0
Scenario: admin user gets all users with certain roles and members of a certain group
Given the administrator has given "Alice" the role "Admin" using the settings api
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And user "Carol" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "Space Admin" using the settings api
And the administrator has given "Carol" the role "Space Admin" using the settings api
And the administrator has assigned the role "Space Admin" to user "Brian" using the Graph API
And the administrator has assigned the role "Space Admin" to user "Carol" using the Graph API
And group "tea-lover" has been created
And user "Brian" has been added to group "tea-lover"
When the user "Alice" gets all users with role "Space Admin" using the Graph API
@@ -967,7 +967,7 @@ Feature: get users
@skipOnStable2.0
Scenario Outline: non-admin user tries to get users with a certain role
Given the administrator has given "Alice" the role "<userRole>" using the settings api
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
When the user "Alice" gets all users with role "<role>" using the Graph API
Then the HTTP status code should be "401"
And the JSON data of the response should match
tests/acceptance/features/apiGraph/removeUserFromGroup.feature
+1 -1
View File
@@ -159,7 +159,7 @@ Feature: remove a user from a group
@issue-5938
Scenario Outline: user other than the admin can't remove a user from their group
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And group "grp1" has been created
And user "Alice" has been added to group "grp1"
And user "Brian" has been added to group "grp1"
tests/acceptance/features/apiGraph/userGDPRExport.feature
+2 -2
View File
@@ -496,8 +496,8 @@ Feature: user GDPR (General Data Protection Regulation) report
Scenario Outline: user tries to generate GDPR report of other users
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "<userRole>" using the settings api
And the administrator has given "Brian" the role "<role>" using the settings api
And the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
When user "Alice" tries to export GDPR report of user "Brian" to "/.personal_data_export.json" using Graph API
Then the HTTP status code should be "400"
Examples: