sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions 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-12-02 09:12:57 +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
tests/acceptance/features/apiGraph/changeRole.feature
+4 -4
View File
@@ -4,11 +4,11 @@ Feature: change role
So that I can manage the role of user
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 changes the role of another user with different roles
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 user "Alice" changes the role of user "Brian" to role "<new-user-role>" using the Graph API
@@ -49,7 +49,7 @@ Feature: change role
Scenario Outline: non-admin cannot change the user role
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
And user "Brian" has been created with default attributes and without skeleton files
And user "Brian" has been created with default attributes
When user "Alice" tries to change the role of user "Alice" to role "Admin" using the Graph API
Then the HTTP status code should be "403"
And user "Brian" should have the role "User"
@@ -62,7 +62,7 @@ Feature: change role
Scenario Outline: non-admin user tries to change the role of nonexistent user
Given the administrator has assigned the role "<user-role>" to user "Alice" using the Graph API
And user "Brian" has been created with default attributes and without skeleton files
And user "Brian" has been created with default attributes
When user "Alice" tries to change the role of user "nonexistent" to role "Admin" using the Graph API
Then the HTTP status code should be "403"
Examples:
tests/acceptance/features/apiGraph/enforcePasswordPublicLink.feature
+11 -11
View File
@@ -18,7 +18,7 @@ Feature: enforce password on public link
| config | value |
| OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD | false |
| OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD | true |
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
And using OCS API version "<ocs-api-version>"
When user "Alice" creates a public link share using the sharing API with settings
@@ -38,7 +38,7 @@ Feature: enforce password on public link
| config | value |
| OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD | false |
| OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD | true |
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
And using OCS API version "<ocs-api-version>"
When user "Alice" creates a public link share using the sharing API with settings
@@ -57,7 +57,7 @@ Feature: enforce password on public link
| config | value |
| OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD | false |
| OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD | true |
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
And using OCS API version "<ocs-api-version>"
And using SharingNG
@@ -89,7 +89,7 @@ Feature: enforce password on public link
| OCIS_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS | 2 |
| OCIS_PASSWORD_POLICY_MIN_DIGITS | 2 |
| OCIS_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS | 2 |
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
And using OCS API version "<ocs-api-version>"
When user "Alice" creates a public link share using the sharing API with settings
@@ -116,7 +116,7 @@ Feature: enforce password on public link
| OCIS_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS | 2 |
| OCIS_PASSWORD_POLICY_MIN_DIGITS | 2 |
| OCIS_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS | 2 |
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
And using OCS API version "<ocs-api-version>"
When user "Alice" creates a public link share using the sharing API with settings
@@ -149,7 +149,7 @@ Feature: enforce password on public link
| OCIS_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS | 2 |
| OCIS_PASSWORD_POLICY_MIN_DIGITS | 1 |
| OCIS_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS | 2 |
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
And using OCS API version "<ocs-api-version>"
And using SharingNG
@@ -182,7 +182,7 @@ Feature: enforce password on public link
| OCIS_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS | 2 |
| OCIS_PASSWORD_POLICY_MIN_DIGITS | 1 |
| OCIS_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS | 2 |
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
And using OCS API version "<ocs-api-version>"
And using SharingNG
@@ -212,7 +212,7 @@ Feature: enforce password on public link
Scenario Outline: create a public link with a password in accordance with the password policy (valid cases)
Given the config "<config>" has been set to "<config-value>"
And using OCS API version "2"
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
When user "Alice" creates a public link share using the sharing API with settings
| path | /testfile.txt |
@@ -238,7 +238,7 @@ Feature: enforce password on public link
Scenario Outline: try to create a public link with a password that does not comply with the password policy (invalid cases)
Given using OCS API version "2"
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
When user "Alice" creates a public link share using the sharing API with settings
| path | /testfile.txt |
@@ -258,7 +258,7 @@ Feature: enforce password on public link
Scenario Outline: update a public link with a password that is listed in the Banned-Password-List
Given the config "OCIS_PASSWORD_POLICY_BANNED_PASSWORDS_LIST" has been set to path "config/drone/banned-password-list.txt"
And using OCS API version "2"
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
And using SharingNG
And user "Alice" has created the following resource link share:
@@ -281,7 +281,7 @@ Feature: enforce password on public link
Scenario Outline: create a public link with a password that is listed in the Banned-Password-List
Given the config "OCIS_PASSWORD_POLICY_BANNED_PASSWORDS_LIST" has been set to path "config/drone/banned-password-list.txt"
And using OCS API version "2"
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
When user "Alice" creates a public link share using the sharing API with settings
| path | /testfile.txt |
tests/acceptance/features/apiGraph/getApplications.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: get applications
So that I can see which role belongs to what user
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 lists all the groups
tests/acceptance/features/apiGraph/getAssignedRole.feature
+3 -3
View File
@@ -4,7 +4,7 @@ Feature: assign role
So that users without an admin role cannot get the list of roles, assignments list and assign roles to users
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: get assigned role of a user
@@ -47,12 +47,12 @@ Feature: assign role
Scenario: non-admin user tries to get assigned role of another user
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
When user "Alice" tries to get the assigned role of user "Brian" using the Graph API
Then the HTTP status code should be "403"
Scenario: non-admin user tries to get assigned role of nonexistent user
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
When user "Alice" tries to get the assigned role of user "nonexistent" using the Graph API
Then the HTTP status code should be "403"
tests/acceptance/features/apiGraph/roleManagementEndpoint.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: permissions role definitions
So that I can find out if those endpoints are working correctly or not
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
Scenario: get a list of permissions role definitions
tests/acceptance/features/apiGraph/unassignRole.feature
+3 -3
View File
@@ -4,11 +4,11 @@ Feature: unassign user role
So that the role of user is set to default
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 unassigns the role of another 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 administrator has assigned the role "<user-role>" to user "Brian" using the Graph API
When user "Alice" unassigns the role of user "Brian" using the Graph API
@@ -32,7 +32,7 @@ Feature: unassign user role
Scenario: non-admin user tries to unassign role of another user
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
When user "Alice" tries to unassign the role of user "Brian" using the Graph API
Then the HTTP status code should be "403"
And user "Brian" should have the role "User" assigned
tests/acceptance/features/apiGraph/userGDPRExport.feature
+5 -5
View File
@@ -4,7 +4,7 @@ Feature: user GDPR (General Data Protection Regulation) report
So that I can review what events are stored by the server
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
And using spaces DAV path
@@ -495,7 +495,7 @@ 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
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
And the administrator has assigned the role "<new-user-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
@@ -585,7 +585,7 @@ Feature: user GDPR (General Data Protection Regulation) report
Scenario: generate a GDPR report and check events when a user shares a folder
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
And user "Alice" has created folder "/folderMain"
And user "Alice" has sent the following resource share invitation:
| resource | folderMain |
@@ -714,7 +714,7 @@ Feature: user GDPR (General Data Protection Regulation) report
Scenario: generate a GDPR report and check events when a user creates a public link share
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
And user "Alice" has created folder "/folderMain"
And user "Alice" has created the following resource link share:
| resource | folderMain |
@@ -860,7 +860,7 @@ Feature: user GDPR (General Data Protection Regulation) report
Scenario: generate a GDPR report and check events when a space is shared
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 "Space Admin" to user "Alice" using the Graph API
And user "Alice" has created a space "GDPR Space" with the default quota using the Graph API
And user "Alice" has sent the following space share invitation: