mirror of
https://github.com/opencloud-eu/opencloud.git
synced 2026-01-01 09:52:23 -06:00
ad66bf2d1f
* Added api test for delete user using graph API * Added scenario, admin user tries to delete another admin user * Added scenario, delete user with username having different case * Addressed reviews
74 lines
3.4 KiB
Gherkin
74 lines
3.4 KiB
Gherkin
@api @skipOnOcV10
|
|
Feature: delete user
|
|
Only user with admin permission can delete user
|
|
|
|
Note - this feature is run in CI with ACCOUNTS_HASH_DIFFICULTY set to the default for production
|
|
See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839
|
|
|
|
Background:
|
|
Given user "Alice" has been created with default attributes and without skeleton files
|
|
|
|
|
|
Scenario Outline: the admin user deletes a user
|
|
Given the administrator has given "Alice" the role "Admin" using the settings api
|
|
And the user "Alice" has created a new user using the Graph API with the following settings:
|
|
| userName | <userName> |
|
|
| displayName | <displayName> |
|
|
| email | <email> |
|
|
| password | <password> |
|
|
When the user "Alice" deletes a user "<userName>" using the Graph API
|
|
Then the HTTP status code should be "204"
|
|
And user "<userName>" should not exist
|
|
Examples:
|
|
| userName | displayName | email | password |
|
|
| SameDisplayName | Alice Hansen | new@example.org | containsCharacters(*:!;_+-&) |
|
|
| withoutPassSameEmail | without pass | alice@example.org | |
|
|
| name | pass with space | example@example.org | my pass |
|
|
|
|
|
|
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
|
|
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
|
|
|
|
|
|
Scenario Outline: the 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
|
|
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 |
|
|
| Admin |
|
|
| Space Admin |
|
|
| User |
|
|
|
|
|
|
Scenario: the admin user tries to delete his/her own account
|
|
Given the administrator has given "Alice" the role "Admin" using the settings 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: the admin user tries to delete a non-existent user
|
|
Given the administrator has given "Alice" the role "Admin" using the settings api
|
|
When the user "Alice" deletes a user "nonExistentUser" using the Graph API
|
|
Then the HTTP status code should be "404"
|
|
|
|
|
|
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 "Alice" the role "<role>" using the settings 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:
|
|
| role |
|
|
| Space Admin |
|
|
| User |
|