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/coreApiAuth/ocsGETAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: auth
So that I can make sure the endpoints need proper authentication
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
@issue-1337 @smokeTest
Scenario: using OCS anonymously
tests/acceptance/features/coreApiAuth/ocsPOSTAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: auth
So that I can make sure the endpoints need proper authentication
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
@issue-1337 @smokeTest
Scenario: send POST requests to OCS endpoints as normal user with wrong password
tests/acceptance/features/coreApiAuth/webDavAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: auth
So that I can make sure it's secure
Background:
Given user "Alice" has been created with default attributes and without skeleton files
Given user "Alice" has been created with default attributes
@smokeTest @issue-10334
Scenario Outline: using WebDAV anonymously
tests/acceptance/features/coreApiAuth/webDavCOPYAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: COPY file/folder
So that I can duplicate it
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 |
tests/acceptance/features/coreApiAuth/webDavDELETEAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: delete file/folder
So that I can remove redundant resources
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 |
tests/acceptance/features/coreApiAuth/webDavLOCKAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: LOCK file/folder
So that I can ensure that the resources won't be changed unexpectedly
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 |
tests/acceptance/features/coreApiAuth/webDavMKCOLAuth.feature
+6 -6
View File
@@ -4,7 +4,7 @@ Feature: create folder using MKCOL
So that I can organise resources in folders
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 uploaded file with content "some data" to "/textfile0.txt"
And user "Alice" has created folder "/PARENT"
And user "Alice" has created folder "/FOLDER"
@@ -40,7 +40,7 @@ Feature: create folder using MKCOL
@issue-5049 @issue-1347 @issue-1292
Scenario: send MKCOL requests to another user's webDav endpoints as normal 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 "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice"
| endpoint |
| /dav/files/%username%/textfile0.txt |
@@ -51,7 +51,7 @@ Feature: create folder using MKCOL
@issue-5049 @issue-1347 @issue-1292
Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal 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 "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user"
| endpoint |
| /dav/files/non-existent-user/textfile0.txt |
@@ -62,7 +62,7 @@ Feature: create folder using MKCOL
@issue-1347 @issue-1292
Scenario: send MKCOL requests to another user's webDav endpoints as normal user using the spaces WebDAV API
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
When user "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice"
| endpoint |
| /dav/spaces/%spaceid%/textfile0.txt |
@@ -73,7 +73,7 @@ Feature: create folder using MKCOL
@issue-5049 @issue-1347 @issue-1292
Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal user using the spaces WebDAV API
Given user "Brian" has been created with default attributes and without skeleton files
Given user "Brian" has been created with default attributes
When user "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user"
| endpoint |
| /dav/spaces/%spaceid%/textfile0.txt |
@@ -98,7 +98,7 @@ Feature: create folder using MKCOL
Scenario: send MKCOL requests to webDav endpoints using valid password and username of different 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 "Brian" requests these endpoints with "MKCOL" including body "doesnotmatter" using the password of user "Alice"
| endpoint |
| /webdav/textfile0.txt |
tests/acceptance/features/coreApiAuth/webDavMOVEAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: MOVE file/folder
So that I can organise resources according to my preference
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 |
tests/acceptance/features/coreApiAuth/webDavPOSTAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: POST file/folder
So that I can ensure the endpoints are well authenticated
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 |
tests/acceptance/features/coreApiAuth/webDavPROPFINDAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: PROPFIND file/folder
So that I can ensure the endpoints are well authenticated
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 |
tests/acceptance/features/coreApiAuth/webDavPROPPATCHAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: PROPPATCH file/folder
So that I can ensure the endpoints are well authenticated
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 |
tests/acceptance/features/coreApiAuth/webDavPUTAuth.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: PUT file/folder
So that I can ensure the endpoints are well authenticated
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 |
tests/acceptance/features/coreApiAuth/webDavSpecialURLs.feature
+1 -1
View File
@@ -4,7 +4,7 @@ Feature: make webdav request with special urls
So that I can make sure that they work
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 uploaded file with content "some data" to "/textfile0.txt"
And user "Alice" has uploaded file with content "some data" to "/textfile1.txt"
And user "Alice" has created folder "/PARENT"