mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-05-14 03:04:16 -04:00
Code Issues Packages Projects Releases Wiki Activity

Used kebab case for example table header name (#8686)

Browse Source
This commit is contained in:
Prarup Gurung
2024-03-19 13:00:42 +05:45
committed by GitHub
parent 4305fce074
commit 6fb55b5599
12 changed files with 206 additions and 206 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
tests/acceptance/features/apiGraphUserGroup/addUserToGroup.feature
View File

@@ -12,18 +12,18 @@ Feature: add users to group
| groupname | comment |
| simplegroup | nothing special here |
| España§àôœ€ | special European and other characters |
| नेपाली | Unicode group name |
| नेपाली | Unicode group name |
When the administrator adds the following users to the following groups using the Graph API
| username | groupname |
| Alice | simplegroup |
| Alice | España§àôœ€ |
| Alice | नेपाली |
| Alice | नेपाली |
Then the HTTP status code of responses on all endpoints should be "204"
And the following users should be listed in the following groups
| username | groupname |
| Alice | simplegroup |
| Alice | España§àôœ€ |
| Alice | नेपाली |
| Alice | नेपाली |
Scenario: adding a user to a group with special character in its name
@@ -120,7 +120,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 assigned the role "<role>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-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"
@@ -148,7 +148,7 @@ Feature: add users to group
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -156,7 +156,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 assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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"
@@ -184,7 +184,7 @@ Feature: add users to group
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -197,11 +197,11 @@ 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 assigned the role "<role>" to user "Alice" using the Graph API
And the administrator has assigned the role "<user-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:
| role |
| user-role |
| Space Admin |
| User |
| User Light |

22
tests/acceptance/features/apiGraphUserGroup/changeOwnPassword.feature
View File

@@ -5,15 +5,15 @@ Feature: an user changes its own password
Scenario Outline: change own password
Given user "Alice" has been created with default attributes and without skeleton files
When the user "Alice" changes its own password "<currentPassword>" to "<newPassword>" using the Graph API
Then the HTTP status code should be "<code>"
When the user "Alice" changes its own password "<current-password>" to "<new-password>" using the Graph API
Then the HTTP status code should be "<http-status-code>"
Examples:
| currentPassword | newPassword | code |
| 123456 | validPass | 204 |
| 123456 | кириллица | 204 |
| 123456 | 密码 | 204 |
| 123456 | ?&^%0 | 204 |
| 123456 | | 400 |
| 123456 | 123456 | 400 |
| wrongPass | 123456 | 400 |
| | validPass | 400 |
| current-password | new-password | http-status-code |
| 123456 | validPass | 204 |
| 123456 | кириллица | 204 |
| 123456 | 密码 | 204 |
| 123456 | ?&^%0 | 204 |
| 123456 | | 400 |
| 123456 | 123456 | 400 |
| wrongPass | 123456 | 400 |
| | validPass | 400 |

26
tests/acceptance/features/apiGraphUserGroup/createGroup.feature
View File

@@ -9,19 +9,19 @@ Feature: create group
Scenario Outline: admin user creates a group
When user "Alice" creates a group "<groupname>" using the Graph API
When user "Alice" creates a group "<group>" using the Graph API
Then the HTTP status code should be "201"
And group "<groupname>" should exist
And group "<group>" should exist
Examples:
| groupname |
| simplegroup |
| España§àôœ€ |
| नेपाली |
| $x<=>[y*z^2+1]! |
| 😅 😆 |
| comma,grp1 |
| Finance (NP) |
| slash\Middle |
| group |
| simplegroup |
| España§àôœ€ |
| नेपाली |
| $x<=>[y*z^2+1]! |
| 😅 😆 |
| comma,grp1 |
| Finance (NP) |
| slash\Middle |
@issue-3516
Scenario: admin user tries to create a group that already exists
@@ -33,12 +33,12 @@ 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 assigned the role "<userRole>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-role>" 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
Examples:
| userRole |
| user-role |
| Space Admin |
| User |
| User Light |

16
tests/acceptance/features/apiGraphUserGroup/createGroupCaseSensitive.feature
View File

@@ -5,17 +5,17 @@ Feature: create groups, group names are case insensitive
@issue-3516
Scenario Outline: group names are case insensitive, creating groups with different upper and lower case names
Given using OCS API version "<ocs_api_version>"
And group "<group_id1>" has been created
When the administrator creates a group "<group_id2>" using the Graph API
And the administrator creates a group "<group_id3>" using the Graph API
Given using OCS API version "<ocs-api-version>"
And group "<group>" has been created
When the administrator creates a group "<group-2>" using the Graph API
And the administrator creates a group "<group-3>" using the Graph API
Then the HTTP status code of responses on all endpoints should be "409"
And these groups should not exist:
| groupname |
| <group_id2> |
| <group_id3> |
| groupname |
| <group-2> |
| <group-3> |
Examples:
| ocs_api_version | group_id1 | group_id2 | group_id3 |
| ocs-api-version | group | group-2 | group-3 |
| 1 | case-sensitive-group | Case-Sensitive-Group | CASE-SENSITIVE-GROUP |
| 1 | Case-Sensitive-Group | CASE-SENSITIVE-GROUP | case-sensitive-group |
| 1 | CASE-SENSITIVE-GROUP | case-sensitive-group | Case-Sensitive-Group |

52
tests/acceptance/features/apiGraphUserGroup/createUser.feature
View File

@@ -13,28 +13,28 @@ Feature: create user
Scenario Outline: admin creates a user
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When the user "Alice" creates a new user with the following attributes using the Graph API:
| userName | <userName> |
| displayName | <displayName> |
| email | <email> |
| password | <password> |
| accountEnabled | <enable> |
Then the HTTP status code should be "<code>"
And user "<userName>" <shouldOrNot> exist
| userName | <user> |
| displayName | <display-name> |
| email | <email> |
| password | <password> |
| accountEnabled | <enable> |
Then the HTTP status code should be "<http-status-code>"
And user "<user>" <should-or-not> exist
Examples:
| userName | displayName | email | password | code | enable | shouldOrNot |
| SameDisplayName | Alice Hansen | new@example.org | containsCharacters(*:!;_+-&) | 201 | true | should |
| withoutPassSameEmail | without pass | alice@example.org | | 201 | true | should |
| name | pass with space | example@example.org | my pass | 201 | true | should |
| user1 | user names must not start with a number | example@example.org | my pass | 201 | true | should |
| nameWithCharacters(*:!;_+-&) | user | new@example.org | 123 | 400 | true | should not |
| name with space | name with space | example@example.org | 123 | 400 | true | should not |
| createDisabledUser | disabled user | example@example.org | 123 | 201 | false | should |
| nameWithNumbers0123456 | user | name0123456@example.org | 123 | 201 | true | should |
| name.with.dots | user | name.w.dots@example.org | 123 | 201 | true | should |
| 123456789 | user | 123456789@example.org | 123 | 400 | true | should not |
| 0.0 | user | float@example.org | 123 | 400 | true | should not |
| withoutEmail | without email | | 123 | 201 | true | should |
| Alice | same userName | new@example.org | 123 | 409 | true | should |
| user | display-name | email | password | http-status-code | enable | should-or-not |
| SameDisplayName | Alice Hansen | new@example.org | containsCharacters(*:!;_+-&) | 201 | true | should |
| withoutPassSameEmail | without pass | alice@example.org | | 201 | true | should |
| name | pass with space | example@example.org | my pass | 201 | true | should |
| user1 | user names must not start with a number | example@example.org | my pass | 201 | true | should |
| nameWithCharacters(*:!;_+-&) | user | new@example.org | 123 | 400 | true | should not |
| name with space | name with space | example@example.org | 123 | 400 | true | should not |
| createDisabledUser | disabled user | example@example.org | 123 | 201 | false | should |
| nameWithNumbers0123456 | user | name0123456@example.org | 123 | 201 | true | should |
| name.with.dots | user | name.w.dots@example.org | 123 | 201 | true | should |
| 123456789 | user | 123456789@example.org | 123 | 400 | true | should not |
| 0.0 | user | float@example.org | 123 | 400 | true | should not |
| withoutEmail | without email | | 123 | 201 | true | should |
| Alice | same userName | new@example.org | 123 | 409 | true | should |
Scenario: user cannot be created with empty name
@@ -49,7 +49,7 @@ Feature: create user
Scenario Outline: user without admin right cannot create a user
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
When the user "Alice" creates a new user with the following attributes using the Graph API:
| userName | user |
| displayName | user |
@@ -59,7 +59,7 @@ Feature: create user
Then the HTTP status code should be "401"
And user "user" should not exist
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -97,15 +97,15 @@ Feature: create user
Given the config "GRAPH_USERNAME_MATCH" has been set to "none"
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
When the user "Alice" creates a new user with the following attributes using the Graph API:
| userName | <userName> |
| userName | <user> |
| displayName | test user |
| email | new@example.org |
| password | 123 |
| accountEnabled | true |
Then the HTTP status code should be "201"
And user "<userName>" should exist
And user "<user>" should exist
Examples:
| userName | description |
| user | description |
| 1248Bob | user names starts with the number |
| (*:!;+-&$%)_alice | user names starts with the ASCII characters |

28
tests/acceptance/features/apiGraphUserGroup/deleteGroup.feature
View File

@@ -9,15 +9,15 @@ Feature: delete groups
Scenario Outline: admin user deletes a group
Given group "<group_id>" has been created
When user "Alice" deletes group "<group_id>" using the Graph API
Given group "<group>" has been created
When user "Alice" deletes group "<group>" using the Graph API
Then the HTTP status code should be "204"
And group "<group_id>" should not exist
And group "<group>" should not exist
Examples:
| group_id | comment |
| group | comment |
| simplegroup | nothing special here |
| España§àôœ€ | special European and other characters |
| नेपाली | Unicode group name |
| नेपाली | Unicode group name |
| brand-new-group | dash |
| the.group | dot |
| left,right | comma |
@@ -39,26 +39,26 @@ Feature: delete groups
@issue-5083
Scenario Outline: admin user deletes a group having % (as only special char) in its name
Given group "<group_id>" has been created
When user "Alice" deletes group "<group_id>" using the Graph API
Given group "<group>" has been created
When user "Alice" deletes group "<group>" using the Graph API
Then the HTTP status code should be "204"
And group "<group_id>" should not exist
And group "<group>" should not exist
Examples:
| group_id | comment |
| 50%pass | Percent sign (special escaping happens) |
| 50%2Eagle | %2E literal looks like an escaped "." |
| 50%2Fix | %2F literal looks like an escaped slash |
| group | comment |
| 50%pass | Percent sign (special escaping happens) |
| 50%2Eagle | %2E literal looks like an escaped "." |
| 50%2Fix | %2F literal looks like an escaped slash |
@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 assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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"
And group "new-group" should exist
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |

38
tests/acceptance/features/apiGraphUserGroup/deleteUser.feature
View File

@@ -13,15 +13,15 @@ Feature: delete user
Scenario Outline: admin user deletes a user
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the user "Alice" has created a new user with the following attributes:
| userName | <userName> |
| displayName | <displayName> |
| email | <email> |
| password | <password> |
When the user "Alice" deletes a user "<userName>" using the Graph API
| userName | <user-name> |
| displayName | <display-name> |
| email | <email> |
| password | <password> |
When the user "Alice" deletes a user "<user-name>" using the Graph API
Then the HTTP status code should be "204"
And user "<userName>" should not exist
And user "<user-name>" should not exist
Examples:
| userName | displayName | email | password |
| user-name | display-name | email | password |
| SameDisplayName | Alice Hansen | new@example.org | containsCharacters(*:!;_+-&) |
| withoutPassSameEmail | without pass | alice@example.org | |
| name | pass with space | example@example.org | my pass |
@@ -38,12 +38,12 @@ 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 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 the administrator has assigned the role "<user-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
Examples:
| role |
| user-role |
| Admin |
| Space Admin |
| User |
@@ -58,12 +58,12 @@ Feature: delete user
Scenario Outline: non-admin user tries to delete his/her own account
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-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
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -76,11 +76,11 @@ Feature: delete user
Scenario Outline: non-admin user tries to delete a nonexistent user
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-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:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -88,13 +88,13 @@ 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 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
And the administrator has assigned the role "<user-role-2>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-role>" 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
Examples:
| userRole | role |
| user-role | user-role-2 |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | User Light |
@@ -122,14 +122,14 @@ Feature: delete user
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 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 administrator has assigned the role "<user-role-2>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-role>" to user "Carol" using the Graph API
And the user "Alice" has disabled user "Brian"
When the user "Carol" deletes a user "Brian" using the Graph API
Then the HTTP status code should be "401"
And user "Brian" should exist
Examples:
| userRole | role |
| user-role | user-role-2 |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | User Light |

26
tests/acceptance/features/apiGraphUserGroup/editGroup.feature
View File

@@ -9,28 +9,28 @@ Feature: edit group name
@issue-5977
Scenario Outline: admin user renames a group
Given group "<old_group>" has been created
When user "Alice" renames group "<old_group>" to "<new_group>" using the Graph API
Given group "<group>" has been created
When user "Alice" renames group "<group>" to "<new-group>" using the Graph API
Then the HTTP status code should be "204"
And group "<old_group>" should not exist
And group "<new_group>" should exist
And group "<group>" should not exist
And group "<new-group>" should exist
Examples:
| old_group | new_group |
| grp1 | grp101 |
| grp1 | España§àôœ€ |
| grp1 | नेपाली |
| grp1 | $x<=>[y*z^2]! |
| grp1 | staff?group |
| grp1 | 50%pass |
| group | new-group |
| grp1 | grp101 |
| grp1 | España§àôœ€ |
| grp1 | नेपाली |
| grp1 | $x<=>[y*z^2]! |
| grp1 | staff?group |
| grp1 | 50%pass |
@issue-5938
Scenario Outline: user other than the admin can't rename a group
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-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"
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |

84
tests/acceptance/features/apiGraphUserGroup/editUser.feature
View File

@@ -17,8 +17,8 @@ Feature: edit user
Scenario Outline: admin user can edit another user's email
When the user "Alice" changes the email of user "Brian" to "<newEmail>" using the Graph API
Then the HTTP status code should be "<code>"
When the user "Alice" changes the email of user "Brian" to "<new-email>" using the Graph API
Then the HTTP status code should be "<http-status-code>"
And the user information of "Brian" should match this JSON schema
"""
{
@@ -29,25 +29,25 @@ Feature: edit user
"properties": {
"mail": {
"type": "string",
"enum": ["<emailAsResult>"]
"enum": ["<expected-email>"]
}
}
}
"""
Examples:
| action description | newEmail | code | emailAsResult |
| change to a valid email | newemail@example.com | 200 | newemail@example.com |
| override existing mail | brian@example.com | 200 | brian@example.com |
| two users with same mail | alice@example.org | 200 | alice@example.org |
| empty mail | | 400 | brian@example.com |
| change to a invalid email | invalidEmail | 400 | brian@example.com |
| action description | new-email | http-status-code | expected-email |
| change to a valid email | newemail@example.com | 200 | newemail@example.com |
| override existing mail | brian@example.com | 200 | brian@example.com |
| two users with same mail | alice@example.org | 200 | alice@example.org |
| empty mail | | 400 | brian@example.com |
| change to a invalid email | invalidEmail | 400 | brian@example.com |
@issue-7044
Scenario Outline: admin user can edit another user's name
Given user "Carol" has been created with default attributes and without skeleton files
When the user "Alice" changes the user name of user "Carol" to "<userName>" using the Graph API
Then the HTTP status code should be "<code>"
And the user information of "<newUserName>" should match this JSON schema
When the user "Alice" changes the user name of user "Carol" to "<user>" using the Graph API
Then the HTTP status code should be "<http-status-code>"
And the user information of "<new-user>" should match this JSON schema
"""
{
"type": "object",
@@ -56,17 +56,17 @@ Feature: edit user
],
"properties": {
"onPremisesSamAccountName": {
"enum": ["<newUserName>"]
"enum": ["<new-user>"]
}
}
}
"""
Examples:
| action description | userName | code | newUserName |
| change to a valid user name | Lionel | 200 | Lionel |
| user name characters | a*!_+-& | 200 | a*!_+-& |
| change to existing user name | Brian | 409 | Brian |
| empty user name | | 400 | Brian |
| action description | user | http-status-code | new-user |
| change to a valid user name | Lionel | 200 | Lionel |
| user name characters | a*!_+-& | 200 | a*!_+-& |
| change to existing user name | Brian | 409 | Carol |
| empty user name | | 400 | Carol |
Scenario: admin user changes the name of a user to the name of an existing disabled user
@@ -122,7 +122,7 @@ Feature: edit user
Scenario Outline: normal user should not be able to change their email address
Given the administrator has assigned the role "<role>" to user "Brian" using the Graph API
Given the administrator has assigned the role "<user-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
@@ -141,20 +141,20 @@ Feature: edit user
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
Scenario Outline: normal user should not be able to edit another user's email
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
Given the administrator has assigned the role "<user-role>" to user "Brian" using the Graph API
And the user "Alice" has created a new user with the following attributes:
| userName | Carol |
| displayName | Carol King |
| email | carol@example.com |
| password | 1234 |
And the administrator has assigned the role "<role>" to user "Carol" using the Graph API
And the administrator has assigned the role "<user-role-2>" 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
@@ -173,7 +173,7 @@ Feature: edit user
}
"""
Examples:
| userRole | role |
| user-role | user-role-2 |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | User Light |
@@ -189,7 +189,7 @@ Feature: edit user
Scenario Outline: admin user can edit another user display name
When the user "Alice" changes the display name of user "Brian" to "<newDisplayName>" using the Graph API
When the user "Alice" changes the display name of user "Brian" to "<new-display-name>" using the Graph API
Then the HTTP status code should be "200"
And the user information of "Brian" should match this JSON schema
"""
@@ -201,21 +201,21 @@ Feature: edit user
"properties": {
"displayName": {
"type": "string",
"enum": ["<displayNameAsResult>"]
"enum": ["<expected-display-name>"]
}
}
}
"""
Examples:
| action description | newDisplayName | displayNameAsResult |
| change to a display name | Olaf Scholz | Olaf Scholz |
| override to existing display name | Carol King | Carol King |
| change to an empty display name | | Brian Murphy |
| displayName with characters | *:!;_+-&#(?) | *:!;_+-&#(?) |
| action description | new-display-name | expected-display-name |
| change to a display name | Olaf Scholz | Olaf Scholz |
| override to existing display name | Carol King | Carol King |
| change to an empty display name | | Brian Murphy |
| displayName with characters | *:!;_+-&#(?) | *:!;_+-&#(?) |
Scenario Outline: normal user should not be able to change his/her own display name
Given the administrator has assigned the role "<role>" to user "Brian" using the Graph API
Given the administrator has assigned the role "<user-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
@@ -234,20 +234,20 @@ Feature: edit user
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
Scenario Outline: normal user should not be able to edit another user's display name
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
Given the administrator has assigned the role "<user-role>" to user "Brian" using the Graph API
And the user "Alice" has created a new user with the following attributes:
| userName | Carol |
| displayName | Carol King |
| email | carol@example.com |
| password | 1234 |
And the administrator has assigned the role "<role>" to user "Carol" using the Graph API
And the administrator has assigned the role "<user-role-2>" 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
@@ -266,7 +266,7 @@ Feature: edit user
}
"""
Examples:
| userRole | role |
| user-role | user-role-2 |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | User Light |
@@ -289,20 +289,20 @@ Feature: edit user
Scenario Outline: normal user should not be able to reset the password of another user
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
Given the administrator has assigned the role "<user-role>" to user "Brian" using the Graph API
And the user "Alice" has created a new user with the following attributes:
| userName | Carol |
| displayName | Carol King |
| email | carol@example.com |
| password | 1234 |
And the administrator has assigned the role "<role>" to user "Carol" using the Graph API
And the administrator has assigned the role "<user-role-2>" 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"
And the content of file "resetpassword.txt" for user "Carol" using password "1234" should be "test file for reset password"
But user "Carol" using password "newpassword" should not be able to download file "resetpassword.txt"
Examples:
| userRole | role |
| user-role | user-role-2 |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | User Light |
@@ -361,7 +361,7 @@ Feature: edit user
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 assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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
@@ -402,7 +402,7 @@ Feature: edit user
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -454,7 +454,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"
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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
@@ -495,7 +495,7 @@ Feature: edit user
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |

28
tests/acceptance/features/apiGraphUserGroup/getGroup.feature
View File

@@ -22,7 +22,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 assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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
@@ -52,7 +52,7 @@ Feature: get groups and their members
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -75,7 +75,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 assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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"
@@ -103,7 +103,7 @@ Feature: get groups and their members
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -243,7 +243,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 assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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"
@@ -274,7 +274,7 @@ Feature: get groups and their members
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -365,7 +365,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 assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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"
@@ -395,7 +395,7 @@ Feature: get groups and their members
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -454,9 +454,9 @@ Feature: get groups and their members
Examples:
| group |
| España§àôœ€ |
| नेपाली |
| नेपाली |
| $x<=>[y*z^2+1]! |
| եòɴԪ˯ΗՐΛɔπ |
| եòɴԪ˯ΗՐΛɔπ |
Scenario: admin user tries to get group information of non-existing group
@@ -473,7 +473,7 @@ Feature: get groups and their members
Then the HTTP status code should be "200"
And the JSON data of the response should match
"""
{
{
"type": "object",
"required": [
"value"
@@ -577,6 +577,6 @@ Feature: get groups and their members
}
"""
Examples:
| group | token |
| tea-lovers | -lovers |
| tea@lovers | @lovers |
| group | token |
| tea-lovers | -lovers |
| tea@lovers | @lovers |

62
tests/acceptance/features/apiGraphUserGroup/getUser.feature
View File

@@ -57,8 +57,8 @@ Feature: get users
@issue-5125
Scenario Outline: non-admin user tries to get the information of a user
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
Given the administrator has assigned the role "<user-role-2>" to user "Alice" using the Graph API
And the administrator has assigned the role "<user-role>" 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
@@ -85,7 +85,7 @@ Feature: get users
}
"""
Examples:
| userRole | role |
| user-role | user-role-2 |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | User Light |
@@ -254,7 +254,7 @@ Feature: get users
Scenario Outline: non-admin user tries to get all users
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-role>" 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 "403"
And the JSON data of the response should match
@@ -281,7 +281,7 @@ Feature: get users
}
"""
Examples:
| userRole |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -418,7 +418,7 @@ Feature: get users
Scenario Outline: user gets his/her own information along with drive information
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
Given the administrator has assigned the role "<user-role>" 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
@@ -546,7 +546,7 @@ Feature: get users
}
"""
Examples:
| userRole |
| user-role |
| Admin |
| Space Admin |
| User |
@@ -623,8 +623,8 @@ Feature: get users
@issue-5125
Scenario Outline: non-admin user tries to get the group information of a user
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
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
And the administrator has assigned the role "<user-role-2>" 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
@@ -653,7 +653,7 @@ Feature: get users
}
"""
Examples:
| userRole | role |
| user-role | user-role-2 |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | User Light |
@@ -904,7 +904,7 @@ Feature: get users
Scenario Outline: non admin user tries to get users of certain groups
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 the administrator has assigned the role "<user-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
@@ -933,7 +933,7 @@ Feature: get users
}
"""
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |
@@ -1060,8 +1060,8 @@ Feature: get users
Scenario Outline: non-admin user tries to get users with a certain role
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
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
When the user "Alice" gets all users with role "<user-role-2>" using the Graph API
Then the HTTP status code should be "403"
And the JSON data of the response should match
"""
@@ -1087,7 +1087,7 @@ Feature: get users
}
"""
Examples:
| userRole | role |
| user-role | user-role-2 |
| Space Admin | Space Admin |
| Space Admin | User |
| Space Admin | User Light |
@@ -1103,7 +1103,7 @@ Feature: get users
@issue-6017
Scenario Outline: admin user gets the drive information of a user with different user role
Given the administrator has assigned the role "<user-role-1>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
And the administrator has assigned the role "<user-role-2>" to user "Brian" using the Graph API
And user "Brian" has created folder "my_data"
When user "Alice" gets the personal drive information of user "Brian" using Graph API
@@ -1196,7 +1196,7 @@ Feature: get users
}
"""
Examples:
| user-role-1 | user-role-2 |
| user-role | user-role-2 |
| Admin | Admin |
| Admin | Space Admin |
| Admin | User |
@@ -1208,7 +1208,7 @@ Feature: get users
Scenario Outline: non-admin user tries to get drive information of other user with different user role
Given the administrator has assigned the role "<user-role-1>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
And the administrator has assigned the role "<user-role-2>" to user "Brian" using the Graph API
When user "Alice" gets the personal drive information of user "Brian" using Graph API
Then the HTTP status code should be "404"
@@ -1241,19 +1241,19 @@ Feature: get users
}
"""
Examples:
| user-role-1 | user-role-2 |
| User | Admin |
| User | Space Admin |
| User | User |
| User | User Light |
| User Light | Admin |
| User Light | Space Admin |
| User Light | User |
| User Light | User Light |
| user-role | user-role-2 |
| User | Admin |
| User | Space Admin |
| User | User |
| User | User Light |
| User Light | Admin |
| User Light | Space Admin |
| User Light | User |
| User Light | User Light |
Scenario Outline: user with different user role gets his/her own drive information
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
When user "Alice" gets own personal drive information using Graph API
Then the HTTP status code should be "200"
And the JSON data of the response should match
@@ -1344,7 +1344,7 @@ Feature: get users
}
"""
Examples:
| userRole |
| user-role |
| Admin |
| Space Admin |
| User |
@@ -1447,7 +1447,7 @@ Feature: get users
"properties": {
"message": {
"type": "string",
"enum": ["Token '<errorToken>' is invalid"]
"enum": ["Token '<error-token>' is invalid"]
}
}
}
@@ -1455,7 +1455,7 @@ Feature: get users
}
"""
Examples:
| user | errorToken |
| user | error-token |
| Alice-From-Wonderland | -From-Wonderland |
| Alice@From@Wonderland | @From@Wonderland |

12
tests/acceptance/features/apiGraphUserGroup/removeUserFromGroup.feature
View File

@@ -12,23 +12,23 @@ Feature: remove a user from a group
| groupname | comment |
| brand-new-group | nothing special here |
| España§àôœ€ | special European and other characters |
| नेपाली | Unicode group name |
| नेपाली | Unicode group name |
And the following users have been added to the following groups
| username | groupname |
| Alice | brand-new-group |
| Alice | España§àôœ€ |
| Alice | नेपाली |
| Alice | नेपाली |
When the administrator removes the following users from the following groups using the Graph API
| username | groupname |
| Alice | brand-new-group |
| Alice | España§àôœ€ |
| Alice | नेपाली |
| Alice | नेपाली |
Then the HTTP status code of responses on all endpoints should be "204"
And the following users should not belong to the following groups
| username | groupname |
| Alice | brand-new-group |
| Alice | España§àôœ€ |
| Alice | नेपाली |
| Alice | नेपाली |
Scenario: admin removes a user from a group with special characters
@@ -158,7 +158,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 assigned the role "<role>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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"
@@ -189,7 +189,7 @@ Feature: remove a user from a group
"""
And user "Brian" should belong to group "grp1"
Examples:
| role |
| user-role |
| Space Admin |
| User |
| User Light |