From ab1de656ad13d4d8cbf131cad348a38322fc0427 Mon Sep 17 00:00:00 2001 From: prajwol Date: Mon, 5 Jun 2023 17:18:44 +0545 Subject: [PATCH] refactoring feature files --- .../expected-failures-API-on-OCIS-storage.md | 70 +++++++++---------- .../coreApiWebdavMove1/moveFolder.feature | 12 ++-- .../moveFolderToBlacklistedName.feature | 2 +- .../coreApiWebdavMove2/moveFile.feature | 24 +++---- .../moveShareOnOcis.feature | 20 +++--- .../downloadFile.feature | 10 +-- .../coreApiWebdavOperations/listFiles.feature | 30 ++++---- .../coreApiWebdavOperations/propfind.feature | 7 +- .../refuseAccess.feature | 4 +- .../coreApiWebdavPreviews/previews.feature | 5 +- .../coreApiWebdavProperties1/copyFile.feature | 40 +++++------ .../createFileFolder.feature | 8 +-- .../coreApiWebdavProperties1/getQuota.feature | 10 +-- .../setFileProperties.feature | 10 +-- .../coreApiWebdavUpload1/uploadFile.feature | 2 +- .../uploadFileUsingOldChunking.feature | 12 ++-- .../coreApiWebdavUploadTUS/checksums.feature | 27 +++---- .../creationWithUploadExtension.feature | 3 + .../lowLevelCreationExtension.feature | 3 + .../lowLevelUpload.feature | 3 + .../optionsRequest.feature | 3 + .../coreApiWebdavUploadTUS/uploadFile.feature | 6 +- .../uploadToMoveFolder.feature | 2 +- .../uploadToShare.feature | 36 +++++----- 24 files changed, 186 insertions(+), 163 deletions(-) diff --git a/tests/acceptance/expected-failures-API-on-OCIS-storage.md b/tests/acceptance/expected-failures-API-on-OCIS-storage.md index 7ae655931..6afa75ee0 100644 --- a/tests/acceptance/expected-failures-API-on-OCIS-storage.md +++ b/tests/acceptance/expected-failures-API-on-OCIS-storage.md @@ -215,11 +215,11 @@ cannot share a folder with create permission #### [download previews of other users file](https://github.com/owncloud/ocis/issues/2071) -- [coreApiWebdavPreviews/previews.feature:91](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L91) +- [coreApiWebdavPreviews/previews.feature:94](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L94) #### [different error message detail for previews of folder](https://github.com/owncloud/ocis/issues/2064) -- [coreApiWebdavPreviews/previews.feature:100](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L100) +- [coreApiWebdavPreviews/previews.feature:103](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L103) #### [copying a folder within a public link folder to folder with same name as an already existing file overwrites the parent file](https://github.com/owncloud/ocis/issues/1232) @@ -461,44 +461,44 @@ And other missing implementation of favorites #### [PATCH request for TUS upload with wrong checksum gives incorrect response](https://github.com/owncloud/ocis/issues/1755) -- [coreApiWebdavUploadTUS/checksums.feature:84](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L84) -- [coreApiWebdavUploadTUS/checksums.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L85) -- [coreApiWebdavUploadTUS/checksums.feature:86](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L86) - [coreApiWebdavUploadTUS/checksums.feature:87](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L87) -- [coreApiWebdavUploadTUS/checksums.feature:92](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L92) -- [coreApiWebdavUploadTUS/checksums.feature:93](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L93) -- [coreApiWebdavUploadTUS/checksums.feature:173](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L173) -- [coreApiWebdavUploadTUS/checksums.feature:174](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L174) -- [coreApiWebdavUploadTUS/checksums.feature:179](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L179) -- [coreApiWebdavUploadTUS/checksums.feature:226](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L226) -- [coreApiWebdavUploadTUS/checksums.feature:227](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L227) -- [coreApiWebdavUploadTUS/checksums.feature:228](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L228) +- [coreApiWebdavUploadTUS/checksums.feature:88](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L88) +- [coreApiWebdavUploadTUS/checksums.feature:89](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L89) +- [coreApiWebdavUploadTUS/checksums.feature:90](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L90) +- [coreApiWebdavUploadTUS/checksums.feature:95](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L95) +- [coreApiWebdavUploadTUS/checksums.feature:96](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L96) +- [coreApiWebdavUploadTUS/checksums.feature:176](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L176) +- [coreApiWebdavUploadTUS/checksums.feature:177](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L177) +- [coreApiWebdavUploadTUS/checksums.feature:182](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L182) - [coreApiWebdavUploadTUS/checksums.feature:229](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L229) -- [coreApiWebdavUploadTUS/checksums.feature:234](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L234) -- [coreApiWebdavUploadTUS/checksums.feature:235](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L235) -- [coreApiWebdavUploadTUS/checksums.feature:282](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L282) -- [coreApiWebdavUploadTUS/checksums.feature:283](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L283) -- [coreApiWebdavUploadTUS/checksums.feature:284](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L284) +- [coreApiWebdavUploadTUS/checksums.feature:230](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L230) +- [coreApiWebdavUploadTUS/checksums.feature:231](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L231) +- [coreApiWebdavUploadTUS/checksums.feature:232](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L232) +- [coreApiWebdavUploadTUS/checksums.feature:237](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L237) +- [coreApiWebdavUploadTUS/checksums.feature:238](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L238) - [coreApiWebdavUploadTUS/checksums.feature:285](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L285) -- [coreApiWebdavUploadTUS/checksums.feature:290](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L290) -- [coreApiWebdavUploadTUS/checksums.feature:291](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L291) -- [coreApiWebdavUploadTUS/optionsRequest.feature:8](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L8) -- [coreApiWebdavUploadTUS/optionsRequest.feature:23](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L23) -- [coreApiWebdavUploadTUS/uploadToShare.feature:174](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L174) -- [coreApiWebdavUploadTUS/uploadToShare.feature:175](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L175) -- [coreApiWebdavUploadTUS/uploadToShare.feature:193](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L193) -- [coreApiWebdavUploadTUS/uploadToShare.feature:194](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L194) -- [coreApiWebdavUploadTUS/uploadToShare.feature:212](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L212) -- [coreApiWebdavUploadTUS/uploadToShare.feature:213](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L213) -- [coreApiWebdavUploadTUS/uploadToShare.feature:251](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L251) -- [coreApiWebdavUploadTUS/uploadToShare.feature:252](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L252) -- [coreApiWebdavUploadTUS/uploadToShare.feature:293](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L293) -- [coreApiWebdavUploadTUS/uploadToShare.feature:294](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L294) +- [coreApiWebdavUploadTUS/checksums.feature:286](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L286) +- [coreApiWebdavUploadTUS/checksums.feature:287](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L287) +- [coreApiWebdavUploadTUS/checksums.feature:288](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L288) +- [coreApiWebdavUploadTUS/checksums.feature:293](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L293) +- [coreApiWebdavUploadTUS/checksums.feature:294](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L294) +- [coreApiWebdavUploadTUS/optionsRequest.feature:11](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L11) +- [coreApiWebdavUploadTUS/optionsRequest.feature:26](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L26) +- [coreApiWebdavUploadTUS/uploadToShare.feature:176](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L176) +- [coreApiWebdavUploadTUS/uploadToShare.feature:177](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L177) +- [coreApiWebdavUploadTUS/uploadToShare.feature:195](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L195) +- [coreApiWebdavUploadTUS/uploadToShare.feature:196](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L196) +- [coreApiWebdavUploadTUS/uploadToShare.feature:214](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L214) +- [coreApiWebdavUploadTUS/uploadToShare.feature:215](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L215) +- [coreApiWebdavUploadTUS/uploadToShare.feature:253](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L253) +- [coreApiWebdavUploadTUS/uploadToShare.feature:254](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L254) +- [coreApiWebdavUploadTUS/uploadToShare.feature:295](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L295) +- [coreApiWebdavUploadTUS/uploadToShare.feature:296](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L296) #### [TUS OPTIONS requests do not reply with TUS headers when invalid password](https://github.com/owncloud/ocis/issues/1012) -- [coreApiWebdavUploadTUS/optionsRequest.feature:38](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L38) -- [coreApiWebdavUploadTUS/optionsRequest.feature:53](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L53) +- [coreApiWebdavUploadTUS/optionsRequest.feature:41](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L41) +- [coreApiWebdavUploadTUS/optionsRequest.feature:56](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L56) #### [Trying to accept a share with invalid ID gives incorrect OCS and HTTP status](https://github.com/owncloud/ocis/issues/2111) @@ -569,7 +569,7 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers #### [Preview of text file with UTF content does not render correctly](https://github.com/owncloud/ocis/issues/2570) -- [coreApiWebdavPreviews/previews.feature:134](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L134) +- [coreApiWebdavPreviews/previews.feature:137](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L137) #### [Share path in the response is different between share states](https://github.com/owncloud/ocis/issues/2540) diff --git a/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature b/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature index a02368f72..b44b25de8 100644 --- a/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature +++ b/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature @@ -9,7 +9,7 @@ Feature: move (rename) folder And user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: Renaming a folder to a backslash should return an error + Scenario Outline: renaming a folder to a backslash should return an error Given using DAV path And user "Alice" has created folder "/testshare" When user "Alice" moves folder "/testshare" to "\" using the WebDAV API @@ -27,7 +27,7 @@ Feature: move (rename) folder | spaces | - Scenario Outline: Renaming a folder beginning with a backslash should return an error + Scenario Outline: renaming a folder beginning with a backslash should return an error Given using DAV path And user "Alice" has created folder "/testshare" When user "Alice" moves folder "/testshare" to "\testshare" using the WebDAV API @@ -45,7 +45,7 @@ Feature: move (rename) folder | spaces | - Scenario Outline: Renaming a folder including a backslash encoded should return an error + Scenario Outline: renaming a folder including a backslash encoded should return an error Given using DAV path And user "Alice" has created folder "/testshare" When user "Alice" moves folder "/testshare" to "/hola\hola" using the WebDAV API @@ -63,7 +63,7 @@ Feature: move (rename) folder | spaces | - Scenario Outline: Move a folder into an other one + Scenario Outline: move a folder into an other folder Given using DAV path And user "Alice" has created folder "/testshare" And user "Alice" has created folder "/an-other-folder" @@ -84,7 +84,7 @@ Feature: move (rename) folder | spaces | - Scenario Outline: Move a folder into a nonexistent one + Scenario Outline: move a folder into a nonexistent folder Given using DAV path And user "Alice" has created folder "/testshare" When user "Alice" moves folder "/testshare" to "/not-existing/testshare" using the WebDAV API @@ -132,7 +132,7 @@ Feature: move (rename) folder | spaces | /..upload | @skipOnRevaMaster @issue-3023 - Scenario Outline: Moving a folder into a sub-folder of itself + Scenario Outline: moving a folder into a sub-folder of itself Given using DAV path And user "Alice" has created folder "PARENT" And user "Alice" has created folder "PARENT/CHILD" diff --git a/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature b/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature index 98c911c13..1038bdc50 100644 --- a/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature +++ b/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature @@ -9,7 +9,7 @@ Feature: users cannot move (rename) a folder to a blacklisted name And user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: Rename a folder to a name that is banned by default + Scenario Outline: rename a folder to a name that is banned by default Given using DAV path And user "Alice" has created folder "/testshare" When user "Alice" moves folder "/testshare" to "/.htaccess" using the WebDAV API diff --git a/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature b/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature index 1af8b00dd..8d3da9b24 100644 --- a/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature +++ b/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature @@ -9,7 +9,7 @@ Feature: move (rename) file And user "Alice" has been created with default attributes and without skeleton files @smokeTest - Scenario Outline: Moving a file + Scenario Outline: moving a file Given using DAV path And user "Alice" has created folder "FOLDER" And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt" @@ -29,7 +29,7 @@ Feature: move (rename) file | spaces | @smokeTest - Scenario Outline: Moving and overwriting a file + Scenario Outline: moving and overwriting a file Given using DAV path And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt" And user "Alice" has uploaded file with content "ownCloud test text file 1" to "textfile1.txt" @@ -49,7 +49,7 @@ Feature: move (rename) file | spaces | - Scenario Outline: Moving (renaming) a file to be only different case + Scenario Outline: moving (renaming) a file to be only different case Given using DAV path And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt" When user "Alice" moves file "/textfile0.txt" to "/TextFile0.txt" using the WebDAV API @@ -67,7 +67,7 @@ Feature: move (rename) file | spaces | @smokeTest - Scenario Outline: Moving (renaming) a file to a file with only different case to an existing file + Scenario Outline: moving (renaming) a file to a file with only different case to an existing file Given using DAV path And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt" And user "Alice" has uploaded file with content "ownCloud test text file 1" to "textfile1.txt" @@ -86,7 +86,7 @@ Feature: move (rename) file | spaces | - Scenario Outline: Moving (renaming) a file to a file in a folder with only different case to an existing file + Scenario Outline: moving (renaming) a file to a file in a folder with only different case to an existing file Given using DAV path And user "Alice" has created folder "PARENT" And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt" @@ -138,7 +138,7 @@ Feature: move (rename) file | spaces | - Scenario Outline: Checking file id after a move + Scenario Outline: checking file id after a move Given using DAV path And user "Alice" has created folder "FOLDER" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" @@ -159,7 +159,7 @@ Feature: move (rename) file | spaces | @issue-1295 - Scenario Outline: Renaming a file to a path with extension .part should not be possible + Scenario Outline: renaming a file to a path with extension .part should not be possible Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToRename.txt" When user "Alice" moves file "/fileToRename.txt" to "/welcome.part" using the WebDAV API @@ -278,7 +278,7 @@ Feature: move (rename) file | spaces | @smokeTest - Scenario Outline: user tries to rename a file that doesnt exist + Scenario Outline: user tries to rename a file that doesn't exist Given using DAV path When user "Alice" moves file "/doesNotExist.txt" to "/exist.txt" using the WebDAV API Then the HTTP status code should be "404" @@ -294,7 +294,7 @@ Feature: move (rename) file | spaces | - Scenario Outline: Moving a hidden file + Scenario Outline: moving a hidden file Given using DAV path And user "Alice" has created folder "FOLDER" And user "Alice" has uploaded the following files with content "hidden file" @@ -325,7 +325,7 @@ Feature: move (rename) file | spaces | - Scenario Outline: Renaming to/from a hidden file + Scenario Outline: renaming to/from a hidden file Given using DAV path And user "Alice" has uploaded the following files with content "hidden file" | path | @@ -355,7 +355,7 @@ Feature: move (rename) file | spaces | - Scenario Outline: Moving a file (deep moves with various folder and file names) + Scenario Outline: moving a file (deep moves with various folder and file names) Given using DAV path And user "Alice" has created folder "" And user "Alice" has created folder "" @@ -397,7 +397,7 @@ Feature: move (rename) file | spaces | texta | file.txt | textb | 1 | - Scenario Outline: Moving a file from a folder to the root + Scenario Outline: moving a file from a folder to the root Given using DAV path And user "Alice" has created folder "" And user "Alice" has uploaded file with content "ownCloud test text file 0" to "//" diff --git a/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature b/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature index 954a98a76..ab24a2033 100644 --- a/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature +++ b/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature @@ -1,4 +1,4 @@ -@api +@api Feature: move (rename) file As a user I want to be able to move and rename files @@ -9,7 +9,7 @@ Feature: move (rename) file And user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: Moving a file into a shared folder as the sharee and as the sharer + Scenario Outline: moving a file into a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -33,7 +33,7 @@ Feature: move (rename) file | new | Brian | /testshare | - Scenario Outline: Moving a file out of a shared folder as the sharer + Scenario Outline: moving a file out of a shared folder as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -55,7 +55,7 @@ Feature: move (rename) file | new | - Scenario Outline: Can not move a file out of a shared folder as the sharee + Scenario Outline: moving a file out of a shared folder as the sharee Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -76,7 +76,7 @@ Feature: move (rename) file | new | - Scenario Outline: Moving a folder into a shared folder as the sharee and as the sharer + Scenario Outline: moving a folder into a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -101,7 +101,7 @@ Feature: move (rename) file | new | Brian | /testshare | - Scenario Outline: Moving a folder out of a shared folder as the sharer + Scenario Outline: moving a folder out of a shared folder as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created the following folders @@ -126,7 +126,7 @@ Feature: move (rename) file | new | - Scenario Outline: Moving a folder out of a shared folder as the sharee + Scenario Outline: moving a folder out of a shared folder as the sharee Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created the following folders @@ -150,7 +150,7 @@ Feature: move (rename) file | new | - Scenario Outline: Moving a file to a shared folder with no permissions + Scenario Outline: moving a file to a shared folder with no permissions Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" And user "Brian" has been created with default attributes and without skeleton files @@ -170,7 +170,7 @@ Feature: move (rename) file | new | - Scenario Outline: Moving a file to overwrite a file in a shared folder with no permissions + Scenario Outline: moving a file to overwrite a file in a shared folder with no permissions Given using DAV path 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 @@ -192,7 +192,7 @@ Feature: move (rename) file | new | - Scenario Outline: Checking file id after a move between received shares + Scenario Outline: checking file id after a move between received shares Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created the following folders diff --git a/tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature b/tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature index dd3b632d2..ccacd20a2 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature @@ -60,7 +60,7 @@ Feature: download file | spaces | - Scenario Outline: Get the size of a file + Scenario Outline: get the size of a file Given using DAV path And user "Alice" has uploaded file with content "This is a test file" to "test-file.txt" When user "Alice" gets the size of file "test-file.txt" using the WebDAV API @@ -78,7 +78,7 @@ Feature: download file | spaces | @issue-1316 - Scenario Outline: Get the content-length response header of a pdf file + Scenario Outline: get the content-length response header of a pdf file Given using DAV path And user "Alice" has uploaded file "filesForUpload/simple.pdf" to "/simple.pdf" When user "Alice" downloads file "/simple.pdf" using the WebDAV API @@ -97,7 +97,7 @@ Feature: download file | spaces | @issue-1316 - Scenario Outline: Get the content-length response header of an image file + Scenario Outline: get the content-length response header of an image file Given using DAV path And user "Alice" has uploaded file "filesForUpload/testavatar.png" to "/testavatar.png" When user "Alice" downloads file "/testavatar.png" using the WebDAV API @@ -116,7 +116,7 @@ Feature: download file | spaces | - Scenario Outline: Download a file with comma in the filename + Scenario Outline: download a file with comma in the filename Given using DAV path And user "Alice" has uploaded file with content "file with comma in filename" to When user "Alice" downloads file using the WebDAV API @@ -264,7 +264,7 @@ Feature: download file | spaces | @smokeTest - Scenario Outline: Downloading a file should serve security headers + Scenario Outline: downloading a file should serve security headers Given using DAV path When user "Alice" downloads file "/welcome.txt" using the WebDAV API Then the HTTP status code should be "200" diff --git a/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature b/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature index 9f1d40007..3b1c9c4d8 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature @@ -24,7 +24,7 @@ Feature: list files | simple-folder/simple-folder1/simple-folder2/welcome.txt | - Scenario Outline: Get the list of resources in the root folder with depth 0 + Scenario Outline: get the list of resources in the root folder with depth 0 Given using DAV path When user "Alice" lists the resources in "/" with depth "0" using the WebDAV API Then the HTTP status code should be "207" @@ -48,7 +48,7 @@ Feature: list files | spaces | - Scenario Outline: Get the list of resources in the root folder with depth 1 + Scenario Outline: get the list of resources in the root folder with depth 1 Given using DAV path When user "Alice" lists the resources in "/" with depth "1" using the WebDAV API Then the HTTP status code should be "207" @@ -74,7 +74,7 @@ Feature: list files | spaces | @depthInfinityPropfindEnabled - Scenario Outline: Get the list of resources in the root folder with depth infinity + Scenario Outline: get the list of resources in the root folder with depth infinity Given using DAV path When user "Alice" lists the resources in "/" with depth "infinity" using the WebDAV API Then the HTTP status code should be "207" @@ -103,7 +103,7 @@ Feature: list files | spaces | - Scenario Outline: Get the list of resources in a folder with depth 0 + Scenario Outline: get the list of resources in a folder with depth 0 Given using DAV path When user "Alice" lists the resources in "/simple-folder" with depth "0" using the WebDAV API Then the HTTP status code should be "207" @@ -127,7 +127,7 @@ Feature: list files | spaces | - Scenario Outline: Get the list of resources in a folder with depth 1 + Scenario Outline: get the list of resources in a folder with depth 1 Given using DAV path When user "Alice" lists the resources in "/simple-folder" with depth "1" using the WebDAV API Then the HTTP status code should be "207" @@ -155,7 +155,7 @@ Feature: list files | spaces | @depthInfinityPropfindEnabled - Scenario Outline: Get the list of resources in a folder with depth infinity + Scenario Outline: get the list of resources in a folder with depth infinity Given using DAV path When user "Alice" lists the resources in "/simple-folder" with depth "infinity" using the WebDAV API Then the HTTP status code should be "207" @@ -180,7 +180,7 @@ Feature: list files | spaces | - Scenario: Get the list of resources in a folder shared through public link with depth 0 + Scenario: get the list of resources in a folder shared through public link with depth 0 Given using new DAV path And user "Alice" has created the following folders | path | @@ -203,7 +203,7 @@ Feature: list files | /simple-folder1/simple-folder2/simple-folder3/simple-folder4 | - Scenario: Get the list of resources in a folder shared through public link with depth 1 + Scenario: get the list of resources in a folder shared through public link with depth 1 Given using new DAV path And user "Alice" has created the following folders | path | @@ -228,7 +228,7 @@ Feature: list files | /simple-folder1/simple-folder2/simple-folder3/simple-folder4 | @depthInfinityPropfindEnabled - Scenario: Get the list of resources in a folder shared through public link with depth infinity + Scenario: get the list of resources in a folder shared through public link with depth infinity Given using new DAV path And user "Alice" has created the following folders | path | @@ -251,7 +251,7 @@ Feature: list files | /simple-folder1/simple-folder2/simple-folder3/simple-folder4 | - Scenario Outline: Get the list of files in the trashbin with depth 0 + Scenario Outline: get the list of files in the trashbin with depth 0 Given using DAV path And user "Alice" has deleted the following resources | path | @@ -282,7 +282,7 @@ Feature: list files | spaces | - Scenario Outline: Get the list of files in the trashbin with depth 1 + Scenario Outline: get the list of files in the trashbin with depth 1 Given using DAV path And user "Alice" has deleted the following resources | path | @@ -315,7 +315,7 @@ Feature: list files | spaces | @depthInfinityPropfindEnabled - Scenario Outline: Get the list of files in the trashbin with depth infinity + Scenario Outline: get the list of files in the trashbin with depth infinity Given using DAV path And user "Alice" has deleted the following resources | path | @@ -346,7 +346,7 @@ Feature: list files | spaces | @depthInfinityPropfindDisabled - Scenario Outline: Get the list of resources in the root folder with depth infinity when depth infinity is not allowed + Scenario Outline: get the list of resources in the root folder with depth infinity when depth infinity is not allowed Given using DAV path When user "Alice" lists the resources in "/" with depth "infinity" using the WebDAV API Then the HTTP status code should be "412" @@ -361,7 +361,7 @@ Feature: list files | spaces | @depthInfinityPropfindDisabled - Scenario Outline: Get the list of resources in a folder shared through public link with depth infinity when depth infinity is not allowed + Scenario Outline: get the list of resources in a folder shared through public link with depth infinity when depth infinity is not allowed Given using DAV path And user "Alice" has created the following folders | path | @@ -380,7 +380,7 @@ Feature: list files | spaces | @depthInfinityPropfindDisabled - Scenario Outline: Get the list of files in the trashbin with depth infinity when depth infinity is not allowed + Scenario Outline: get the list of files in the trashbin with depth infinity when depth infinity is not allowed Given using DAV path And user "Alice" has deleted the following resources | path | diff --git a/tests/acceptance/features/coreApiWebdavOperations/propfind.feature b/tests/acceptance/features/coreApiWebdavOperations/propfind.feature index 0ac7918a9..75ca8f991 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/propfind.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/propfind.feature @@ -1,8 +1,11 @@ @api Feature: PROPFIND + As a user + I want to retrieve all properties of a resource + So that I can get the information about a resource @issue-751 - Scenario Outline: PROPFIND to "/remote.php/dav/(files|spaces)" + Scenario Outline: send PROPFIND request to "/remote.php/dav/(files|spaces)" Given user "Alice" has been created with default attributes and without skeleton files When user "Alice" requests "" with "PROPFIND" using basic auth Then the HTTP status code should be "405" @@ -16,7 +19,7 @@ Feature: PROPFIND | /remote.php/dav/spaces | - Scenario Outline: PROPFIND to "/remote.php/dav/(files|spaces)" with depth header + Scenario Outline: send PROPFIND request to "/remote.php/dav/(files|spaces)" with depth header Given user "Alice" has been created with default attributes and without skeleton files When user "Alice" requests "" with "PROPFIND" using basic auth and with headers | header | value | diff --git a/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature b/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature index 815477ec7..09efa70a3 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature @@ -8,7 +8,7 @@ Feature: refuse access Given using OCS API version "1" @smokeTest - Scenario Outline: Unauthenticated call + Scenario Outline: unauthenticated call # cannot perform with spaces WebDAV due to the absence of user Given using DAV path When an unauthenticated client connects to the DAV endpoint using the WebDAV API @@ -23,7 +23,7 @@ Feature: refuse access | new | - Scenario Outline: A disabled user cannot use webdav + Scenario Outline: disabled user cannot use webdav Given using DAV path And user "Alice" has been created with default attributes and without skeleton files And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" diff --git a/tests/acceptance/features/coreApiWebdavPreviews/previews.feature b/tests/acceptance/features/coreApiWebdavPreviews/previews.feature index 9d5293c75..98c396c72 100644 --- a/tests/acceptance/features/coreApiWebdavPreviews/previews.feature +++ b/tests/acceptance/features/coreApiWebdavPreviews/previews.feature @@ -1,5 +1,8 @@ @api @preview-extension-required Feature: previews of files downloaded through the webdav API + As a user + I want to be able to download the preview of the files + So that I can view the contents of the files Background: Given user "Alice" has been created with default attributes and without skeleton files @@ -131,7 +134,7 @@ Feature: previews of files downloaded through the webdav API And as user "Brian" the preview of "/Shares/parent.txt" with width "32" and height "32" should have been changed - Scenario: it should update the preview content if the file content is updated (content with UTF chars) + Scenario: preview content should be updated if the file content is updated (content with UTF chars) Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/lorem.txt" And user "Alice" has uploaded file with content "सिमसिमे पानी" to "/lorem.txt" When user "Alice" downloads the preview of "/lorem.txt" with width "32" and height "32" using the WebDAV API diff --git a/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature b/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature index 2310a35f3..7cbfa9e77 100644 --- a/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature +++ b/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature @@ -12,7 +12,7 @@ Feature: copy file And user "Alice" has created folder "/FOLDER" @smokeTest - Scenario Outline: Copying a file + Scenario Outline: copying a file Given using DAV path When user "Alice" copies file "/textfile0.txt" to "/FOLDER/textfile0.txt" using the WebDAV API Then the HTTP status code should be "201" @@ -28,7 +28,7 @@ Feature: copy file | spaces | @smokeTest - Scenario Outline: Copying and overwriting a file + Scenario Outline: copying and overwriting a file Given using DAV path When user "Alice" copies file "/textfile0.txt" to "/textfile1.txt" using the WebDAV API Then the HTTP status code should be "204" @@ -44,7 +44,7 @@ Feature: copy file | spaces | - Scenario Outline: Copying a file when 2 files exist with different case + Scenario Outline: copying a file when 2 files exist with different case Given using DAV path # "/textfile1.txt" already exists in the skeleton, make another with only case differences in the file name When user "Alice" copies file "/textfile0.txt" to "/TextFile1.txt" using the WebDAV API @@ -62,7 +62,7 @@ Feature: copy file | spaces | - Scenario Outline: Copying a file to a folder with no permissions + Scenario Outline: copying a file to a folder with no permissions Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -81,7 +81,7 @@ Feature: copy file | new | - Scenario Outline: Copying a file to overwrite a file into a folder with no permissions + Scenario Outline: copying a file to overwrite a file into a folder with no permissions Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -102,7 +102,7 @@ Feature: copy file | new | @issue-1345 - Scenario Outline: Copying file to a path with extension .part should not be possible + Scenario Outline: copying file to a path with extension .part should not be possible Given using DAV path When user "Alice" copies file "/textfile1.txt" to "/textfile1.part" using the WebDAV API Then the HTTP status code should be "400" @@ -567,7 +567,7 @@ Feature: copy file | spaces | - Scenario Outline: Copy file into a nonexistent folder + Scenario Outline: copy file into a nonexistent folder Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToCopy.txt" When user "Alice" copies file "/fileToCopy.txt" to "/not-existing-folder/fileToCopy.txt" using the WebDAV API @@ -584,7 +584,7 @@ Feature: copy file | spaces | - Scenario Outline: Copy a nonexistent file into a folder + Scenario Outline: copy a nonexistent file into a folder Given using DAV path When user "Alice" copies file "/doesNotExist.txt" to "/FOLDER/doesNotExist.txt" using the WebDAV API Then the HTTP status code should be "404" @@ -600,7 +600,7 @@ Feature: copy file | spaces | - Scenario Outline: Copy a folder into a nonexistent one + Scenario Outline: copy a folder into a nonexistent one Given using DAV path And user "Alice" has created folder "/testshare" When user "Alice" copies folder "/testshare" to "/not-existing/testshare" using the WebDAV API @@ -618,7 +618,7 @@ Feature: copy file | spaces | - Scenario Outline: Copying a file into a shared folder as the sharee + Scenario Outline: copying a file into a shared folder as the sharee Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -638,7 +638,7 @@ Feature: copy file | new | - Scenario Outline: Copying a file into a shared folder as the sharer + Scenario Outline: copying a file into a shared folder as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -659,7 +659,7 @@ Feature: copy file | new | - Scenario Outline: Copying a file out of a shared folder as the sharee + Scenario Outline: copying a file out of a shared folder as the sharee Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -681,7 +681,7 @@ Feature: copy file | new | - Scenario Outline: Copying a file out of a shared folder as the sharer + Scenario Outline: copying a file out of a shared folder as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -703,7 +703,7 @@ Feature: copy file | new | - Scenario Outline: Copying a hidden file + Scenario Outline: copying a hidden file Given using DAV path And user "Alice" has uploaded the following files with content "hidden file" | path | @@ -730,7 +730,7 @@ Feature: copy file | spaces | - Scenario Outline: Copying a file between shares received from different users + Scenario Outline: copying a file between shares received from different users Given using DAV path 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 @@ -761,7 +761,7 @@ Feature: copy file | new | - Scenario Outline: Copying a folder between shares received from different users + Scenario Outline: copying a folder between shares received from different users Given using DAV path 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 @@ -793,7 +793,7 @@ Feature: copy file | new | - Scenario Outline: Copying a file to a folder that is shared with multiple users + Scenario Outline: copying a file to a folder that is shared with multiple users Given using DAV path 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 @@ -822,7 +822,7 @@ Feature: copy file | new | - Scenario Outline: Copy a folder into another one + Scenario Outline: copy a folder into another one Given using DAV path And user "Alice" has created folder "/testshare" And user "Alice" has created folder "/an-other-folder" @@ -843,7 +843,7 @@ Feature: copy file | spaces | @skipOnRevaMaster @issue-3023 - Scenario Outline: Copying a folder into a sub-folder of itself + Scenario Outline: copying a folder into a sub-folder of itself Given using DAV path And user "Alice" has created folder "/PARENT" And user "Alice" has created folder "/PARENT/CHILD" @@ -860,7 +860,7 @@ Feature: copy file | spaces | - Scenario Outline: Copying a folder with a file into another folder + Scenario Outline: copying a folder with a file into another folder Given using DAV path And user "Alice" has created folder "/FOLDER1" And user "Alice" has created folder "/FOLDER2" diff --git a/tests/acceptance/features/coreApiWebdavProperties1/createFileFolder.feature b/tests/acceptance/features/coreApiWebdavProperties1/createFileFolder.feature index 526ca36f0..e3c6bdb39 100644 --- a/tests/acceptance/features/coreApiWebdavProperties1/createFileFolder.feature +++ b/tests/acceptance/features/coreApiWebdavProperties1/createFileFolder.feature @@ -46,7 +46,7 @@ Feature: create files and folder | spaces | /new&folder | @smokeTest - Scenario Outline: Creating a folder + Scenario Outline: get resourcetype property of a folder Given using DAV path And user "Alice" has created folder "/test_folder" When user "Alice" gets the following properties of folder "/test_folder" using the WebDAV API @@ -65,7 +65,7 @@ Feature: create files and folder | spaces | - Scenario Outline: Creating a folder with special chars + Scenario Outline: get resourcetype property of a folder with special chars Given using DAV path And user "Alice" has created folder "/test_folder:5" When user "Alice" gets the following properties of folder "/test_folder:5" using the WebDAV API @@ -84,7 +84,7 @@ Feature: create files and folder | spaces | @issue-1345 - Scenario Outline: Creating a directory which contains .part should not be possible + Scenario Outline: creating a directory which contains .part should not be possible Given using DAV path When user "Alice" creates folder "/folder.with.ext.part" using the WebDAV API Then the HTTP status code should be "400" @@ -142,7 +142,7 @@ Feature: create files and folder | spaces | - Scenario Outline: Create a file + Scenario Outline: create a file Given using DAV path When user "Alice" uploads file with content "some text" to "" using the WebDAV API Then the HTTP status code should be "201" diff --git a/tests/acceptance/features/coreApiWebdavProperties1/getQuota.feature b/tests/acceptance/features/coreApiWebdavProperties1/getQuota.feature index 621c30d01..9e11eb0fd 100644 --- a/tests/acceptance/features/coreApiWebdavProperties1/getQuota.feature +++ b/tests/acceptance/features/coreApiWebdavProperties1/getQuota.feature @@ -9,7 +9,7 @@ Feature: get quota And user "Alice" has been created with default attributes and small skeleton files - Scenario Outline: Retrieving folder quota when no quota is set + Scenario Outline: retrieving folder quota when no quota is set Given using DAV path When the administrator gives unlimited quota to user "Alice" using the provisioning API Then the HTTP status code should be "200" @@ -21,7 +21,7 @@ Feature: get quota | spaces | @smokeTest - Scenario Outline: Retrieving folder quota when quota is set + Scenario Outline: retrieving folder quota when quota is set Given using DAV path When the administrator sets the quota of user "Alice" to "10 MB" using the provisioning API Then the HTTP status code should be "200" @@ -33,7 +33,7 @@ Feature: get quota | spaces | - Scenario Outline: Retrieving folder quota of shared folder with quota when no quota is set for recipient + Scenario Outline: retrieving folder quota of shared folder with quota when no quota is set for recipient Given using DAV path And user "Brian" has been created with default attributes and small skeleton files And user "Alice" has been given unlimited quota @@ -56,7 +56,7 @@ Feature: get quota | spaces | - Scenario Outline: Retrieving folder quota when quota is set and a file was uploaded + Scenario Outline: retrieving folder quota when quota is set and a file was uploaded Given using DAV path And the quota of user "Alice" has been set to "1 KB" And user "Alice" has uploaded file "/prueba.txt" of size 93 bytes @@ -72,7 +72,7 @@ Feature: get quota | spaces | - Scenario Outline: Retrieving folder quota when quota is set and a file was received + Scenario Outline: retrieving folder quota when quota is set and a file was received Given using DAV path And user "Brian" has been created with default attributes and small skeleton files And the quota of user "Brian" has been set to "1 KB" diff --git a/tests/acceptance/features/coreApiWebdavProperties1/setFileProperties.feature b/tests/acceptance/features/coreApiWebdavProperties1/setFileProperties.feature index 75a396ded..8e864b90a 100644 --- a/tests/acceptance/features/coreApiWebdavProperties1/setFileProperties.feature +++ b/tests/acceptance/features/coreApiWebdavProperties1/setFileProperties.feature @@ -9,7 +9,7 @@ Feature: set file properties And user "Alice" has been created with default attributes and without skeleton files @smokeTest @issue-1263 - Scenario Outline: Setting custom DAV property and reading it + Scenario Outline: setting custom DAV property and reading it Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustomprop.txt" And user "Alice" has set property "very-custom-prop" with namespace "x1='http://whatever.org/ns'" of file "/testcustomprop.txt" to "veryCustomPropValue" @@ -26,7 +26,7 @@ Feature: set file properties | spaces | @issue-1297 - Scenario Outline: Setting custom complex DAV property and reading it + Scenario Outline: setting custom complex DAV property and reading it Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustomprop.txt" And user "Alice" has set property "very-custom-prop" with namespace "x1='http://whatever.org/ns'" of file "/testcustomprop.txt" to "" @@ -43,7 +43,7 @@ Feature: set file properties | spaces | @issue-1263 - Scenario Outline: Setting custom DAV property and reading it after the file is renamed + Scenario Outline: setting custom DAV property and reading it after the file is renamed Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustompropwithmove.txt" And user "Alice" has set property "very-custom-prop" with namespace "x1='http://whatever.org/ns'" of file "/testcustompropwithmove.txt" to "valueForMovetest" @@ -61,7 +61,7 @@ Feature: set file properties | spaces | @issue-1297 - Scenario Outline: Setting custom DAV property on a shared file as an owner and reading as a recipient + Scenario Outline: setting custom DAV property on a shared file as an owner and reading as a recipient Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustompropshared.txt" @@ -84,7 +84,7 @@ Feature: set file properties | spaces | @issue-1263 - Scenario Outline: Setting custom DAV property using one endpoint and reading it with other endpoint + Scenario Outline: setting custom DAV property using one endpoint and reading it with other endpoint Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testnewold.txt" And user "Alice" has set property "very-custom-prop" with namespace "x1='http://whatever.org/ns'" of file "/testnewold.txt" to "lucky" diff --git a/tests/acceptance/features/coreApiWebdavUpload1/uploadFile.feature b/tests/acceptance/features/coreApiWebdavUpload1/uploadFile.feature index 1cc07fb6b..3aef89d8c 100644 --- a/tests/acceptance/features/coreApiWebdavUpload1/uploadFile.feature +++ b/tests/acceptance/features/coreApiWebdavUpload1/uploadFile.feature @@ -167,7 +167,7 @@ Feature: upload file | spaces | @issue-1345 - Scenario Outline: Uploading file to path with extension .part should not be possible + Scenario Outline: uploading file to path with extension .part should not be possible Given using DAV path When user "Alice" uploads file "filesForUpload/textfile.txt" to "/textfile.part" using the WebDAV API Then the HTTP status code should be "400" diff --git a/tests/acceptance/features/coreApiWebdavUpload2/uploadFileUsingOldChunking.feature b/tests/acceptance/features/coreApiWebdavUpload2/uploadFileUsingOldChunking.feature index 279d0e7c0..aa9378e99 100644 --- a/tests/acceptance/features/coreApiWebdavUpload2/uploadFileUsingOldChunking.feature +++ b/tests/acceptance/features/coreApiWebdavUpload2/uploadFileUsingOldChunking.feature @@ -9,7 +9,7 @@ Feature: upload file using old chunking And user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: Upload chunked file asc + Scenario Outline: upload chunked file in ascending order Given using DAV path When user "Alice" uploads the following "3" chunks to "/myChunkedFile.txt" with old chunking and using the WebDAV API | number | content | @@ -31,7 +31,7 @@ Feature: upload file using old chunking | spaces | - Scenario Outline: Upload chunked file desc + Scenario Outline: upload chunked file in descending order Given using DAV path When user "Alice" uploads the following "3" chunks to "/myChunkedFile.txt" with old chunking and using the WebDAV API | number | content | @@ -51,7 +51,7 @@ Feature: upload file using old chunking | spaces | - Scenario Outline: Upload chunked file random + Scenario Outline: upload chunked file in random order Given using DAV path When user "Alice" uploads the following "3" chunks to "/myChunkedFile.txt" with old chunking and using the WebDAV API | number | content | @@ -71,7 +71,7 @@ Feature: upload file using old chunking | spaces | - Scenario Outline: Checking file id after a move overwrite using old chunking endpoint + Scenario Outline: checking file id after a move overwrite using old chunking endpoint Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" And user "Alice" has copied file "/textfile0.txt" to "/existingFile.txt" @@ -98,7 +98,7 @@ Feature: upload file using old chunking # This smokeTest scenario does ordinary checks for chunked upload, # without adjusting the log level. This allows it to run in test environments # where the log level has been fixed and cannot be changed. - Scenario Outline: Chunked upload files with difficult name + Scenario Outline: chunked upload files with difficult name Given using DAV path When user "Alice" uploads file "filesForUpload/textfile.txt" to "/" in 3 chunks using the WebDAV API Then the HTTP status code should be "201" @@ -121,7 +121,7 @@ Feature: upload file using old chunking | spaces | 0 | - Scenario Outline: Upload chunked file with old chunking with lengthy filenames + Scenario Outline: upload chunked file with old chunking with lengthy filenames Given using DAV path When user "Alice" uploads the following chunks to "नेपालि-file-नाम-नेपालि-file-नाम-नेपालि-file-नाम-नेपालि-file-नाम-नेपालि-file-नाम-नेपालि-file-नाम-12345678910.txt" with old chunking and using the WebDAV API | number | content | diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature index ac143ae02..06e9623a4 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature @@ -1,11 +1,14 @@ @api Feature: checksums + As a user + I want to upload resources with checksum + So that the integrity of the uploaded resources is maintained Background: Given user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: Uploading a file with checksum should work + Scenario Outline: uploading a file with checksum should work Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 5 | @@ -28,7 +31,7 @@ Feature: checksums | spaces | SHA1 8cb2237d0679ca88db6464eac60da96345513964 | - Scenario Outline: Uploading a file with checksum should return the checksum in the propfind + Scenario Outline: uploading a file with checksum should return the checksum in the propfind Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 5 | @@ -49,7 +52,7 @@ Feature: checksums | spaces | - Scenario Outline: Uploading a file with checksum should return the checksum in the download header + Scenario Outline: uploading a file with checksum should return the checksum in the download header Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 5 | @@ -70,7 +73,7 @@ Feature: checksums | spaces | - Scenario Outline: Uploading a file with incorrect checksum should not work + Scenario Outline: uploading a file with incorrect checksum should not work Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 5 | @@ -93,7 +96,7 @@ Feature: checksums | spaces | SHA1 8cb2237d0679ca88db6464eac60da96345513963 | - Scenario Outline: Uploading a chunked file with correct checksum should work + Scenario Outline: uploading a chunked file with correct checksum should work Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 10 | @@ -114,7 +117,7 @@ Feature: checksums | spaces | - Scenario Outline: Uploading a chunked file with correct checksum should return the checksum in the propfind + Scenario Outline: uploading a chunked file with correct checksum should return the checksum in the propfind Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 10 | @@ -136,7 +139,7 @@ Feature: checksums | spaces | - Scenario Outline: Uploading a chunked file with checksum should return the checksum in the download header + Scenario Outline: uploading a chunked file with checksum should return the checksum in the download header Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 10 | @@ -158,7 +161,7 @@ Feature: checksums | spaces | - Scenario Outline: Uploading second chunk of file with incorrect checksum should not work + Scenario Outline: uploading second chunk of file with incorrect checksum should not work Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 10 | @@ -179,7 +182,7 @@ Feature: checksums | spaces | - Scenario Outline: Uploading a file with correct checksum and overwriting an existing file should return the checksum for new data in the propfind + Scenario Outline: uploading a file with correct checksum and overwriting an existing file should return the checksum for new data in the propfind Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 10 | @@ -208,7 +211,7 @@ Feature: checksums | spaces | SHA1 aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d | - Scenario Outline: Uploading a file with correct checksum and overwriting an existing file with invalid checksum should not work + Scenario Outline: uploading a file with correct checksum and overwriting an existing file with invalid checksum should not work Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 10 | @@ -235,7 +238,7 @@ Feature: checksums | spaces | SHA1 aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434a | - Scenario Outline: Overwriting an existing file with new data and checksum should return the checksum of new data in the propfind + Scenario Outline: overwriting an existing file with new data and checksum should return the checksum of new data in the propfind Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 5 | @@ -264,7 +267,7 @@ Feature: checksums | spaces | SHA1 aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d | - Scenario Outline: Overwriting an existing file with new data and invalid checksum should not work + Scenario Outline: overwriting an existing file with new data and invalid checksum should not work Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 5 | diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/creationWithUploadExtension.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/creationWithUploadExtension.feature index 6bcc82791..65cabe6e2 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/creationWithUploadExtension.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/creationWithUploadExtension.feature @@ -1,5 +1,8 @@ @api Feature: tests of the creation extension see https://tus.io/protocols/resumable-upload.html#creation-with-upload + As a user + I want to be able to include parts of upload while creating resources + So that I can provide basic information about the resources to the server Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelCreationExtension.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelCreationExtension.feature index 78b9d359d..3ccafad69 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelCreationExtension.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelCreationExtension.feature @@ -1,5 +1,8 @@ @api Feature: low level tests of the creation extension see https://tus.io/protocols/resumable-upload.html#creation + As a user + I want to able to create resources + So that I can manage my resources Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature index b2c9b2a0b..fb015b2ce 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature @@ -1,5 +1,8 @@ @api Feature: low level tests for upload of chunks + As a user + I want to be able to upload resources in chunks + So that I can manage my resources Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature index b19ce14b9..8f036896f 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature @@ -1,5 +1,8 @@ @api Feature: OPTIONS request + As a user + I want to check OPTIONS request + So that I can get information about communication options for target resource Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFile.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFile.feature index 6afc36a05..77cc56b3d 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFile.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFile.feature @@ -75,7 +75,7 @@ Feature: upload file | spaces | /?fi=le&%#2 . txt | # %ab ab?=ed | - Scenario Outline: Upload chunked file with TUS + Scenario Outline: upload chunked file with TUS Given using DAV path When user "Alice" uploads file with content "uploaded content" in 3 chunks to "/myChunkedFile.txt" using the TUS protocol on the WebDAV API Then the content of file "/myChunkedFile.txt" for user "Alice" should be "uploaded content" @@ -90,7 +90,7 @@ Feature: upload file | spaces | - Scenario Outline: Upload 1 byte chunks with TUS + Scenario Outline: upload 1 byte chunks with TUS Given using DAV path When user "Alice" uploads file with content "0123456789" in 10 chunks to "/myChunkedFile.txt" using the TUS protocol on the WebDAV API Then the content of file "/myChunkedFile.txt" for user "Alice" should be "0123456789" @@ -105,7 +105,7 @@ Feature: upload file | spaces | - Scenario Outline: Upload to overwriting a file + Scenario Outline: upload to overwriting a file Given using DAV path And user "Alice" has uploaded file with content "original content" to "textfile.txt" When user "Alice" uploads file with content "overwritten content" to "textfile.txt" using the TUS protocol on the WebDAV API diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToMoveFolder.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToMoveFolder.feature index 4b14d8cac..16a447afc 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToMoveFolder.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToMoveFolder.feature @@ -8,7 +8,7 @@ Feature: move folders Given user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: Uploading file into a moved folder + Scenario Outline: uploading file into a moved folder Given using DAV path And user "Alice" has created folder "/test" And user "Alice" has created folder "/test-moved" diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature index b6ff91fe7..95fc18bdb 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature @@ -1,6 +1,8 @@ -@api - +@api Feature: upload file to shared folder + As a user + I want to upload files on a shared folder + So that other user with access on the shared folder can access the resource Background: Given these users have been created with default attributes and without skeleton files: @@ -9,7 +11,7 @@ Feature: upload file to shared folder | Brian | - Scenario Outline: Uploading file to a received share folder + Scenario Outline: uploading file to a received share folder Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" @@ -23,7 +25,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Uploading file to a user read/write share folder works + Scenario Outline: uploading file to a user read/write share folder works Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "change" @@ -37,7 +39,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Uploading a file into a group share as share receiver + Scenario Outline: uploading a file into a group share as share receiver Given using DAV path And group "grp1" has been created And user "Brian" has been added to group "grp1" @@ -53,7 +55,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Overwrite file to a received share folder + Scenario Outline: overwrite file to a received share folder Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has uploaded file with content "original content" to "/FOLDER/textfile.txt" @@ -81,7 +83,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Upload a file to shared folder with checksum should return the checksum in the propfind for sharee + Scenario Outline: upload a file to shared folder with checksum should return the checksum in the propfind for sharee Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" @@ -100,7 +102,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Upload a file to shared folder with checksum should return the checksum in the download header for sharee + Scenario Outline: upload a file to shared folder with checksum should return the checksum in the download header for sharee Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" @@ -119,7 +121,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharer shares a file with correct checksum should return the checksum in the propfind for sharee + Scenario Outline: sharer shares a file with correct checksum should return the checksum in the propfind for sharee Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 5 | @@ -137,7 +139,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharer shares a file with correct checksum should return the checksum in the download header for sharee + Scenario Outline: sharer shares a file with correct checksum should return the checksum in the download header for sharee Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 5 | @@ -155,7 +157,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharee uploads a file to a received share folder with correct checksum + Scenario Outline: sharee uploads a file to a received share folder with correct checksum Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" @@ -175,7 +177,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharee uploads a file to a received share folder with wrong checksum should not work + Scenario Outline: sharee uploads a file to a received share folder with wrong checksum should not work Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" @@ -194,7 +196,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharer uploads a file to shared folder with wrong correct checksum should not work + Scenario Outline: sharer uploads a file to shared folder with wrong correct checksum should not work Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" @@ -213,7 +215,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharer uploads a chunked file with correct checksum and share it with sharee should work + Scenario Outline: sharer uploads a chunked file with correct checksum and share it with sharee should work Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 10 | @@ -231,7 +233,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharee uploads a chunked file with correct checksum to a received share folder should work + Scenario Outline: sharee uploads a chunked file with correct checksum to a received share folder should work Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" @@ -252,7 +254,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharer uploads a file with checksum and as a sharee overwrites the shared file with new data and correct checksum + Scenario Outline: sharer uploads a file with checksum and as a sharee overwrites the shared file with new data and correct checksum Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 16 | @@ -273,7 +275,7 @@ Feature: upload file to shared folder | new | - Scenario Outline: Sharer uploads a file with checksum and as a sharee overwrites the shared file with new data and invalid checksum + Scenario Outline: sharer uploads a file with checksum and as a sharee overwrites the shared file with new data and invalid checksum Given using DAV path And user "Alice" has created a new TUS resource on the WebDAV API with these headers: | Upload-Length | 16 |