@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-310 Feature: copying from public link share Background: Given user "Alice" has been created with default attributes and without skeleton files 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 Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt" And user "Alice" has created folder "/PARENT/new-folder" And user "Alice" has uploaded file with content "some data 1" to "/PARENT/new-folder/testfile1.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 "/new-folder" using the new public WebDAV API Then the HTTP status code should be "204" 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"