diff --git a/tests/acceptance/features/apiBugDemonstration/apiSharePublicLink2-copyFromPublicLink.feature b/tests/acceptance/features/apiBugDemonstration/apiSharePublicLink2-copyFromPublicLink.feature index c364374c8..ff889194a 100644 --- a/tests/acceptance/features/apiBugDemonstration/apiSharePublicLink2-copyFromPublicLink.feature +++ b/tests/acceptance/features/apiBugDemonstration/apiSharePublicLink2-copyFromPublicLink.feature @@ -6,22 +6,6 @@ Feature: copying from public link share And user "Alice" has created folder "/PARENT" And the administrator has enabled DAV tech_preview - @issue-ocis-reva-373 @issue-core-37683 @skipOnOcis-OCIS-Storage - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario: Copy folder within a public link folder to the same folder name as an already existing file - Given user "Alice" has created folder "/PARENT/testFolder" - And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt" - And user "Alice" has uploaded file with content "some data 1" to "/PARENT/copy1.txt" - And user "Alice" has created a public link share with settings - | path | /PARENT | - | permissions | read,update,create,delete | - When the public copies folder "/testFolder" to "/copy1.txt" using the new public WebDAV API - Then the HTTP status code should be "204" - And as "Alice" folder "/PARENT/testFolder" should exist - And as "Alice" file "/PARENT/copy1.txt" should exist - And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data" - And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data 1" - @issue-ocis-reva-373 @issue-core-37683 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario: Copy file within a public link folder to a file with name same as an existing folder @@ -36,32 +20,3 @@ Feature: copying from public link share And as "Alice" file "/PARENT/testfile.txt" should exist And as "Alice" file "/PARENT/new-folder" should exist And the content of file "/PARENT/testfile.txt" for user "Alice" should be "some data" - - @issue-ocis-reva-368 @skipOnOcis-OCIS-Storage - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: Copy file within a public link folder to a file with unusual destination names - Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt" - And user "Alice" has created a public link share with settings - | path | /PARENT | - | permissions | read,update,create,delete | - When the public copies file "/testfile.txt" to "/" using the new public WebDAV API - Then the HTTP status code should be "204" - And as "Alice" file "/PARENT/" should exist - And the content of file "/PARENT/" for user "Alice" should be "some data" - Examples: - | destination-file-name | - | testfile.txt | - | | - - @issue-ocis-reva-368 @skipOnOcis-OCIS-Storage - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario: Copy folder within a public link folder to a folder with unusual destination names - Given user "Alice" has created folder "/PARENT/testFolder" - And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt" - And user "Alice" has created a public link share with settings - | path | /PARENT | - | permissions | read,update,create,delete | - When the public copies folder "/testFolder" to "/testFolder" using the new public WebDAV API - Then the HTTP status code should be "204" - And as "Alice" folder "/PARENT/testFolder" should exist - And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data" diff --git a/tests/acceptance/features/apiBugDemonstration/apiWebdavMove1-moveFolder.feature b/tests/acceptance/features/apiBugDemonstration/apiWebdavMove1-moveFolder.feature index 6b5bc6a79..c8e360888 100644 --- a/tests/acceptance/features/apiBugDemonstration/apiWebdavMove1-moveFolder.feature +++ b/tests/acceptance/features/apiBugDemonstration/apiWebdavMove1-moveFolder.feature @@ -7,39 +7,3 @@ Feature: move (rename) folder Background: Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - - @issue-ocis-reva-211 - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: Renaming a folder to a backslash is allowed - Given using DAV path - And user "Alice" has created folder "/testshare" - When user "Alice" moves folder "/testshare" to "\" using the WebDAV API - Then the HTTP status code should be "201" or "500" - Examples: - | dav_version | - | old | - | new | - - @issue-ocis-reva-211 - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: Renaming a folder beginning with a backslash is allowed - Given using DAV path - And user "Alice" has created folder "/testshare" - When user "Alice" moves folder "/testshare" to "\testshare" using the WebDAV API - Then the HTTP status code should be "201" or "500" - Examples: - | dav_version | - | old | - | new | - - @issue-ocis-reva-211 - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: Renaming a folder including a backslash encoded is allowed - Given using DAV path - And user "Alice" has created folder "/testshare" - When user "Alice" moves folder "/testshare" to "/hola\hola" using the WebDAV API - Then the HTTP status code should be "201" or "500" - Examples: - | dav_version | - | old | - | new | diff --git a/tests/acceptance/features/apiBugDemonstration/apiWebdavMove2-moveFile.feature b/tests/acceptance/features/apiBugDemonstration/apiWebdavMove2-moveFile.feature index 38118528b..6d0566601 100644 --- a/tests/acceptance/features/apiBugDemonstration/apiWebdavMove2-moveFile.feature +++ b/tests/acceptance/features/apiBugDemonstration/apiWebdavMove2-moveFile.feature @@ -9,18 +9,6 @@ Feature: move (rename) file And user "Alice" has been created with default attributes and without skeleton files 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 "/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: - | dav_version | - | old | - | new | - @issue-ocis-reva-211 @skipOnOcis-OCIS-Storage # 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 @@ -31,4 +19,4 @@ Feature: move (rename) file Examples: | dav_version | | old | - | new | \ No newline at end of file + | new | diff --git a/tests/acceptance/features/apiBugDemonstration/apiWebdavProperties2-getFileProperties.feature b/tests/acceptance/features/apiBugDemonstration/apiWebdavProperties2-getFileProperties.feature index e7e303282..d64b0d4ca 100644 --- a/tests/acceptance/features/apiBugDemonstration/apiWebdavProperties2-getFileProperties.feature +++ b/tests/acceptance/features/apiBugDemonstration/apiWebdavProperties2-getFileProperties.feature @@ -51,13 +51,3 @@ Feature: get file properties | dav_version | | old | | new | - - @issue-ocis-reva-163 - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: Do a PROPFIND to a non-existing URL - And user "Alice" requests "" with "PROPFIND" using basic auth - Then the body of the response should be empty - Examples: - | url | - | /remote.php/dav/files/does-not-exist | - | /remote.php/dav/does-not-exist |