diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiShareOperations-gettingShares.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiShareOperations-gettingShares.feature index 4a35971b4..2007a366a 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiShareOperations-gettingShares.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiShareOperations-gettingShares.feature @@ -2,14 +2,15 @@ Feature: sharing Background: - Given user "Alice" has been created with default attributes and without skeleton files - And user "Brian" has been created with default attributes and without skeleton files + Given these users have been created with default attributes and skeleton files: + | username | + | Alice | + | Brian | @issue-ocis-reva-374 # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: Get a share with a user that didn't receive the share - Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" - And using OCS API version "" + Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files And user "Alice" has shared file "textfile0.txt" with user "Brian" When user "Carol" gets the info of the last share using the sharing API @@ -24,9 +25,7 @@ Feature: sharing @issue-ocis-reva-372 # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: getting all the shares inside the folder - Given user "Alice" has created folder "/PARENT" - And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt" - And using OCS API version "" + Given using OCS API version "" And user "Alice" has shared file "PARENT/parent.txt" with user "Brian" When user "Alice" gets all the shares inside the folder "PARENT/parent.txt" using the sharing API Then the OCS status code should be "" diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-updatePublicLinkShare.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-updatePublicLinkShare.feature index fcba331e4..e14ed5e6a 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-updatePublicLinkShare.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-updatePublicLinkShare.feature @@ -3,8 +3,7 @@ Feature: update a public link share Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files - And user "Alice" has created folder "/FOLDER" + And user "Alice" has been created with default attributes and skeleton files @issue-ocis-reva-243 @issue-ocis-reva-349 @issue-37653 # after fixing all issues delete this Scenario and use the one from oC10 core diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-uploadToPublicLinkShare.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-uploadToPublicLinkShare.feature index 9e00ee813..320ce525b 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-uploadToPublicLinkShare.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-uploadToPublicLinkShare.feature @@ -3,8 +3,7 @@ Feature: upload to a public link share Background: - Given user "Alice" has been created with default attributes and without skeleton files - And user "Alice" has created folder "/FOLDER" + Given user "Alice" has been created with default attributes and skeleton files @issue-ocis-reva-290 # after fixing all issues delete this Scenario and use the one from oC10 core diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiShareUpdate-updateShare.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiShareUpdate-updateShare.feature index 33b9cfc40..38b85dbbe 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiShareUpdate-updateShare.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiShareUpdate-updateShare.feature @@ -5,7 +5,7 @@ Feature: sharing Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @skipOnOcis-EOS-Storage @toFixOnOCIS @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage + @skipOnOcis-EOS-Storage @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario: Share ownership change after moving a shared file to another share Given these users have been created with default attributes and without skeleton files: @@ -43,7 +43,7 @@ Feature: sharing And as "Alice" folder "/Alice-folder/folder2" should exist And as "Carol" folder "/Carol-folder/folder2" should not exist - @skipOnOcis-OC-Storage @toFixOnOCIS @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage + @skipOnOcis-OC-Storage @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage # same as oC10 core Scenario but without displayname_owner because EOS does not report it # after fixing all issues delete this Scenario and use the one from oC10 core Scenario: Share ownership change after moving a shared file to another share @@ -74,7 +74,7 @@ Feature: sharing And as "Alice" folder "/Alice-folder/folder2" should exist And as "Carol" folder "/Carol-folder/folder2" should not exist - @toFixOnOCIS @toFixOnOcV10 @issue-ocis-reva-350 @issue-ocis-reva-352 @issue-37653 + @issue-ocis-reva-350 @issue-ocis-reva-352 @issue-37653 # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: API responds with a full set of parameters when owner changes the permission of a share Given using OCS API version "" diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiTrashbin-trashbinDelete.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiTrashbin-trashbinDelete.feature index 419083598..ce45db8a0 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiTrashbin-trashbinDelete.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiTrashbin-trashbinDelete.feature @@ -19,7 +19,6 @@ Feature: files and folders can be deleted from the trashbin @issue-product-179 Scenario Outline: Trashbin cannot be emptied # after fixing all issues delete this Scenario and use the one from oC10 core - # because of @issue-product-178 we cannot perform this test using new dav, so only old dav is being used Given user "Alice" has uploaded file with content "file with comma" to "sample,0.txt" And user "Alice" has uploaded file with content "file with comma" to "sample,1.txt" And using DAV path diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove1-moveFolderToBlacklistedName.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove1-moveFolderToBlacklistedName.feature index b07ff20fe..3d1289d8b 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove1-moveFolderToBlacklistedName.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove1-moveFolderToBlacklistedName.feature @@ -8,7 +8,7 @@ Feature: users cannot move (rename) a folder to a blacklisted name Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @issue-ocis-reva-211 @skipOnOcis-EOS-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-269 + @issue-ocis-reva-211 @skipOnOcis-EOS-Storage @issue-ocis-reva-269 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: Renaming a folder to a name that is banned by default is allowed Given using DAV path diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature index 10eea11ec..caada530f 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature @@ -7,13 +7,13 @@ Feature: move (rename) file Background: Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - And user "Alice" has uploaded file with content "some welcome data" to "/welcome.txt" + And user "Alice" has uploaded file with content "text file 0" to "/textfile0.txt" @issue-ocis-reva-211 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: rename a file into an invalid filename Given using DAV path - When user "Alice" moves file "/welcome.txt" to "/a\\a" using the WebDAV API + When user "Alice" moves file "/textfile0.txt" to "/a\\a" using the WebDAV API Then the HTTP status code should be "201" And as "Alice" file "/a\\a" should exist Examples: @@ -25,9 +25,9 @@ Feature: move (rename) file # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: Renaming a file to a path with extension .part is possible Given using DAV path - When user "Alice" moves file "/welcome.txt" to "/welcome.part" using the WebDAV API + When user "Alice" moves file "/textfile0.txt" to "/textfile0.part" using the WebDAV API Then the HTTP status code should be "201" - And as "Alice" file "/welcome.part" should exist + And as "Alice" file "/textfile0.part" should exist Examples: | dav_version | | old | diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFileToBlacklistedName.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFileToBlacklistedName.feature index 00b4763be..288306217 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFileToBlacklistedName.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFileToBlacklistedName.feature @@ -7,13 +7,13 @@ Feature: users cannot move (rename) a file to a blacklisted name Background: Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - And user "Alice" has uploaded file with content "some welcome data" to "/welcome.txt" + And user "Alice" has uploaded file with content "text file 0" to "/textfile0.txt" @issue-ocis-reva-211 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: rename a file to a filename that is banned by default Given using DAV path - When user "Alice" moves file "/welcome.txt" to "/.htaccess" using the WebDAV API + When user "Alice" moves file "/textfile0.txt" to "/.htaccess" using the WebDAV API Then the HTTP status code should be "201" And as "Alice" file "/.htaccess" should exist Examples: diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature index 5ce403a66..f98c1a400 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature @@ -8,7 +8,7 @@ Feature: set file properties Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-276 + @skipOnOcis-OC-Storage @issue-ocis-reva-276 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: Setting custom DAV property Given using DAV path diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature index f1edbebc8..67d0594c5 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature @@ -17,10 +17,10 @@ Feature: get file properties Then the properties response should contain an etag And the value of the item "//d:response/d:href" in the response to user "Alice" should match "/remote\.php\//" Examples: - | dav_version | file_name | expected_href | - | old | /C++ file.cpp | webdav\/C\+\+%20file\.cpp | - | old | /file #2.txt | webdav\/file%20%232\.txt | - | old | /file &2.txt | webdav\/file%20&2\.txt | + | dav_version | file_name | expected_href | + | old | /C++ file.cpp | webdav\/C\+\+%20file\.cpp | + | old | /file #2.txt | webdav\/file%20%232\.txt | + | old | /file &2.txt | webdav\/file%20&2\.txt | | new | /C++ file.cpp | dav\/files\/%username%\/C\+\+%20file\.cpp | | new | /file #2.txt | dav\/files\/%username%\/file%20%232\.txt | | new | /file &2.txt | dav\/files\/%username%\/file%20&2\.txt | @@ -45,11 +45,11 @@ Feature: get file properties When user "Alice" uploads file with content "uploaded content" to "" using the WebDAV API Then the HTTP status code should be "500" Examples: - | dav_version | file_name | - | old | /file ?2.txt | - | new | /file ?2.txt | + | dav_version | file_name | + | old | /file ?2.txt | + | new | /file ?2.txt | - @issue-ocis-reva-214 @skipOnOcis-OCIS-Storage @issue-ocis-reva-471 + @issue-ocis-reva-214 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: Do a PROPFIND of various folder names Given using DAV path @@ -61,21 +61,21 @@ Feature: get file properties And the value of the item "//d:response[2]/d:href" in the response to user "Alice" should match "/remote\.php\/\/file1.txt/" And the value of the item "//d:response[3]/d:href" in the response to user "Alice" should match "/remote\.php\/\/file2.txt/" Examples: - | dav_version | folder_name | expected_href | - | old | /upload | webdav\/upload | - | old | /strängé folder | webdav\/str%C3%A4ng%C3%A9%20folder | - | old | /C++ folder | webdav\/C\+\+%20folder | - | old | /नेपाली | webdav\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 | - | old | /folder #2.txt | webdav\/folder%20%232\.txt | - | old | /folder &2.txt | webdav\/folder%20&2\.txt | + | dav_version | folder_name | expected_href | + | old | /upload | webdav\/upload | + | old | /strängé folder | webdav\/str%C3%A4ng%C3%A9%20folder | + | old | /C++ folder | webdav\/C\+\+%20folder | + | old | /नेपाली | webdav\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 | + | old | /folder #2.txt | webdav\/folder%20%232\.txt | + | old | /folder &2.txt | webdav\/folder%20&2\.txt | | new | /upload | dav\/files\/%username%\/upload | | new | /strängé folder | dav\/files\/%username%\/str%C3%A4ng%C3%A9%20folder | - | new | /C++ folder | dav\/files\/%username%\/C\+\+%20folder | + | new | /C++ folder | dav\/files\/%username%\/C\+\+%20folder | | new | /नेपाली | dav\/files\/%username%\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 | | new | /folder #2.txt | dav\/files\/%username%\/folder%20%232\.txt | | new | /folder &2.txt | dav\/files\/%username%\/folder%20&2\.txt | - @issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage @issue-ocis-reva-471 + @issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: Do a PROPFIND of various folder names Given using DAV path @@ -87,11 +87,11 @@ Feature: get file properties And the value of the item "//d:response[2]/d:href" in the response to user "Alice" should match "/remote\.php\/\/file1.txt/" And the value of the item "//d:response[3]/d:href" in the response to user "Alice" should match "/remote\.php\/\/file2.txt/" Examples: - | dav_version | folder_name | expected_href | - | old | /folder ?2.txt | webdav\/folder%20%3F2\.txt | - | new | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt | + | dav_version | folder_name | expected_href | + | old | /folder ?2.txt | webdav\/folder%20%3F2\.txt | + | new | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt | - @skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-265 + @skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: Do a PROPFIND of various folder names Given using DAV path diff --git a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature index a4b7ba65f..e570c2acd 100644 --- a/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature +++ b/ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature @@ -8,7 +8,7 @@ Feature: upload file Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-265 + @skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: upload a file and check download content Given using DAV path @@ -19,7 +19,7 @@ Feature: upload file | old | "file ?2.txt" | | new | "file ?2.txt" | - @skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-product-127 + @skipOnOcis-OC-Storage @issue-product-127 @skipOnOcis-OCIS-Storage # this scenario passes/fails intermittently on OC storage, so do not run it in CI # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: uploading a file inside a folder changes its etag