sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[full-ci] [tests-only] Removed tag personalSpace, and refactored the example tables (#6250)

Browse Source 
* Refactored personalSpace tagged scenarios

* Fixed line numbers in expected failure
This commit is contained in:
Prarup Gurung
2023-05-25 17:50:00 +05:45
committed by GitHub
parent 45c31b3d61
commit d31f544a9f
60 changed files with 421 additions and 782 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature
+1 -50
View File
@@ -1,4 +1,4 @@
@api
@api
Feature: OPTIONS request
Background:
@@ -10,18 +10,6 @@ Feature: OPTIONS request
| endpoint |
| /remote.php/webdav/ |
| /remote.php/dav/files/%username%/ |
Then the HTTP status code should be "204"
And the following headers should be set
| header | value |
| Tus-Resumable | 1.0.0 |
| Tus-Version | 1.0.0 |
| Tus-Extension | creation,creation-with-upload,checksum,expiration |
| Tus-Checksum-Algorithm | md5,sha1,adler32 |
@personalSpace
Scenario: send OPTIONS request to spaces webDav endpoint using the TUS protocol with valid password and username
When user "Alice" requests these endpoints with "OPTIONS" including body "doesnotmatter" using the password of user "Alice"
| endpoint |
| /remote.php/dav/spaces/%spaceid%/ |
Then the HTTP status code should be "204"
And the following headers should be set
@@ -37,18 +25,6 @@ Feature: OPTIONS request
| endpoint |
| /remote.php/webdav/ |
| /remote.php/dav/files/%username%/ |
Then the HTTP status code should be "204"
And the following headers should be set
| header | value |
| Tus-Resumable | 1.0.0 |
| Tus-Version | 1.0.0 |
| Tus-Extension | creation,creation-with-upload,checksum,expiration |
| Tus-Checksum-Algorithm | md5,sha1,adler32 |
@personalSpace
Scenario: send OPTIONS request to spaces webDav endpoint using the TUS protocol without any authentication
When a user requests these endpoints with "OPTIONS" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
| /remote.php/dav/spaces/%spaceid%/ |
Then the HTTP status code should be "204"
And the following headers should be set
@@ -64,18 +40,6 @@ Feature: OPTIONS request
| endpoint |
| /remote.php/webdav/ |
| /remote.php/dav/files/%username%/ |
Then the HTTP status code should be "401"
And the following headers should be set
| header | value |
| Tus-Resumable | 1.0.0 |
| Tus-Version | 1.0.0 |
| Tus-Extension | creation,creation-with-upload,checksum,expiration |
| Tus-Checksum-Algorithm | md5,sha1,adler32 |
@personalSpace
Scenario: send OPTIONS request to spaces webDav endpoint using the TUS protocol with valid username and wrong password
When user "Alice" requests these endpoints with "OPTIONS" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /remote.php/dav/spaces/%spaceid%/ |
Then the HTTP status code should be "401"
And the following headers should be set
@@ -92,19 +56,6 @@ Feature: OPTIONS request
| endpoint |
| /remote.php/webdav/ |
| /remote.php/dav/files/%username%/ |
Then the HTTP status code should be "401"
And the following headers should be set
| header | value |
| Tus-Resumable | 1.0.0 |
| Tus-Version | 1.0.0 |
| Tus-Extension | creation,creation-with-upload,checksum,expiration |
| Tus-Checksum-Algorithm | md5,sha1,adler32 |
@personalSpace
Scenario: send OPTIONS requests to spaces webDav endpoints using valid password and username of different user
Given user "Brian" has been created with default attributes and without skeleton files
When user "Brian" requests these endpoints with "OPTIONS" including body "doesnotmatter" using the password of user "Alice"
| endpoint |
| /remote.php/dav/spaces/%spaceid%/ |
Then the HTTP status code should be "401"
And the following headers should be set