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/apiAccountsHashDifficulty/assignRole.feature
+4 -4
View File
@@ -5,7 +5,7 @@ Feature: assign role
Scenario Outline: only admin user can see all existing roles
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 given "Alice" the role "<user-role>" using the settings api
When user "Alice" tries to get all existing roles
Then the HTTP status code should be "<http-status-code>"
@@ -17,7 +17,7 @@ Feature: assign role
@issue-5032
Scenario Outline: only admin user can see assignments list
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 given "Alice" the role "<user-role>" using the settings api
When user "Alice" tries to get list of assignment
Then the HTTP status code should be "<http-status-code>"
@@ -29,7 +29,7 @@ Feature: assign role
Scenario Outline: a user cannot change own role
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 given "Alice" the role "<user-role>" using the settings api
When user "Alice" changes his own role to "<desired-role>"
Then the HTTP status code should be "400"
@@ -45,7 +45,7 @@ Feature: assign role
Scenario Outline: only admin user can change the role for another user
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 |
tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature
+2 -2
View File
@@ -10,9 +10,9 @@ Feature: sharing
Scenario Outline: creating a share of a file with a user
Given using OCS API version "<ocs-api-version>"
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 "ownCloud test text file 0" to "/textfile0.txt"
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" shares file "textfile0.txt" with user "Brian" using the sharing API
And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
Examples:
tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature
+1 -1
View File
@@ -10,7 +10,7 @@ Feature: upload file
Scenario Outline: upload a file and check download content
Given using OCS API version "<ocs-api-version>"
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has been created with default attributes
And using <dav-path-version> DAV path
When user "Alice" uploads file with content "uploaded content" to "/upload.txt" using the WebDAV API
Then the content of file "/upload.txt" for user "Alice" should be "uploaded content"
tests/acceptance/features/apiAccountsHashDifficulty/webDavPUTAuthInvalid.feature
+1 -1
View File
@@ -8,7 +8,7 @@ Feature: attempt to PUT files with invalid password
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 user "Alice" has created folder "/PARENT"