mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-01-06 12:19:37 -06:00
Code Issues Packages Projects Releases Wiki Activity

removing without skeleton files string from the user creation steps

Browse Source
This commit is contained in:
Niraj Acharya
2024-11-29 09:39:21 +05:45
parent a265fcbe46
commit c98841904d
219 changed files with 663 additions and 804 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -4,7 +4,7 @@ Feature: add users to group
So that I can give a user access to the resources of the group
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
Scenario: adding a user to a group
@@ -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
Given user "Brian" has been created with default attributes
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
@@ -196,7 +196,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
Given user "Brian" has been created with default attributes
And the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
When user "Alice" tries to add user "Brian" to a nonexistent group using the Graph API
Then the HTTP status code should be "403"
@@ -226,7 +226,7 @@ Feature: add users to group
Scenario: add multiple users to a group at once
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:
And these users have been created with default attributes:
| username |
| Brian |
| Carol |
@@ -244,7 +244,7 @@ Feature: add users to group
Scenario: admin tries to add users to a nonexistent group at once
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:
And these users have been created with default attributes:
| username |
| Brian |
| Carol |
@@ -267,7 +267,7 @@ Feature: add users to group
Scenario: admin tries to add nonexistent and existing users to a group at once
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:
And these users have been created with default attributes:
| username |
| Brian |
And user "Alice" has created a group "grp1" using the Graph API
@@ -294,7 +294,7 @@ Feature: add users to group
@issue-5702
Scenario: try to add users to a group twice
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:
And these users have been created with default attributes:
| username |
| Brian |
| Carol |
@@ -316,7 +316,7 @@ Feature: add users to group
@issue-5793
Scenario: try to add a group to another group with PATCH request
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:
And these users have been created with default attributes:
| username |
| Brian |
And these groups have been created:
@@ -330,7 +330,7 @@ Feature: add users to group
@issue-5793
Scenario: try to add a group to another group with POST request
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:
And these users have been created with default attributes:
| username |
| Brian |
And these groups have been created:
@@ -344,7 +344,7 @@ Feature: add users to group
Scenario Outline: admin tries to add a user to a group with invalid JSON
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:
And these users have been created with default attributes:
| username |
| Brian |
And user "Alice" has created a group "grp1" using the Graph API
@@ -359,7 +359,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 assigned the role "Admin" to user "Alice" using the Graph API
And these users have been created with default attributes and without skeleton files:
And these users have been created with default attributes:
| username |
| Brian |
| Carol |
@@ -378,7 +378,7 @@ Feature: add users to group
@issue-5871
Scenario: admin tries to add multiple users with wrong host
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:
And these users have been created with default attributes:
| username |
| Brian |
| Carol |
@@ -392,7 +392,7 @@ Feature: add users to group
@issue-5871
Scenario: admin tries to add single user with wrong host
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:
And these users have been created with default attributes:
| username |
| Brian |
And user "Alice" has created a group "grp1" using the Graph API
@@ -429,7 +429,7 @@ Feature: add users to group
@issue-5855
Scenario: add same user twice to a group at once
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:
And these users have been created with default attributes:
| username |
| Brian |
And user "Alice" has created a group "grp1" using the Graph API

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

@@ -5,7 +5,7 @@ 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
Given user "Alice" has been created with default attributes
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:

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

@@ -4,7 +4,7 @@ Feature: create group
So that I can add users to the group
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
@@ -32,7 +32,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
Given user "Brian" has been created with default attributes
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"

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

@@ -7,7 +7,7 @@ Feature: create user
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
Given user "Alice" has been created with default attributes
@issue-3516
Scenario Outline: admin creates a user
@@ -66,7 +66,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
Given user "Brian" has been created with default attributes
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the user "Alice" has disabled user "Brian"
When the user "Alice" creates a new user with the following attributes using the Graph API:
@@ -79,7 +79,7 @@ Feature: create user
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
Given user "Brian" has been created with default attributes
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
And the user "Alice" has deleted a user "Brian"
When the user "Alice" creates a new user with the following attributes using the Graph API:

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

@@ -4,7 +4,7 @@ Feature: delete groups
So that I can remove unnecessary groups
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
@@ -56,7 +56,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
Given user "Brian" has been created with default attributes
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
@@ -105,7 +105,7 @@ Feature: delete groups
Scenario: user should not see share received via deleted group
Given user "Alice" has uploaded file with content "sample text" to "lorem.txt"
And user "Brian" has been created with default attributes and without skeleton files
And user "Brian" has been created with default attributes
And group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has sent the following resource share invitation:

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

@@ -7,7 +7,7 @@ Feature: delete user
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
Given user "Alice" has been created with default attributes
Scenario Outline: admin user deletes a user
@@ -28,7 +28,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
Given user "brand-new-user" has been created with default attributes
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"
@@ -36,7 +36,7 @@ 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
Given user "Brian" has been created with default attributes
And the administrator has assigned the role "Admin" to user "Alice" 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
@@ -87,7 +87,7 @@ 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
Given user "Brian" has been created with default attributes
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
@@ -111,7 +111,7 @@ Feature: delete user
Scenario: admin user deletes a disabled 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 "Brian" has been created with default attributes
And the user "Alice" has disabled user "Brian"
When the user "Alice" deletes a user "Brian" using the Graph API
Then the HTTP status code should be "204"
@@ -120,8 +120,8 @@ Feature: delete user
Scenario Outline: normal user tries to delete a disabled 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 user "Brian" has been created with default attributes
And user "Carol" has been created with default attributes
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"
@@ -146,7 +146,7 @@ Feature: delete user
Scenario: personal space is deleted automatically when the user is deleted
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 "Brian" has been created with default attributes
When the user "Alice" deletes a user "Brian" using the Graph API
Then the HTTP status code should be "204"
When user "Alice" lists all spaces via the Graph API with query "$filter=driveType eq 'personal'"
@@ -155,7 +155,7 @@ Feature: delete user
Scenario: accepted share is deleted automatically when the user is deleted
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 "Brian" has been created with default attributes
And user "Brian" has created folder "new"
And user "Brian" has sent the following resource share invitation:
| resource | new |

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

@@ -4,7 +4,7 @@ Feature: edit group name
So that I can manage group name
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
@issue-5977

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

@@ -7,7 +7,7 @@ Feature: edit user
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
Given user "Alice" has been created with default attributes
And 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 | Brian |
@@ -17,7 +17,7 @@ Feature: edit user
@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
Given user "Carol" has been created with default attributes
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
@@ -277,7 +277,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
Given user "Carol" has been created with default attributes
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 "403"
@@ -359,7 +359,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
Given user "Carol" has been created with default attributes
And the user "Alice" has disabled user "Carol"
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

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

@@ -4,7 +4,7 @@ Feature: get groups and their members
So that I can see all the groups and their members
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
@@ -21,7 +21,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
Given user "Brian" has been created with default attributes
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
@@ -59,7 +59,7 @@ Feature: get groups and their members
Scenario: admin user gets users of a group
Given these users have been created with default attributes and without skeleton files:
Given these users have been created with default attributes:
| username |
| Brian |
| Carol |
@@ -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
Given user "Brian" has been created with default attributes
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
@@ -110,7 +110,7 @@ Feature: get groups and their members
Scenario: admin user gets all groups along with its member's information
Given these users have been created with default attributes and without skeleton files:
Given these users have been created with default attributes:
| username |
| Brian |
| Carol |
@@ -242,7 +242,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
Given user "Brian" has been created with default attributes
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
@@ -281,7 +281,7 @@ Feature: get groups and their members
Scenario: admin user gets a group along with its member's information
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
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"
@@ -364,7 +364,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
Given user "Brian" has been created with default attributes
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"
@@ -511,7 +511,7 @@ Feature: get groups and their members
Scenario Outline: non-admin user searches for a group by group name
Given these users have been created with default attributes and without skeleton files:
Given these users have been created with default attributes:
| username |
| Brian |
And group "tea-lover" has been created
@@ -561,7 +561,7 @@ Feature: get groups and their members
Scenario: non-admin user tries to search for a group by group name with less than 3 characters
Given these users have been created with default attributes and without skeleton files:
Given these users have been created with default attributes:
| username |
| Brian |
And group "tea-lover" has been created
@@ -593,7 +593,7 @@ Feature: get groups and their members
@issue-7990
Scenario Outline: user tries to search for groups with invalid characters/token (search term without quotation)
Given these users have been created with default attributes and without skeleton files:
Given these users have been created with default attributes:
| username |
| Brian |
And group "<group>" has been created
@@ -629,7 +629,7 @@ Feature: get groups and their members
@issue-7990
Scenario Outline: user searches for groups with special characters (search term with quotation)
Given these users have been created with default attributes and without skeleton files:
Given these users have been created with default attributes:
| username |
| Brian |
And group "<group>" has been created

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

@@ -4,7 +4,7 @@ Feature: get users
So that I can see the information
Background:
Given these users have been created with default attributes and without skeleton files:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
@@ -667,7 +667,7 @@ Feature: get users
Scenario: admin user gets all users of certain groups
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 user "Carol" has been created with default attributes
And the user "Alice" has disabled user "Carol"
And group "tea-lover" has been created
And group "coffee-lover" has been created
@@ -817,7 +817,7 @@ Feature: get users
Scenario: admin user gets all users of two groups
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 user "Carol" has been created with default attributes
And group "tea-lover" has been created
And group "coffee-lover" has been created
And group "wine-lover" has been created
@@ -938,7 +938,7 @@ Feature: get users
Scenario: admin user gets all users with certain roles and members of a certain group
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 user "Carol" has been created with default attributes
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
@@ -1421,7 +1421,7 @@ Feature: get users
@issue-7990
Scenario Outline: user tries to search other users with invalid characters/token (search term without quotation)
Given user "<user>" has been created with default attributes and without skeleton files
Given user "<user>" has been created with default attributes
When user "Brian" tries to search for user "<user>" using Graph API
Then the HTTP status code should be "400"
And the JSON data of the response should match

2
tests/acceptance/features/apiGraphUserGroup/getUserOwnInformation.feature
View File

@@ -4,7 +4,7 @@ Feature: get user's own information
So that I can see my information
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
Scenario: user gets his/her own information with no group involvement

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

@@ -4,7 +4,7 @@ Feature: remove a user from a group
So that I can manage user access to group resources
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
Scenario: admin removes a user from a group
@@ -157,7 +157,7 @@ Feature: remove a user from a group
Scenario Outline: non-admin user tries to remove a user from a nonexistent group
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
And the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
When user "Alice" tries to remove user "Brian" from a nonexistent group using the Graph API
Then the HTTP status code should be "403"
@@ -169,7 +169,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
Given user "Brian" has been created with default attributes
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"

2
tests/acceptance/features/apiGraphUserGroup/searchUserIncludingEmail.feature
View File

@@ -2,7 +2,7 @@
Feature: edit/search user including email
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
And 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 | Brian |