diff --git a/tests/acceptance/features/apiSpaces/listSpaces.feature b/tests/acceptance/features/apiSpaces/listSpaces.feature index bf80f38ac..3d4307420 100644 --- a/tests/acceptance/features/apiSpaces/listSpaces.feature +++ b/tests/acceptance/features/apiSpaces/listSpaces.feature @@ -29,11 +29,11 @@ Feature: List and create spaces And user "Brian" has created folder "folder" And user "Brian" has shared folder "folder" with user "Alice" with permissions "31" And user "Alice" has accepted share "/folder" offered by user "Brian" - Then the user "Alice" should have a space called "Shares Jail" with these key and value pairs: + Then the user "Alice" should have a space called "Shares" with these key and value pairs: | key | value | | driveType | virtual | | id | %space_id% | - | name | Shares Jail | + | name | Shares | When user "Alice" lists all available spaces via the GraphApi with query "$filter=driveType eq 'personal'" Then the HTTP status code should be "200" And the json responded should contain a space "Alice Hansen" with these key and value pairs: @@ -43,7 +43,7 @@ Feature: List and create spaces | name | Alice Hansen | | quota@@@state | normal | | root@@@webDavUrl | %base_url%/dav/spaces/%space_id% | - And the json responded should not contain a space with name "Shares Jail" + And the json responded should not contain a space with name "Shares" And the json responded should only contain spaces of type "personal" diff --git a/tests/acceptance/features/apiSpaces/search.feature b/tests/acceptance/features/apiSpaces/search.feature index 3a6367bf3..23b338ecb 100644 --- a/tests/acceptance/features/apiSpaces/search.feature +++ b/tests/acceptance/features/apiSpaces/search.feature @@ -1,6 +1,6 @@ @api @skipOnOcV10 Feature: Search - It is possible to search files in the shares jail and the project space + It is possible to search files in the Shares and the project space Note - this feature is run in CI with ACCOUNTS_HASH_DIFFICULTY set to the default for production See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 @@ -40,7 +40,7 @@ Feature: Search | /folderMain/SubFolder1/subFOLDER2/insideTheFolder.txt | - Scenario: Brian can find data from the shares jail + Scenario: Brian can find data from the Shares Given user "Alice" shares the following entity "folderMain" inside of space "find data" with user "Brian" with role "viewer" And user "Brian" has accepted share "/folderMain" offered by user "Alice" When user "Brian" searches for "folder" using the WebDAV API @@ -113,7 +113,7 @@ Feature: Search | folderMain | find data | - Scenario Outline: search result for shares jail contains resource parentID + Scenario Outline: search result for Shares contains resource parentID Given user "Alice" shares the following entity "folderMain" inside of space "find data" with user "Brian" with role "viewer" And user "Brian" has accepted share "/folderMain" offered by user "Alice" When user "Brian" searches for "" using the WebDAV API diff --git a/tests/acceptance/features/apiSpacesShares/changingFilesShare.feature b/tests/acceptance/features/apiSpacesShares/changingFilesShare.feature index b609ab4d5..d9b918ba2 100644 --- a/tests/acceptance/features/apiSpacesShares/changingFilesShare.feature +++ b/tests/acceptance/features/apiSpacesShares/changingFilesShare.feature @@ -19,11 +19,11 @@ Feature: And user "Brian" has shared folder "/PARENT" with user "Carol" And user "Carol" has accepted share "/PARENT" offered by user "Alice" And user "Carol" has accepted share "/PARENT" offered by user "Brian" - When user "Carol" moves file "PARENT/from_alice.txt" to "PARENT (1)/from_alice.txt" in space "Shares Jail" using the WebDAV API + When user "Carol" moves file "PARENT/from_alice.txt" to "PARENT (1)/from_alice.txt" in space "Shares" using the WebDAV API Then the HTTP status code should be "201" - And for user "Carol" folder "PARENT" of the space "Shares Jail" should not contain these entries: + And for user "Carol" folder "PARENT" of the space "Shares" should not contain these entries: | from_alice.txt | - And for user "Carol" folder "PARENT (1)" of the space "Shares Jail" should contain these entries: + And for user "Carol" folder "PARENT (1)" of the space "Shares" should contain these entries: | from_alice.txt | @@ -32,15 +32,15 @@ Feature: And user "Alice" has uploaded file with content "old content version 2" to "/textfile1.txt" And user "Alice" has shared file "/textfile1.txt" with user "Brian" And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice" - When user "Brian" uploads a file inside space "Shares Jail" with content "this is a new content" to "textfile1.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "this is a new content" to "textfile1.txt" using the WebDAV API Then the HTTP status code should be "204" - And for user "Brian" the space "Shares Jail" should contain these entries: + And for user "Brian" the space "Shares" should contain these entries: | textfile1.txt | - And for user "Brian" the content of the file "/textfile1.txt" of the space "Shares Jail" should be "this is a new content" + And for user "Brian" the content of the file "/textfile1.txt" of the space "Shares" should be "this is a new content" And for user "Alice" the content of the file "/textfile1.txt" of the space "Personal" should be "this is a new content" When user "Alice" downloads version of the file "/textfile1.txt" with the index "2" of the space "Personal" using the WebDAV API Then the HTTP status code should be "200" And the downloaded content should be "old content version 1" - When user "Brian" downloads version of the file "/textfile1.txt" with the index "1" of the space "Shares Jail" using the WebDAV API + When user "Brian" downloads version of the file "/textfile1.txt" with the index "1" of the space "Shares" using the WebDAV API Then the HTTP status code should be "200" And the downloaded content should be "old content version 2" diff --git a/tests/acceptance/features/apiSpacesShares/checksum.feature b/tests/acceptance/features/apiSpacesShares/checksum.feature index 08e68f0ab..9115b6893 100644 --- a/tests/acceptance/features/apiSpacesShares/checksum.feature +++ b/tests/acceptance/features/apiSpacesShares/checksum.feature @@ -13,7 +13,7 @@ Feature: checksums Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian" And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice" - When user "Brian" requests the checksum of file "/myChecksumFile.txt" in space "Shares Jail" via propfind using the WebDAV API + When user "Brian" requests the checksum of file "/myChecksumFile.txt" in space "Shares" via propfind using the WebDAV API Then the HTTP status code should be "207" And the webdav checksum should match "SHA1:3ee962b839762adb0ad8ba6023a4690be478de6f MD5:d70b40f177b14b470d1756a3c12b963a ADLER32:8ae90960" @@ -22,6 +22,6 @@ Feature: checksums Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian" And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice" - When user "Brian" uploads file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/myChecksumFile.txt" in space "Shares Jail" using the WebDAV API + When user "Brian" uploads file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/myChecksumFile.txt" in space "Shares" using the WebDAV API Then the HTTP status code should be "204" And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a" diff --git a/tests/acceptance/features/apiSpacesShares/copySpaces.feature b/tests/acceptance/features/apiSpacesShares/copySpaces.feature index 5b388fd5d..e49484b59 100644 --- a/tests/acceptance/features/apiSpacesShares/copySpaces.feature +++ b/tests/acceptance/features/apiSpacesShares/copySpaces.feature @@ -95,7 +95,7 @@ Feature: copy file | viewer | - Scenario Outline: User copies a file from space project with different role to space shares jail with editor role + Scenario Outline: User copies a file from space project with different role to space Shares with editor role Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has created folder "/testshare" @@ -103,11 +103,11 @@ Feature: copy file And user "Brian" has shared a space "Project" to user "Alice" with role "" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "31" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies file "/project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "201" - And for user "Alice" folder "testshare" of the space "Shares Jail" should contain these files: + And for user "Alice" folder "testshare" of the space "Shares" should contain these files: | /project.txt | - And for user "Alice" the content of the file "/testshare/project.txt" of the space "Shares Jail" should be "Project content" + And for user "Alice" the content of the file "/testshare/project.txt" of the space "Shares" should be "Project content" Examples: | role | | manager | @@ -115,7 +115,7 @@ Feature: copy file | viewer | - Scenario Outline: User copies a file from space project with different role to shares jail with viewer role + Scenario Outline: User copies a file from space project with different role to Shares with viewer role Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has created folder "/testshare" @@ -123,9 +123,9 @@ Feature: copy file And user "Brian" has shared a space "Project" to user "Alice" with role "" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "17" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies file "/project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "403" - And for user "Alice" the space "Shares Jail" should not contain these entries: + And for user "Alice" the space "Shares" should not contain these entries: | /testshare/project.txt | Examples: | role | @@ -161,36 +161,36 @@ Feature: copy file | /personal.txt | - Scenario: User copies a file from space personal to space shares jail with role editor + Scenario: User copies a file from space personal to space Shares with role editor Given user "Brian" has created folder "/testshare" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "31" And user "Alice" has accepted share "/testshare" offered by user "Brian" And user "Alice" has uploaded file with content "personal content" to "personal.txt" - When user "Alice" copies file "/personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "201" - And for user "Alice" folder "testshare" of the space "Shares Jail" should contain these files: + And for user "Alice" folder "testshare" of the space "Shares" should contain these files: | personal.txt | - And for user "Alice" the content of the file "/testshare/personal.txt" of the space "Shares Jail" should be "personal content" + And for user "Alice" the content of the file "/testshare/personal.txt" of the space "Shares" should be "personal content" - Scenario: User copies a file from space personal to space shares jail with role viewer + Scenario: User copies a file from space personal to space Shares with role viewer Given user "Brian" has created folder "/testshare" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "17" And user "Alice" has accepted share "/testshare" offered by user "Brian" And user "Alice" has uploaded file with content "personal content" to "/personal.txt" - When user "Alice" copies file "/personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "403" - And for user "Alice" the space "Shares Jail" should not contain these entries: + And for user "Alice" the space "Shares" should not contain these entries: | /testshare/personal.txt | - Scenario Outline: User copies a file from space shares jail with different role to space personal + Scenario Outline: User copies a file from space Shares with different role to space personal Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies file "/testshare/testshare.txt" from space "Shares Jail" to "/testshare.txt" inside space "Personal" using the WebDAV API + When user "Alice" copies file "/testshare/testshare.txt" from space "Shares" to "/testshare.txt" inside space "Personal" using the WebDAV API Then the HTTP status code should be "201" And for user "Alice" the space "Personal" should contain these entries: | /testshare.txt | @@ -201,7 +201,7 @@ Feature: copy file | 17 | - Scenario Outline: User copies a file from space shares jail with different role to space project with different role + Scenario Outline: User copies a file from space Shares with different role to space project with different role Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has shared a space "Project" to user "Alice" with role "" @@ -209,7 +209,7 @@ Feature: copy file And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies file "/testshare/testshare.txt" from space "Shares Jail" to "/testshare.txt" inside space "Project" using the WebDAV API + When user "Alice" copies file "/testshare/testshare.txt" from space "Shares" to "/testshare.txt" inside space "Project" using the WebDAV API Then the HTTP status code should be "201" And for user "Alice" the space "Project" should contain these entries: | /testshare.txt | @@ -222,7 +222,7 @@ Feature: copy file | editor | 17 | - Scenario Outline: User copies a file from space shares jail with different role to space project with role viewer + Scenario Outline: User copies a file from space Shares with different role to space project with role viewer Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has shared a space "Project" to user "Alice" with role "viewer" @@ -230,7 +230,7 @@ Feature: copy file And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies file "/testshare/testshare.txt" from space "Shares Jail" to "/testshare.txt" inside space "Project" using the WebDAV API + When user "Alice" copies file "/testshare/testshare.txt" from space "Shares" to "/testshare.txt" inside space "Project" using the WebDAV API Then the HTTP status code should be "403" And for user "Alice" the space "Project" should not contain these entries: | /testshare.txt | @@ -240,7 +240,7 @@ Feature: copy file | 17 | - Scenario Outline: User copies a file from space shares jail with different role to space shares jail with role editor + Scenario Outline: User copies a file from space Shares with different role to space Shares with role editor Given user "Brian" has created folder "/testshare1" And user "Brian" has created folder "/testshare2" And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt" @@ -248,13 +248,13 @@ Feature: copy file And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "31" And user "Alice" has accepted share "/testshare1" offered by user "Brian" And user "Alice" has accepted share "/testshare2" offered by user "Brian" - When user "Alice" copies file "/testshare1/testshare1.txt" from space "Shares Jail" to "/testshare2/testshare1.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "201" - And for user "Alice" folder "testshare2" of the space "Shares Jail" should contain these files: + And for user "Alice" folder "testshare2" of the space "Shares" should contain these files: | /testshare1.txt | And for user "Brian" the space "Personal" should contain these entries: | /testshare2/testshare1.txt | - And for user "Alice" the content of the file "/testshare2/testshare1.txt" of the space "Shares Jail" should be "testshare1 content" + And for user "Alice" the content of the file "/testshare2/testshare1.txt" of the space "Shares" should be "testshare1 content" And for user "Brian" the content of the file "/testshare1/testshare1.txt" of the space "Personal" should be "testshare1 content" Examples: | permissions | @@ -262,7 +262,7 @@ Feature: copy file | 17 | - Scenario Outline: User copies a file from space shares jail with different role to space shares jail with role editor + Scenario Outline: User copies a file from space Shares with different role to space Shares with role editor Given user "Brian" has created folder "/testshare1" And user "Brian" has created folder "/testshare2" And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt" @@ -270,9 +270,9 @@ Feature: copy file And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "17" And user "Alice" has accepted share "/testshare1" offered by user "Brian" And user "Alice" has accepted share "/testshare2" offered by user "Brian" - When user "Alice" copies file "/testshare1/testshare1.txt" from space "Shares Jail" to "/testshare2/testshare1.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "403" - And for user "Alice" the space "Shares Jail" should not contain these entries: + And for user "Alice" the space "Shares" should not contain these entries: | /testshare2/testshare1.txt | And for user "Brian" the space "Personal" should not contain these entries: | /testshare2/testshare1.txt | @@ -341,7 +341,7 @@ Feature: copy file | viewer | - Scenario Outline: User copies a folder from space project with different role to space shares jail with different role + Scenario Outline: User copies a folder from space project with different role to space Shares with different role Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has created folder "/testshare" @@ -350,9 +350,9 @@ Feature: copy file And user "Brian" has shared a space "Project" to user "Alice" with role "" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies folder "/folder1" from space "Project" to "/testshare/folder1" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies folder "/folder1" from space "Project" to "/testshare/folder1" inside space "Shares" using the WebDAV API Then the HTTP status code should be "" - And for user "Alice" folder "testshare" of the space "Shares Jail" contain these files: + And for user "Alice" folder "testshare" of the space "Shares" contain these files: | /folder1/demo.txt | Examples: | role | shouldOrNot | permissions | status-code | @@ -381,15 +381,15 @@ Feature: copy file | viewer | should not | 403 | - Scenario Outline: User copies a folder from space personal to space shares jail with different permmissions + Scenario Outline: User copies a folder from space personal to space Shares with different permmissions Given user "Brian" has created folder "/testshare" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" And user "Alice" has created folder "folder1" And user "Alice" has uploaded file with content "some content" to "folder1/demo.txt" - When user "Alice" copies folder "/folder1" from space "Personal" to "/testshare/folder1" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies folder "/folder1" from space "Personal" to "/testshare/folder1" inside space "Shares" using the WebDAV API Then the HTTP status code should be "" - And for user "Alice" folder "testshare" of the space "Shares Jail" contain these files: + And for user "Alice" folder "testshare" of the space "Shares" contain these files: | folder1/demo.txt | Examples: | permissions | shouldOrNot | status-code | @@ -397,13 +397,13 @@ Feature: copy file | 17 | should not | 403 | - Scenario Outline: User copies a folder from space shares jail with different role to space personal + Scenario Outline: User copies a folder from space Shares with different role to space personal Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies file "/testshare/testshare.txt" from space "Shares Jail" to "/testshare.txt" inside space "Personal" using the WebDAV API + When user "Alice" copies file "/testshare/testshare.txt" from space "Shares" to "/testshare.txt" inside space "Personal" using the WebDAV API Then the HTTP status code should be "201" And for user "Alice" the space "Personal" should contain these entries: | /testshare.txt | @@ -414,7 +414,7 @@ Feature: copy file | 17 | - Scenario Outline: User copies a folder from space shares jail with different role to space project with different role + Scenario Outline: User copies a folder from space Shares with different role to space project with different role Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has shared a space "Project" to user "Alice" with role "" @@ -423,7 +423,7 @@ Feature: copy file And user "Brian" has uploaded file with content "testshare content" to "/testshare/folder1/testshare.txt" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies folder "/testshare/folder1" from space "Shares Jail" to "folder1" inside space "Project" using the WebDAV API + When user "Alice" copies folder "/testshare/folder1" from space "Shares" to "folder1" inside space "Project" using the WebDAV API Then the HTTP status code should be "201" And for user "Alice" the space "Project" should contain these entries: | /folder1/testshare.txt | @@ -435,7 +435,7 @@ Feature: copy file | editor | 17 | - Scenario Outline: User copies a folder from space shares jail with different role to space project with role viewer + Scenario Outline: User copies a folder from space Shares with different role to space project with role viewer Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has shared a space "Project" to user "Alice" with role "viewer" @@ -444,7 +444,7 @@ Feature: copy file And user "Brian" has uploaded file with content "testshare content" to "/testshare/folder1/testshare.txt" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies folder "/testshare/folder1" from space "Shares Jail" to "folder1" inside space "Project" using the WebDAV API + When user "Alice" copies folder "/testshare/folder1" from space "Shares" to "folder1" inside space "Project" using the WebDAV API Then the HTTP status code should be "403" And for user "Alice" the space "Project" should not contain these entries: | /folder1/testshare.txt | @@ -464,9 +464,9 @@ Feature: copy file | shareWith | Alice | And user "Alice" has accepted share "/testshare" offered by user "Brian" And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" - When user "Alice" copies file "/textfile0.txt" from space "Personal" to "/testshare/textfile0.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/textfile0.txt" from space "Personal" to "/testshare/textfile0.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "403" - And user "Alice" should not be able to download file "/testshare/textfile0.txt" from space "Shares Jail" + And user "Alice" should not be able to download file "/testshare/textfile0.txt" from space "Shares" Scenario: Copying a file to overwrite a file into a folder with no permissions @@ -480,9 +480,9 @@ Feature: copy file | permissions | read | | shareWith | Alice | And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" copies file "/textfile0.txt" from space "Personal" to "/testshare/overwritethis.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/textfile0.txt" from space "Personal" to "/testshare/overwritethis.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "403" - And for user "Alice" the content of the file "/testshare/overwritethis.txt" of the space "Shares Jail" should be "ownCloud test text file 1" + And for user "Alice" the content of the file "/testshare/overwritethis.txt" of the space "Shares" should be "ownCloud test text file 1" Scenario: copy a file over the top of an existing folder received as a user share @@ -492,9 +492,9 @@ Feature: copy file And user "Brian" has created folder "BRIAN-Folder/sample-folder" And user "Brian" has shared folder "BRIAN-Folder" with user "Alice" And user "Alice" has accepted share "/BRIAN-Folder" offered by user "Brian" - When user "Alice" copies file "/textfile1.txt" from space "Personal" to "/BRIAN-Folder" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/textfile1.txt" from space "Personal" to "/BRIAN-Folder" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" - And for user "Alice" the content of the file "/BRIAN-Folder" of the space "Shares Jail" should be "ownCloud test text file 1" + And for user "Alice" the content of the file "/BRIAN-Folder" of the space "Shares" should be "ownCloud test text file 1" And as "Alice" file "/textfile1.txt" should exist And user "Alice" should not have any received shares @@ -506,10 +506,10 @@ Feature: copy file And user "Brian" has uploaded file with content "file to share" to "/sharedfile1.txt" And user "Brian" has shared file "/sharedfile1.txt" with user "Alice" And user "Alice" has accepted share "/sharedfile1.txt" offered by user "Brian" - When user "Alice" copies folder "/FOLDER" from space "Personal" to "/sharedfile1.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies folder "/FOLDER" from space "Personal" to "/sharedfile1.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" And as "Alice" folder "/FOLDER/sample-folder" should exist - And for user "Alice" folder "/sharedfile1.txt" of the space "Shares Jail" should contain these files: + And for user "Alice" folder "/sharedfile1.txt" of the space "Shares" should contain these files: | /sample-folder | And user "Alice" should not have any received shares @@ -524,10 +524,10 @@ Feature: copy file And user "Alice" has created folder "/Sample-Folder-A" And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b" And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b/sample-folder-c" - When user "Alice" copies folder "/Sample-Folder-A/sample-folder-b" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-folder" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies folder "/Sample-Folder-A/sample-folder-b" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-folder" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" And as "Alice" folder "/Sample-Folder-A/sample-folder-b/sample-folder-c" should exist - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these entries: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should contain these entries: | /second-level-folder/third-level-folder/sample-folder-c/ | And for user "Brian" folder "BRIAN-FOLDER" of the space "Personal" should contain these files: | /second-level-folder/third-level-folder/sample-folder-c/ | @@ -545,14 +545,14 @@ Feature: copy file And user "Alice" has created folder "/Sample-Folder-A" And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b" And user "Alice" has uploaded file with content "sample file-c" to "/Sample-Folder-A/sample-folder-b/textfile-c.txt" - When user "Alice" copies file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" from space "Personal" to "/BRIAN-FOLDER/second-level-folder" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" from space "Personal" to "/BRIAN-FOLDER/second-level-folder" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should not contain these files: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should not contain these files: | /second-level-folder/third-level-folder | And as "Alice" file "Sample-Folder-A/sample-folder-b/textfile-c.txt" should exist - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these files: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should contain these files: | /second-level-folder | - And for user "Alice" the content of the file "/BRIAN-FOLDER/second-level-folder" of the space "Shares Jail" should be "sample file-c" + And for user "Alice" the content of the file "/BRIAN-FOLDER/second-level-folder" of the space "Shares" should be "sample file-c" And for user "Brian" the content of the file "/BRIAN-FOLDER/second-level-folder" of the space "Personal" should be "sample file-c" And the response when user "Alice" gets the info of the last share should include | file_target | /Shares/BRIAN-FOLDER | @@ -567,14 +567,14 @@ Feature: copy file And user "Alice" has created folder "/Sample-Folder-A" And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b" And user "Alice" has uploaded file with content "sample file-c" to "/Sample-Folder-A/sample-folder-b/textfile-c.txt" - When user "Alice" copies file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" from space "Personal" to "/BRIAN-FOLDER/second-level-file.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" from space "Personal" to "/BRIAN-FOLDER/second-level-file.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" And as "Alice" file "Sample-Folder-A/sample-folder-b/textfile-c.txt" should exist - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these files: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should contain these files: | /second-level-file.txt | - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should not contain these files: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should not contain these files: | /textfile-c.txt | - And for user "Alice" the content of the file "/BRIAN-FOLDER/second-level-file.txt" of the space "Shares Jail" should be "sample file-c" + And for user "Alice" the content of the file "/BRIAN-FOLDER/second-level-file.txt" of the space "Shares" should be "sample file-c" And for user "Brian" the content of the file "/BRIAN-FOLDER/second-level-file.txt" of the space "Personal" should be "sample file-c" And the response when user "Alice" gets the info of the last share should include | file_target | /Shares/BRIAN-FOLDER | @@ -590,11 +590,11 @@ Feature: copy file And user "Brian" has uploaded file with content "file at third level" to "BRIAN-FOLDER/second-level-folder/third-level-file.txt" And user "Brian" has shared folder "/BRIAN-FOLDER" with user "Alice" And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian" - When user "Alice" copies folder "/FOLDER/second-level-folder" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-file.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies folder "/FOLDER/second-level-folder" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-file.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these entries: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should contain these entries: | /second-level-folder/third-level-file.txt/third-level-folder | - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should not contain these entries: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should not contain these entries: | /second-level-folder/second-level-folder/ | And the response when user "Alice" gets the info of the last share should include | file_target | /Shares/BRIAN-FOLDER | @@ -613,10 +613,10 @@ Feature: copy file And user "Alice" has created folder "/Sample-Folder-A" And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b" And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b/sample-folder-c" - When user "Alice" copies folder "/Sample-Folder-A/sample-folder-b" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-folder" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies folder "/Sample-Folder-A/sample-folder-b" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-folder" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" And as "Alice" folder "/Sample-Folder-A/sample-folder-b/sample-folder-c" should exist - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these files: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should contain these files: | /second-level-folder/third-level-folder/sample-folder-c/ | And the response when user "Alice" gets the info of the last share should include | file_target | /Shares/BRIAN-FOLDER | @@ -635,11 +635,11 @@ Feature: copy file And user "Alice" has created folder "/Sample-Folder-A" And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b" And user "Alice" has uploaded file with content "sample file-c" to "/Sample-Folder-A/sample-folder-b/textfile-c.txt" - When user "Alice" copies file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" from space "Personal" to "/BRIAN-FOLDER/second-level-folder" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" from space "Personal" to "/BRIAN-FOLDER/second-level-folder" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should not contain these entries: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should not contain these entries: | /second-level-folder/third-level-folder | - And for user "Alice" the content of the file "/BRIAN-FOLDER/second-level-folder" of the space "Shares Jail" should be "sample file-c" + And for user "Alice" the content of the file "/BRIAN-FOLDER/second-level-folder" of the space "Shares" should be "sample file-c" And for user "Brian" the content of the file "/BRIAN-FOLDER/second-level-folder" of the space "Personal" should be "sample file-c" And the response when user "Alice" gets the info of the last share should include | file_target | /Shares/BRIAN-FOLDER | @@ -657,13 +657,13 @@ Feature: copy file And user "Alice" has created folder "/Sample-Folder-A" And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b" And user "Alice" has uploaded file with content "sample file-c" to "/Sample-Folder-A/sample-folder-b/textfile-c.txt" - When user "Alice" copies file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" from space "Personal" to "/BRIAN-FOLDER/second-level-file.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" from space "Personal" to "/BRIAN-FOLDER/second-level-file.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" And as "Alice" file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" should exist - And for user "Alice" folder "/BRIAN-FOLDER" of the space "Shares Jail" should not contain these files: + And for user "Alice" folder "/BRIAN-FOLDER" of the space "Shares" should not contain these files: | /textfile-c.txt | And as "Alice" file "/Sample-Folder-A/sample-folder-b/textfile-c.txt" should exist - And for user "Alice" the content of the file "/BRIAN-FOLDER/second-level-file.txt" of the space "Shares Jail" should be "sample file-c" + And for user "Alice" the content of the file "/BRIAN-FOLDER/second-level-file.txt" of the space "Shares" should be "sample file-c" And for user "Brian" the content of the file "/BRIAN-FOLDER/second-level-file.txt" of the space "Personal" should be "sample file-c" And the response when user "Alice" gets the info of the last share should include | file_target | /Shares/BRIAN-FOLDER | @@ -682,13 +682,13 @@ Feature: copy file And user "Alice" has created folder "/FOLDER" And user "Alice" has created folder "/FOLDER/second-level-folder" And user "Alice" has created folder "/FOLDER/second-level-folder/third-level-folder" - When user "Alice" copies folder "/FOLDER/second-level-folder" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-file.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" copies folder "/FOLDER/second-level-folder" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-file.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "204" - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should contain these files: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should contain these files: | /second-level-folder/third-level-file.txt/ | | /second-level-folder/third-level-file.txt/third-level-folder/ | And as "Alice" folder "FOLDER/second-level-folder/third-level-folder" should exist - And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares Jail" should not contain these files: + And for user "Alice" folder "BRIAN-FOLDER" of the space "Shares" should not contain these files: | /second-level-folder/second-level-folder | And the response when user "Alice" gets the info of the last share should include | file_target | /Shares/BRIAN-FOLDER | @@ -706,7 +706,7 @@ Feature: copy file | newfolder/insideSpace.txt | | newfolder/insideSpace (1).txt | And for user "Alice" the content of the file "/newfolder/insideSpace (1).txt" of the space "Project" should be "new content" - + Scenario: Copying a file with an option "replace" inside of the project space Given the administrator has given "Alice" the role "Space Admin" using the settings api @@ -727,7 +727,7 @@ Feature: copy file And as "Alice" file "insideSpace.txt" should not exist in the trashbin of the space "Project" - Scenario: Copying a file from Personal to Shares Jail with an option "keep both" + Scenario: Copying a file from Personal to Shares with an option "keep both" Given the administrator has given "Alice" the role "Space Admin" using the settings api And user "Alice" has created a space "Project" with the default quota using the GraphApi And user "Alice" has created a folder "/newfolder" in space "Project" @@ -735,18 +735,18 @@ Feature: copy file And user "Alice" shares the following entity "newfolder" inside of space "Project" with user "Brian" with role "editor" And user "Brian" has accepted share "/newfolder" offered by user "Alice" And user "Brian" has uploaded file with content "new content" to "/personal.txt" - When user "Brian" copies file "/personal.txt" from space "Personal" to "/newfolder/personal (1).txt" inside space "Shares Jail" using the WebDAV API + When user "Brian" copies file "/personal.txt" from space "Personal" to "/newfolder/personal (1).txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "201" And for user "Alice" the space "Project" should contain these entries: | newfolder/personal.txt | | newfolder/personal (1).txt | And for user "Alice" the content of the file "/newfolder/personal (1).txt" of the space "Project" should be "new content" - And for user "Brian" the space "Shares Jail" should contain these entries: + And for user "Brian" the space "Shares" should contain these entries: | newfolder/personal.txt | | newfolder/personal (1).txt | - Scenario: Copying a file from Personal to Shares Jail with an option "replace" + Scenario: Copying a file from Personal to Shares with an option "replace" Given the administrator has given "Alice" the role "Space Admin" using the settings api And user "Alice" has created a space "Project" with the default quota using the GraphApi And user "Alice" has created a folder "/newfolder" in space "Project" @@ -755,7 +755,7 @@ Feature: copy file And user "Alice" shares the following entity "newfolder" inside of space "Project" with user "Brian" with role "editor" And user "Brian" has accepted share "/newfolder" offered by user "Alice" And user "Brian" has uploaded file with content "new content" to "/personal.txt" - When user "Brian" overwrites file "/personal.txt" from space "Personal" to "/newfolder/personal.txt" inside space "Shares Jail" while copying using the WebDAV API + When user "Brian" overwrites file "/personal.txt" from space "Personal" to "/newfolder/personal.txt" inside space "Shares" while copying using the WebDAV API Then the HTTP status code should be "204" And for user "Alice" the space "Project" should contain these entries: | newfolder/personal.txt | @@ -763,8 +763,8 @@ Feature: copy file When user "Alice" downloads version of the file "/newfolder/personal.txt" with the index "1" of the space "Project" using the WebDAV API Then the HTTP status code should be "200" And the downloaded content should be "old content version 2" - And for user "Brian" the content of the file "/newfolder/personal.txt" of the space "Shares Jail" should be "new content" - When user "Brian" downloads version of the file "/newfolder/personal.txt" with the index "2" of the space "Shares Jail" using the WebDAV API + And for user "Brian" the content of the file "/newfolder/personal.txt" of the space "Shares" should be "new content" + When user "Brian" downloads version of the file "/newfolder/personal.txt" with the index "2" of the space "Shares" using the WebDAV API Then the HTTP status code should be "200" And the downloaded content should be "old content version 1" And as "Brian" file "insideSpace.txt" should not exist in the trashbin of the space "Personal" diff --git a/tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature b/tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature index 2d6575260..0c97b153c 100644 --- a/tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature +++ b/tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature @@ -32,7 +32,7 @@ Feature: create file or folder named similar to Shares folder And the content of file "" for user "Brian" should be "some text" And for user "Brian" the space "Personal" should contain these entries: | | - And for user "Brian" the space "Shares Jail" should contain these entries: + And for user "Brian" the space "Shares" should contain these entries: | FOLDER/ | Examples: | file_name | @@ -44,12 +44,12 @@ Feature: create file or folder named similar to Shares folder Given using spaces DAV path When user "Brian" creates folder "/Shares" using the WebDAV API Then the HTTP status code should be "201" - And for user "Brian" the space "Shares Jail" should contain these entries: + And for user "Brian" the space "Shares" should contain these entries: | FOLDER/ | Scenario: try to create a file named Shares Given using spaces DAV path When user "Brian" uploads file with content "some text" to "/Shares" using the WebDAV API Then the HTTP status code should be "201" - And for user "Brian" the space "Shares Jail" should contain these entries: + And for user "Brian" the space "Shares" should contain these entries: | FOLDER/ | diff --git a/tests/acceptance/features/apiSpacesShares/etagPropagation.feature b/tests/acceptance/features/apiSpacesShares/etagPropagation.feature index bd93c6598..b021a2402 100644 --- a/tests/acceptance/features/apiSpacesShares/etagPropagation.feature +++ b/tests/acceptance/features/apiSpacesShares/etagPropagation.feature @@ -17,24 +17,24 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/upload/file.txt" inside space "Personal" And user "Alice" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/file.txt" inside space "Shares Jail" - And user "Brian" has stored etag of element "upload/file.txt" on path "/upload/renamed.txt" inside space "Shares Jail" - When user "Brian" copies file "/upload/file.txt" to "/upload/renamed.txt" inside space "Shares Jail" using the WebDAV API + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/upload/file.txt" inside space "Shares" + And user "Brian" has stored etag of element "upload/file.txt" on path "/upload/renamed.txt" inside space "Shares" + When user "Brian" copies file "/upload/file.txt" to "/upload/renamed.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /upload/renamed.txt | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /upload/renamed.txt | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /upload/renamed.txt | Shares | And these etags should not have changed | user | path | space | | Alice | /upload/file.txt | Personal | - | Brian | /upload/file.txt | Shares Jail | + | Brian | /upload/file.txt | Shares | Scenario: copying a file inside a folder as a sharer changes its etag for all collaborators Given user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" @@ -44,10 +44,10 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/upload/file.txt" inside space "Personal" And user "Alice" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/file.txt" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/upload/file.txt" inside space "Shares" + And user "Brian" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Shares" When user "Alice" copies file "/upload/file.txt" to "/upload/renamed.txt" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed @@ -55,13 +55,13 @@ Feature: check etag propagation after different file alterations | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /upload/renamed.txt | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /upload/renamed.txt | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /upload/renamed.txt | Shares | And these etags should not have changed | user | path | space | | Alice | /upload/file.txt | Personal | - | Brian | /upload/file.txt | Shares Jail | + | Brian | /upload/file.txt | Shares | Scenario: as share receiver renaming a file inside a folder changes its etag for all collaborators @@ -71,21 +71,21 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Shares Jail" - When user "Brian" moves file "/upload/file.txt" to "/upload/renamed.txt" in space "Shares Jail" using the WebDAV API + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Shares" + When user "Brian" moves file "/upload/file.txt" to "/upload/renamed.txt" in space "Shares" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | And these etags should not have changed | user | path | space | | Alice | /upload/renamed.txt | Personal | - | Brian | /upload/renamed.txt | Shares Jail | + | Brian | /upload/renamed.txt | Shares | Scenario: as sharer renaming a file inside a folder changes its etag for all collaborators @@ -95,21 +95,21 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Shares" When user "Alice" moves file "/upload/file.txt" to "/upload/renamed.txt" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | And these etags should not have changed | user | path | space | | Alice | /upload/renamed.txt | Personal | - | Brian | /upload/renamed.txt | Shares Jail | + | Brian | /upload/renamed.txt | Shares | Scenario: as sharer moving a file from one folder to an other changes the etags of both folders for all collaborators @@ -123,9 +123,9 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/dst" inside space "Personal" And user "Alice" has stored etag of element "/upload/file.txt" on path "/dst/file.txt" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/dst" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/dst" inside space "Shares" When user "Alice" moves file "/upload/file.txt" to "/dst/file.txt" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed @@ -133,9 +133,9 @@ Feature: check etag propagation after different file alterations | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /dst | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /dst | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /dst | Shares | Scenario: as share receiver moving a file from one folder to an other changes the etags of both folders for all collaborators @@ -148,19 +148,19 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/dst" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/dst" inside space "Shares Jail" - When user "Brian" moves file "/upload/file.txt" to "/dst/file.txt" in space "Shares Jail" using the WebDAV API + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/dst" inside space "Shares" + When user "Brian" moves file "/upload/file.txt" to "/dst/file.txt" in space "Shares" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /dst | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /dst | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /dst | Shares | Scenario: as sharer moving a folder from one folder to an other changes the etags of both folders for all collaborators @@ -173,9 +173,9 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/dst" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/dst" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/dst" inside space "Shares" When user "Alice" moves file "/upload/toMove" to "/dst/toMove" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed @@ -183,9 +183,9 @@ Feature: check etag propagation after different file alterations | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /dst | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /dst | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /dst | Shares | Scenario: as share reciever moving a folder from one folder to an other changes the etags of both folders for all collaborators @@ -198,19 +198,19 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/dst" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/dst" inside space "Shares Jail" - When user "Brian" moves file "/upload/toMove" to "/dst/toMove" in space "Shares Jail" using the WebDAV API + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/dst" inside space "Shares" + When user "Brian" moves file "/upload/toMove" to "/dst/toMove" in space "Shares" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /dst | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /dst | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /dst | Shares | Scenario: as share receiver creating a folder inside a folder received as a share changes its etag for all collaborators @@ -218,16 +218,16 @@ Feature: check etag propagation after different file alterations And user "Brian" has accepted share "/upload" offered by user "Alice" And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - When user "Brian" creates a subfolder "/upload/new" in space "Shares Jail" using the WebDav Api + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + When user "Brian" creates a subfolder "/upload/new" in space "Shares" using the WebDav Api Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | Scenario: as sharer creating a folder inside a shared folder changes etag for all collaborators @@ -235,16 +235,16 @@ Feature: check etag propagation after different file alterations And user "Brian" has accepted share "/upload" offered by user "Alice" And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" When user "Alice" creates folder "/upload/new" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | Scenario: as share receiver uploading a file inside a folder received as a share changes its etag for all collaborators @@ -252,16 +252,16 @@ Feature: check etag propagation after different file alterations And user "Brian" has accepted share "/upload" offered by user "Alice" And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - When user "Brian" uploads a file inside space "Shares Jail" with content "uploaded content" to "/upload/file.txt" using the WebDAV API + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + When user "Brian" uploads a file inside space "Shares" with content "uploaded content" to "/upload/file.txt" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | Scenario: as sharer uploading a file inside a shared folder should update etags for all collaborators @@ -269,16 +269,16 @@ Feature: check etag propagation after different file alterations And user "Brian" has accepted share "/upload" offered by user "Alice" And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" When user "Alice" uploads file with content "uploaded content" to "/upload/file.txt" using the WebDAV API Then the HTTP status code should be "201" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | Scenario: as share receiver overwriting a file inside a received shared folder should update etags for all collaborators @@ -287,16 +287,16 @@ Feature: check etag propagation after different file alterations And user "Brian" has accepted share "/upload" offered by user "Alice" And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - When user "Brian" uploads a file inside space "Shares Jail" with content "new content" to "/upload/file.txt" using the WebDAV API + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + When user "Brian" uploads a file inside space "Shares" with content "new content" to "/upload/file.txt" using the WebDAV API Then the HTTP status code should be "204" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | Scenario: as sharer overwriting a file inside a shared folder should update etags for all collaborators @@ -305,16 +305,16 @@ Feature: check etag propagation after different file alterations And user "Brian" has accepted share "/upload" offered by user "Alice" And user "Alice" has stored etag of element "/" inside space "Personal" And user "Alice" has stored etag of element "/upload" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" When user "Alice" uploads file with content "new content" to "/upload/file.txt" using the WebDAV API Then the HTTP status code should be "204" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | Scenario: As share receiver deleting (removing) a file changes the etags of all parents for all collaborators @@ -326,19 +326,19 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/upload/sub" inside space "Personal" And user "Brian" has stored etag of element "/" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/sub" inside space "Shares Jail" - When user "Brian" removes the file "upload/sub/file.txt" from space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/upload/sub" inside space "Shares" + When user "Brian" removes the file "upload/sub/file.txt" from space "Shares" Then the HTTP status code should be "204" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /upload/sub | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /upload/sub | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /upload/sub | Shares | And these etags should not have changed | user | path | space | | Brian | / | Personal | @@ -353,9 +353,9 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/upload/sub" inside space "Personal" And user "Brian" has stored etag of element "/" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/sub" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/upload/sub" inside space "Shares" When user "Alice" removes the file "upload/sub/file.txt" from space "Personal" Then the HTTP status code should be "204" And these etags should have changed @@ -363,9 +363,9 @@ Feature: check etag propagation after different file alterations | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /upload/sub | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /upload/sub | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /upload/sub | Shares | And these etags should not have changed | user | path | space | | Brian | / | Personal | @@ -380,19 +380,19 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/upload/sub" inside space "Personal" And user "Brian" has stored etag of element "/" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/sub" inside space "Shares Jail" - When user "Brian" removes the file "upload/sub/toDelete" from space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/upload/sub" inside space "Shares" + When user "Brian" removes the file "upload/sub/toDelete" from space "Shares" Then the HTTP status code should be "204" And these etags should have changed | user | path | space | | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /upload/sub | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /upload/sub | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /upload/sub | Shares | And these etags should not have changed | user | path | space | | Brian | / | Personal | @@ -407,9 +407,9 @@ Feature: check etag propagation after different file alterations And user "Alice" has stored etag of element "/upload" inside space "Personal" And user "Alice" has stored etag of element "/upload/sub" inside space "Personal" And user "Brian" has stored etag of element "/" inside space "Personal" - And user "Brian" has stored etag of element "/" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload" inside space "Shares Jail" - And user "Brian" has stored etag of element "/upload/sub" inside space "Shares Jail" + And user "Brian" has stored etag of element "/" inside space "Shares" + And user "Brian" has stored etag of element "/upload" inside space "Shares" + And user "Brian" has stored etag of element "/upload/sub" inside space "Shares" When user "Alice" removes the file "upload/sub/toDelete" from space "Personal" Then the HTTP status code should be "204" And these etags should have changed @@ -417,9 +417,9 @@ Feature: check etag propagation after different file alterations | Alice | / | Personal | | Alice | /upload | Personal | | Alice | /upload/sub | Personal | - | Brian | / | Shares Jail | - | Brian | /upload | Shares Jail | - | Brian | /upload/sub | Shares Jail | + | Brian | / | Shares | + | Brian | /upload | Shares | + | Brian | /upload/sub | Shares | And these etags should not have changed | user | path | space | | Brian | / | Personal | diff --git a/tests/acceptance/features/apiSpacesShares/favorite.feature b/tests/acceptance/features/apiSpacesShares/favorite.feature index 467fe4295..b6b570568 100644 --- a/tests/acceptance/features/apiSpacesShares/favorite.feature +++ b/tests/acceptance/features/apiSpacesShares/favorite.feature @@ -13,34 +13,34 @@ Feature: favorite Scenario: favorite a received share itself Given user "Alice" has shared folder "/PARENT" with user "Brian" And user "Brian" has accepted share "/PARENT" offered by user "Alice" - When user "Brian" favorites element "/PARENT" in space "Shares Jail" using the WebDAV API + When user "Brian" favorites element "/PARENT" in space "Shares" using the WebDAV API Then the HTTP status code should be "207" - And as user "Brian" folder "/PARENT" inside space "Shares Jail" should be favorited + And as user "Brian" folder "/PARENT" inside space "Shares" should be favorited Scenario: favorite a file inside of a received share Given user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt" And user "Alice" has shared folder "/PARENT" with user "Brian" And user "Brian" has accepted share "/PARENT" offered by user "Alice" - When user "Brian" favorites element "/PARENT/parent.txt" in space "Shares Jail" using the WebDAV API + When user "Brian" favorites element "/PARENT/parent.txt" in space "Shares" using the WebDAV API Then the HTTP status code should be "207" - And as user "Brian" file "/PARENT/parent.txt" inside space "Shares Jail" should be favorited + And as user "Brian" file "/PARENT/parent.txt" inside space "Shares" should be favorited Scenario: favorite a folder inside of a received share Given user "Alice" has created folder "/PARENT/sub-folder" And user "Alice" has shared folder "/PARENT" with user "Brian" And user "Brian" has accepted share "/PARENT" offered by user "Alice" - When user "Brian" favorites element "/PARENT/sub-folder" in space "Shares Jail" using the WebDAV API + When user "Brian" favorites element "/PARENT/sub-folder" in space "Shares" using the WebDAV API Then the HTTP status code should be "207" - And as user "Brian" folder "/PARENT/sub-folder" inside space "Shares Jail" should be favorited + And as user "Brian" folder "/PARENT/sub-folder" inside space "Shares" should be favorited Scenario: sharee file favorite state should not change the favorite state of sharer Given user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt" And user "Alice" has shared file "/PARENT/parent.txt" with user "Brian" And user "Brian" has accepted share "/parent.txt" offered by user "Alice" - When user "Brian" favorites element "/parent.txt" in space "Shares Jail" using the WebDAV API + When user "Brian" favorites element "/parent.txt" in space "Shares" using the WebDAV API Then the HTTP status code should be "207" - And as user "Brian" file "/parent.txt" inside space "Shares Jail" should be favorited + And as user "Brian" file "/parent.txt" inside space "Shares" should be favorited And as user "Alice" file "/PARENT/parent.txt" inside space "Personal" should not be favorited diff --git a/tests/acceptance/features/apiSpacesShares/moveSpaces.feature b/tests/acceptance/features/apiSpacesShares/moveSpaces.feature index 0a2444e1d..f2a9ee51d 100644 --- a/tests/acceptance/features/apiSpacesShares/moveSpaces.feature +++ b/tests/acceptance/features/apiSpacesShares/moveSpaces.feature @@ -87,7 +87,7 @@ Feature: move (rename) file | viewer | 403 | - Scenario Outline: User moves a file from space project with different role to space shares jail with different role (permission) + Scenario Outline: User moves a file from space project with different role to space Shares with different role (permission) Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has created folder "/testshare" @@ -95,11 +95,11 @@ Feature: move (rename) file And user "Brian" has shared a space "Project" to user "Alice" with role "" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" moves file "project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" moves file "project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "502" And for user "Alice" the space "Project" should contain these entries: | project.txt | - And for user "Alice" the space "Shares Jail" should not contain these entries: + And for user "Alice" the space "Shares" should not contain these entries: | /testshare/project.txt | Examples: | role | permissions | @@ -129,16 +129,16 @@ Feature: move (rename) file | viewer | 403 | - Scenario Outline: User moves a file from space personal to space shares jail with different role (permission) + Scenario Outline: User moves a file from space personal to space Shares with different role (permission) Given user "Brian" has created folder "/testshare" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" And user "Alice" has uploaded file with content "personal content" to "personal.txt" - When user "Alice" moves file "personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" moves file "personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "502" And for user "Alice" the space "Personal" should contain these entries: | personal.txt | - And for user "Alice" the space "Shares Jail" should not contain these entries: + And for user "Alice" the space "Shares" should not contain these entries: | /testshare/personal.txt | Examples: | permissions | @@ -147,16 +147,16 @@ Feature: move (rename) file | 1 | - Scenario Outline: User moves a file from space shares jail with different role (permissions) to space personal + Scenario Outline: User moves a file from space Shares with different role (permissions) to space personal Given user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" moves file "/testshare/testshare.txt" from space "Shares Jail" to "testshare.txt" inside space "Personal" using the WebDAV API + When user "Alice" moves file "/testshare/testshare.txt" from space "Shares" to "testshare.txt" inside space "Personal" using the WebDAV API Then the HTTP status code should be "502" And for user "Alice" the space "Personal" should not contain these entries: | testshare.txt | - And for user "Alice" folder "testshare" of the space "Shares Jail" should contain these entries: + And for user "Alice" folder "testshare" of the space "Shares" should contain these entries: | testshare.txt | Examples: | permissions | @@ -165,7 +165,7 @@ Feature: move (rename) file | 1 | - Scenario Outline: User moves a file from space shares jail with different role (permissions) to space project with different role + Scenario Outline: User moves a file from space Shares with different role (permissions) to space project with different role Given the administrator has given "Brian" the role "Space Admin" using the settings api And user "Brian" has created a space "Project" with the default quota using the GraphApi And user "Brian" has shared a space "Project" to user "Alice" with role "" @@ -173,11 +173,11 @@ Feature: move (rename) file And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt" And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "" And user "Alice" has accepted share "/testshare" offered by user "Brian" - When user "Alice" moves file "/testshare/testshare.txt" from space "Shares Jail" to "testshare.txt" inside space "Project" using the WebDAV API + When user "Alice" moves file "/testshare/testshare.txt" from space "Shares" to "testshare.txt" inside space "Project" using the WebDAV API Then the HTTP status code should be "502" And for user "Alice" the space "Project" should not contain these entries: | /testshare.txt | - And for user "Alice" folder "testshare" of the space "Shares Jail" should contain these entries: + And for user "Alice" folder "testshare" of the space "Shares" should contain these entries: | testshare.txt | Examples: | role | permissions | @@ -189,7 +189,7 @@ Feature: move (rename) file | viewer | 17 | - Scenario: User moves a file from space shares jail with role editor to space shares jail with role editor + Scenario: User moves a file from space Shares with role editor to space Shares with role editor Given user "Brian" has created folder "/testshare1" And user "Brian" has created folder "/testshare2" And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt" @@ -197,17 +197,17 @@ Feature: move (rename) file And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "31" And user "Alice" has accepted share "/testshare1" offered by user "Brian" And user "Alice" has accepted share "/testshare2" offered by user "Brian" - When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares Jail" to "/testshare2/testshare1.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "201" - And for user "Alice" folder "testshare2" of the space "Shares Jail" should contain these entries: + And for user "Alice" folder "testshare2" of the space "Shares" should contain these entries: | testshare1.txt | - And for user "Alice" folder "testshare1" of the space "Shares Jail" should not contain these entries: + And for user "Alice" folder "testshare1" of the space "Shares" should not contain these entries: | testshare1.txt | And for user "Brian" the space "Personal" should contain these entries: | /testshare2/testshare1.txt | - Scenario: User moves a file from space shares jail with role editor to space shares jail with role viewer + Scenario: User moves a file from space Shares with role editor to space Shares with role viewer Given user "Brian" has created folder "/testshare1" And user "Brian" has created folder "/testshare2" And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt" @@ -215,15 +215,15 @@ Feature: move (rename) file And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "17" And user "Alice" has accepted share "/testshare1" offered by user "Brian" And user "Alice" has accepted share "/testshare2" offered by user "Brian" - When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares Jail" to "/testshare2/testshare1.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "403" - And for user "Alice" the space "Shares Jail" should not contain these entries: + And for user "Alice" the space "Shares" should not contain these entries: | /testshare2/testshare1.txt | And for user "Brian" the space "Personal" should not contain these entries: | /testshare2/testshare1.txt | - Scenario: User moves a file from space shares jail with role viewer to space shares jail with role editor + Scenario: User moves a file from space Shares with role viewer to space Shares with role editor Given user "Brian" has created folder "/testshare1" And user "Brian" has created folder "/testshare2" And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt" @@ -231,9 +231,9 @@ Feature: move (rename) file And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "31" And user "Alice" has accepted share "/testshare1" offered by user "Brian" And user "Alice" has accepted share "/testshare2" offered by user "Brian" - When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares Jail" to "/testshare2/testshare1.txt" inside space "Shares Jail" using the WebDAV API + When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API Then the HTTP status code should be "403" - And for user "Alice" the space "Shares Jail" should not contain these entries: + And for user "Alice" the space "Shares" should not contain these entries: | /testshare2/testshare1.txt | And for user "Brian" the space "Personal" should not contain these entries: | /testshare2/testshare1.txt | @@ -248,19 +248,19 @@ Feature: move (rename) file And user "Alice" has shared folder "/folderB" with user "Brian" And user "Brian" has accepted share "/folderA" offered by user "Alice" And user "Brian" has accepted share "/folderB" offered by user "Alice" - And user "Brian" has created a folder "/folderA/ONE" in space "Shares Jail" - And user "Brian" has created a folder "/folderA/ONE/TWO" in space "Shares Jail" - And user "Brian" has stored id of folder "/folderA/ONE" of the space "Shares Jail" - When user "Brian" moves folder "/folderA/ONE" from space "Shares Jail" to "/folderB/ONE" inside space "Shares Jail" using the WebDAV API + And user "Brian" has created a folder "/folderA/ONE" in space "Shares" + And user "Brian" has created a folder "/folderA/ONE/TWO" in space "Shares" + And user "Brian" has stored id of folder "/folderA/ONE" of the space "Shares" + When user "Brian" moves folder "/folderA/ONE" from space "Shares" to "/folderB/ONE" inside space "Shares" using the WebDAV API Then the HTTP status code should be "201" - And for user "Brian" the space "Shares Jail" should contain these entries: + And for user "Brian" the space "Shares" should contain these entries: | /folderA | - And for user "Brian" folder "folderB" of the space "Shares Jail" should contain these entries: + And for user "Brian" folder "folderB" of the space "Shares" should contain these entries: | /ONE | - And for user "Brian" folder "folderA" of the space "Shares Jail" should not contain these entries: + And for user "Brian" folder "folderA" of the space "Shares" should not contain these entries: | /ONE | | /ONE/TWO | - And user "Brian" folder "/folderB/ONE" of the space "Shares Jail" should have the previously stored id + And user "Brian" folder "/folderB/ONE" of the space "Shares" should have the previously stored id Scenario: Moving a file out of a shared folder as a sharer @@ -275,7 +275,7 @@ Feature: move (rename) file When user "Brian" moves file "/testshare/testfile.txt" from space "Personal" to "/testfile.txt" inside space "Personal" using the WebDAV API Then the HTTP status code should be "201" And the content of file "/testfile.txt" for user "Brian" should be "test data" - And for user "Alice" folder "testshare" of the space "Shares Jail" should not contain these entries: + And for user "Alice" folder "testshare" of the space "Shares" should not contain these entries: | testfile.txt | And for user "Brian" the space "Personal" should not contain these entries: | /testshare/testfile.txt | @@ -296,7 +296,7 @@ Feature: move (rename) file When user "Brian" moves folder "/testshare/testsubfolder" from space "Personal" to "/testsubfolder" inside space "Personal" using the WebDAV API Then the HTTP status code should be "201" And the content of file "/testsubfolder/testfile.txt" for user "Brian" should be "test data" - And for user "Alice" folder "testshare" of the space "Shares Jail" should not contain these entries: + And for user "Alice" folder "testshare" of the space "Shares" should not contain these entries: | testsubfolder | And for user "Brian" the space "Personal" should not contain these entries: | /testshare/testsubfolder | diff --git a/tests/acceptance/features/apiSpacesShares/shareOperations.feature b/tests/acceptance/features/apiSpacesShares/shareOperations.feature index 896ec6f0e..583f96935 100644 --- a/tests/acceptance/features/apiSpacesShares/shareOperations.feature +++ b/tests/acceptance/features/apiSpacesShares/shareOperations.feature @@ -14,7 +14,7 @@ Feature: sharing Given user "Alice" has uploaded file with content "foo" to "/tmp.txt" And user "Alice" has shared file "/tmp.txt" with user "Brian" And user "Brian" has accepted share "/tmp.txt" offered by user "Alice" - When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -31,7 +31,7 @@ Feature: sharing | permissions | share,update,read | | shareWith | grp1 | And user "Brian" has accepted share "/tmp.txt" offered by user "Alice" - When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -45,7 +45,7 @@ Feature: sharing When user "Alice" updates the last share using the sharing API with | permissions | update,read | Then the HTTP status code should be "200" - And as user "Brian" file "/tmp.txt" inside space "Shares Jail" should contain a property "ocs:share-permissions" with value "3" + And as user "Brian" file "/tmp.txt" inside space "Shares" should contain a property "ocs:share-permissions" with value "3" Scenario: Correct webdav share-permissions for received group shared file with edit permissions but no reshare permissions @@ -58,7 +58,7 @@ Feature: sharing | permissions | update,read | | shareWith | grp1 | And user "Brian" has accepted share "/tmp.txt" offered by user "Alice" - When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -72,7 +72,7 @@ Feature: sharing When user "Alice" updates the last share using the sharing API with | permissions | share,read | Then the HTTP status code should be "200" - And as user "Brian" file "/tmp.txt" inside space "Shares Jail" should contain a property "ocs:share-permissions" with value "17" + And as user "Brian" file "/tmp.txt" inside space "Shares" should contain a property "ocs:share-permissions" with value "17" Scenario: Correct webdav share-permissions for received group shared file with reshare permissions but no edit permissions @@ -85,7 +85,7 @@ Feature: sharing | permissions | share,read | | shareWith | grp1 | And user "Brian" has accepted share "/tmp.txt" offered by user "Alice" - When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -96,7 +96,7 @@ Feature: sharing Given user "Alice" has created folder "/tmp" And user "Alice" has shared file "/tmp" with user "Brian" And user "Brian" has accepted share "/tmp" offered by user "Alice" - When user "Brian" gets the following properties of folder "/tmp" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -112,7 +112,7 @@ Feature: sharing | shareType | group | | shareWith | grp1 | And user "Brian" has accepted share "/tmp" offered by user "Alice" - When user "Brian" gets the following properties of folder "/tmp" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -126,7 +126,7 @@ Feature: sharing When user "Alice" updates the last share using the sharing API with | permissions | share,delete,create,read | Then the HTTP status code should be "200" - And as user "Brian" folder "/tmp" inside space "Shares Jail" should contain a property "ocs:share-permissions" with value "29" + And as user "Brian" folder "/tmp" inside space "Shares" should contain a property "ocs:share-permissions" with value "29" Scenario: Correct webdav share-permissions for received group shared folder with all permissions but edit @@ -139,7 +139,7 @@ Feature: sharing | shareWith | grp1 | | permissions | share,delete,create,read | And user "Brian" has accepted share "/tmp" offered by user "Alice" - When user "Brian" gets the following properties of folder "/tmp" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -153,7 +153,7 @@ Feature: sharing When user "Alice" updates the last share using the sharing API with | permissions | share,delete,update,read | Then the HTTP status code should be "200" - And as user "Brian" folder "/tmp" inside space "Shares Jail" should contain a property "ocs:share-permissions" with value "27" + And as user "Brian" folder "/tmp" inside space "Shares" should contain a property "ocs:share-permissions" with value "27" Scenario: Correct webdav share-permissions for received group shared folder with all permissions but create @@ -166,7 +166,7 @@ Feature: sharing | shareWith | grp1 | | permissions | share,delete,update,read | And user "Brian" has accepted share "/tmp" offered by user "Alice" - When user "Brian" gets the following properties of folder "/tmp" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -180,7 +180,7 @@ Feature: sharing When user "Alice" updates the last share using the sharing API with | permissions | share,create,update,read | Then the HTTP status code should be "200" - And as user "Brian" folder "/tmp" inside space "Shares Jail" should contain a property "ocs:share-permissions" with value "23" + And as user "Brian" folder "/tmp" inside space "Shares" should contain a property "ocs:share-permissions" with value "23" Scenario: Correct webdav share-permissions for received group shared folder with all permissions but delete @@ -193,7 +193,7 @@ Feature: sharing | shareWith | grp1 | | permissions | share,create,update,read | And user "Brian" has accepted share "/tmp" offered by user "Alice" - When user "Brian" gets the following properties of folder "/tmp" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -207,7 +207,7 @@ Feature: sharing When user "Alice" updates the last share using the sharing API with | permissions | change | Then the HTTP status code should be "200" - And as user "Brian" folder "/tmp" inside space "Shares Jail" should contain a property "ocs:share-permissions" with value "15" + And as user "Brian" folder "/tmp" inside space "Shares" should contain a property "ocs:share-permissions" with value "15" Scenario: Correct webdav share-permissions for received group shared folder with all permissions but share @@ -220,7 +220,7 @@ Feature: sharing | shareWith | grp1 | | permissions | change | And user "Brian" has accepted share "/tmp" offered by user "Alice" - When user "Brian" gets the following properties of folder "/tmp" inside space "Shares Jail" using the WebDAV API + When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API | propertyName | | ocs:share-permissions | Then the HTTP status code should be "200" @@ -237,7 +237,7 @@ Feature: sharing | permissions | read | | shareWith | grp1 | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - When user "Brian" uploads a file inside space "Shares Jail" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "403" And as "Alice" file "/FOLDER/textfile.txt" should not exist @@ -250,7 +250,7 @@ Feature: sharing | permissions | create | | shareWith | Brian | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - When user "Brian" uploads a file inside space "Shares Jail" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "201" And the following headers should match these regular expressions for user "Brian" | ETag | /^"[a-f0-9:\.]{1,32}"$/ | @@ -270,7 +270,7 @@ Feature: sharing | permissions | create | | shareWith | grp1 | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - When user "Brian" uploads a file inside space "Shares Jail" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "201" And the following headers should match these regular expressions for user "Brian" | ETag | /^"[a-f0-9:\.]{1,32}"$/ | @@ -288,7 +288,7 @@ Feature: sharing | permissions | change | | shareWith | Brian | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - When user "Brian" uploads a file inside space "Shares Jail" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "201" And the content of file "/FOLDER/textfile.txt" for user "Alice" should be: """ @@ -306,7 +306,7 @@ Feature: sharing | permissions | change | | shareWith | grp1 | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - When user "Brian" uploads a file inside space "Shares Jail" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "201" And the content of file "/FOLDER/textfile.txt" for user "Alice" should be: """ @@ -323,7 +323,7 @@ Feature: sharing | shareWith | Brian | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" - When user "Brian" uploads a file inside space "Shares Jail" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "507" And as "Alice" file "/FOLDER/textfile.txt" should not exist @@ -337,7 +337,7 @@ Feature: sharing | shareWith | Brian | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" - When user "Brian" uploads a file inside space "Shares Jail" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "507" And as "Alice" file "/FOLDER/textfile.txt" should not exist @@ -353,7 +353,7 @@ Feature: sharing | shareWith | grp1 | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "10" - When user "Brian" uploads a file inside space "Shares Jail" with content "new descriptionfgshsywhhh" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "new descriptionfgshsywhhh" to "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "507" And as "Alice" file "/FOLDER/textfile.txt" should not exist @@ -366,7 +366,7 @@ Feature: sharing | permissions | | | shareWith | Brian | And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - When user "Brian" uploads a file inside space "Shares Jail" with content "some content" to "/FOLDER/textfile.txt" using the WebDAV API + When user "Brian" uploads a file inside space "Shares" with content "some content" to "/FOLDER/textfile.txt" using the WebDAV API And user "Alice" downloads file "/FOLDER/textfile.txt" using the WebDAV API Then the HTTP status code should be "200" And the downloaded content should be "some content" diff --git a/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature b/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature index b66f6b98b..467807abf 100644 --- a/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature +++ b/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature @@ -16,10 +16,10 @@ Feature: upload resources on share using TUS protocol Given user "Alice" has created folder "/toShare" And user "Alice" has shared folder "/toShare" with user "Brian" And user "Brian" has accepted share "/toShare" offered by user "Alice" - When user "Brian" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Shares Jail" using the WebDAV API - Then for user "Brian" folder "toShare" of the space "Shares Jail" should contain these entries: + When user "Brian" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Shares" using the WebDAV API + Then for user "Brian" folder "toShare" of the space "Shares" should contain these entries: | file.txt | - And as "Brian" the mtime of the file "/toShare/file.txt" in space "Shares Jail" should be "Thu, 08 Aug 2012 04:18:13 GMT" + And as "Brian" the mtime of the file "/toShare/file.txt" in space "Shares" should be "Thu, 08 Aug 2012 04:18:13 GMT" And as "Alice" the mtime of the file "/toShare/file.txt" in space "Personal" should be "Thu, 08 Aug 2012 04:18:13 GMT" @@ -31,7 +31,7 @@ Feature: upload resources on share using TUS protocol Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries: | file.txt | And as "Alice" the mtime of the file "/toShare/file.txt" in space "Personal" should be "Thu, 08 Aug 2012 04:18:13 GMT" - And as "Brian" the mtime of the file "/toShare/file.txt" in space "Shares Jail" should be "Thu, 08 Aug 2012 04:18:13 GMT" + And as "Brian" the mtime of the file "/toShare/file.txt" in space "Shares" should be "Thu, 08 Aug 2012 04:18:13 GMT" Scenario: overwriting a file with mtime in a received share @@ -39,10 +39,10 @@ Feature: upload resources on share using TUS protocol And user "Alice" has shared folder "/toShare" with user "Brian" And user "Brian" has accepted share "/toShare" offered by user "Alice" And user "Alice" has uploaded file with content "uploaded content" to "/toShare/file.txt" - When user "Brian" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Shares Jail" using the WebDAV API - Then for user "Brian" folder "toShare" of the space "Shares Jail" should contain these entries: + When user "Brian" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Shares" using the WebDAV API + Then for user "Brian" folder "toShare" of the space "Shares" should contain these entries: | file.txt | - And as "Brian" the mtime of the file "/toShare/file.txt" in space "Shares Jail" should be "Thu, 08 Aug 2012 04:18:13 GMT" + And as "Brian" the mtime of the file "/toShare/file.txt" in space "Shares" should be "Thu, 08 Aug 2012 04:18:13 GMT" And as "Alice" the mtime of the file "/toShare/file.txt" in space "Personal" should be "Thu, 08 Aug 2012 04:18:13 GMT" @@ -50,12 +50,12 @@ Feature: upload resources on share using TUS protocol Given user "Alice" has created folder "/toShare" And user "Alice" has shared folder "/toShare" with user "Brian" And user "Brian" has accepted share "/toShare" offered by user "Alice" - And user "Brian" has uploaded a file inside space "Shares Jail" with content "uploaded content" to "toShare/file.txt" + And user "Brian" has uploaded a file inside space "Shares" with content "uploaded content" to "toShare/file.txt" When user "Alice" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Personal" using the WebDAV API Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries: | file.txt | And as "Alice" the mtime of the file "/toShare/file.txt" in space "Personal" should be "Thu, 08 Aug 2012 04:18:13 GMT" - And as "Brian" the mtime of the file "/toShare/file.txt" in space "Shares Jail" should be "Thu, 08 Aug 2012 04:18:13 GMT" + And as "Brian" the mtime of the file "/toShare/file.txt" in space "Shares" should be "Thu, 08 Aug 2012 04:18:13 GMT" Scenario: attempt to upload a file into a nonexistent folder within correctly received share @@ -63,8 +63,8 @@ Feature: upload resources on share using TUS protocol And user "Alice" has created folder "/toShare" And user "Alice" has shared folder "/toShare" with user "Brian" And user "Brian" has accepted share "/toShare" offered by user "Alice" - When user "Brian" uploads a file with content "uploaded content" to "/toShare/nonExistentFolder/file.txt" via TUS inside of the space "Shares Jail" using the WebDAV API - Then for user "Brian" folder "toShare" of the space "Shares Jail" should not contain these entries: + When user "Brian" uploads a file with content "uploaded content" to "/toShare/nonExistentFolder/file.txt" via TUS inside of the space "Shares" using the WebDAV API + Then for user "Brian" folder "toShare" of the space "Shares" should not contain these entries: | nonExistentFolder/file.txt | @@ -73,8 +73,8 @@ Feature: upload resources on share using TUS protocol And user "Alice" has created folder "/toShare" And user "Alice" has shared folder "/toShare" with user "Brian" with permissions "read" And user "Brian" has accepted share "/toShare" offered by user "Alice" - When user "Brian" uploads a file with content "uploaded content" to "/toShare/nonExistentFolder/file.txt" via TUS inside of the space "Shares Jail" using the WebDAV API - Then for user "Brian" folder "toShare" of the space "Shares Jail" should not contain these entries: + When user "Brian" uploads a file with content "uploaded content" to "/toShare/nonExistentFolder/file.txt" via TUS inside of the space "Shares" using the WebDAV API + Then for user "Brian" folder "toShare" of the space "Shares" should not contain these entries: | nonExistentFolder/file.txt | @@ -82,7 +82,7 @@ Feature: upload resources on share using TUS protocol Given user "Alice" has created folder "/toShare" And user "Alice" has shared folder "/toShare" with user "Brian" And user "Brian" has accepted share "/toShare" offered by user "Alice" - When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares Jail" using the WebDAV API + When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries: | file.txt | And for user "Alice" the content of the file "toShare/file.txt" of the space "Personal" should be "uploaded content" @@ -92,7 +92,7 @@ Feature: upload resources on share using TUS protocol Given user "Alice" has created folder "/toShare" And user "Alice" has shared folder "/toShare" with user "Brian" with permissions "change" And user "Brian" has accepted share "/toShare" offered by user "Alice" - When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares Jail" using the WebDAV API + When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries: | file.txt | And for user "Alice" the content of the file "toShare/file.txt" of the space "Personal" should be "uploaded content" @@ -104,7 +104,7 @@ Feature: upload resources on share using TUS protocol And user "Alice" has created folder "/toShare" And user "Alice" has shared folder "toShare" with group "grp1" with permissions "change" And user "Brian" has accepted share "/toShare" offered by user "Alice" - When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares Jail" using the WebDAV API + When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries: | file.txt | And for user "Alice" the content of the file "toShare/file.txt" of the space "Personal" should be "uploaded content" @@ -115,7 +115,7 @@ Feature: upload resources on share using TUS protocol And user "Alice" has uploaded file with content "original content" to "/toShare/file.txt" And user "Alice" has shared folder "/toShare" with user "Brian" And user "Brian" has accepted share "/toShare" offered by user "Alice" - When user "Brian" uploads a file with content "overwritten content" to "/toShare/file.txt" via TUS inside of the space "Shares Jail" using the WebDAV API + When user "Brian" uploads a file with content "overwritten content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries: | file.txt | And for user "Alice" the content of the file "toShare/file.txt" of the space "Personal" should be "overwritten content" @@ -125,8 +125,8 @@ Feature: upload resources on share using TUS protocol Given user "Alice" has created folder "/toShare" And user "Alice" has shared folder "/toShare" with user "Brian" with permissions "read" And user "Brian" has accepted share "/toShare" offered by user "Alice" - When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares Jail" using the WebDAV API - Then for user "Brian" folder "toShare" of the space "Shares Jail" should not contain these entries: + When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API + Then for user "Brian" folder "toShare" of the space "Shares" should not contain these entries: | file.txt | @@ -140,7 +140,7 @@ Feature: upload resources on share using TUS protocol | Upload-Metadata | filename L0ZPTERFUi90ZXh0RmlsZS50eHQ= | | Tus-Resumable | 1.0.0 | And user "Alice" has uploaded file with checksum "SHA1 8cb2237d0679ca88db6464eac60da96345513964" to the last created TUS Location with offset "0" and content "12345" via TUS inside of the space "Personal" using the WebDAV API - When user "Brian" requests the checksum of file "/FOLDER/textFile.txt" in space "Shares Jail" via propfind using the WebDAV API + When user "Brian" requests the checksum of file "/FOLDER/textFile.txt" in space "Shares" via propfind using the WebDAV API Then the HTTP status code should be "207" And the webdav checksum should match "SHA1:8cb2237d0679ca88db6464eac60da96345513964 MD5:827ccb0eea8a706c4c34a16891f84e7b ADLER32:02f80100" @@ -155,7 +155,7 @@ Feature: upload resources on share using TUS protocol | Upload-Metadata | filename L0ZPTERFUi90ZXh0RmlsZS50eHQ= | | Tus-Resumable | 1.0.0 | And user "Alice" has uploaded file with checksum "SHA1 8cb2237d069ca88db6464eac60da96345513964" to the last created TUS Location with offset "0" and content "12345" via TUS inside of the space "Personal" using the WebDAV API - When user "Brian" downloads the file "/FOLDER/textFile.txt" of the space "Shares Jail" using the WebDAV API + When user "Brian" downloads the file "/FOLDER/textFile.txt" of the space "Shares" using the WebDAV API Then the header checksum should match "SHA1:8cb2237d0679ca88db6464eac60da96345513964" @@ -168,7 +168,7 @@ Feature: upload resources on share using TUS protocol And user "Alice" has uploaded file with checksum "SHA1 8cb2237d0679ca88db6464eac60da96345513964" to the last created TUS Location with offset "0" and content "12345" via TUS inside of the space "Personal" using the WebDAV API And user "Alice" has shared file "/textFile.txt" with user "Brian" And user "Brian" has accepted share "/textFile.txt" offered by user "Alice" - When user "Brian" requests the checksum of file "/textFile.txt" in space "Shares Jail" via propfind using the WebDAV API + When user "Brian" requests the checksum of file "/textFile.txt" in space "Shares" via propfind using the WebDAV API Then the HTTP status code should be "207" And the webdav checksum should match "SHA1:8cb2237d0679ca88db6464eac60da96345513964 MD5:827ccb0eea8a706c4c34a16891f84e7b ADLER32:02f80100" @@ -182,7 +182,7 @@ Feature: upload resources on share using TUS protocol And user "Alice" has uploaded file with checksum "SHA1 8cb2237d0679ca88db6464eac60da96345513964" to the last created TUS Location with offset "0" and content "12345" via TUS inside of the space "Personal" using the WebDAV API And user "Alice" has shared file "/textFile.txt" with user "Brian" And user "Brian" has accepted share "/textFile.txt" offered by user "Alice" - When user "Brian" downloads the file "/textFile.txt" of the space "Shares Jail" using the WebDAV API + When user "Brian" downloads the file "/textFile.txt" of the space "Shares" using the WebDAV API Then the header checksum should match "SHA1:8cb2237d0679ca88db6464eac60da96345513964" @@ -190,12 +190,12 @@ Feature: upload resources on share using TUS protocol Given user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - When user "Brian" creates a new TUS resource for the space "Shares Jail" using the WebDAV API with these headers: + When user "Brian" creates a new TUS resource for the space "Shares" using the WebDAV API with these headers: | Upload-Length | 16 | # L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt | Upload-Metadata | filename L0ZPTERFUi90ZXh0RmlsZS50eHQ= | | Tus-Resumable | 1.0.0 | - And user "Brian" uploads file with checksum "MD5 827ccb0eea8a706c4c34a16891f84e7b" to the last created TUS Location with offset "0" and content "uploaded content" via TUS inside of the space "Shares Jail" using the WebDAV API + And user "Brian" uploads file with checksum "MD5 827ccb0eea8a706c4c34a16891f84e7b" to the last created TUS Location with offset "0" and content "uploaded content" via TUS inside of the space "Shares" using the WebDAV API Then for user "Alice" folder "FOLDER" of the space "Personal" should contain these entries: | textFile.txt | And for user "Alice" the content of the file "FOLDER/textFile.txt" of the space "Personal" should be "uploaded content" @@ -205,12 +205,12 @@ Feature: upload resources on share using TUS protocol Given user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - When user "Brian" creates a new TUS resource for the space "Shares Jail" using the WebDAV API with these headers: + When user "Brian" creates a new TUS resource for the space "Shares" using the WebDAV API with these headers: | Upload-Length | 16 | # L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt | Upload-Metadata | filename L0ZPTERFUi90ZXh0RmlsZS50eHQ= | | Tus-Resumable | 1.0.0 | - And user "Brian" uploads file with checksum "MD5 827ccb0eea8a706c4c34a16891f84e8c" to the last created TUS Location with offset "0" and content "uploaded content" via TUS inside of the space "Shares Jail" using the WebDAV API + And user "Brian" uploads file with checksum "MD5 827ccb0eea8a706c4c34a16891f84e8c" to the last created TUS Location with offset "0" and content "uploaded content" via TUS inside of the space "Shares" using the WebDAV API Then the HTTP status code should be "406" And for user "Alice" folder "FOLDER" of the space "Personal" should not contain these entries: | textFile.txt | @@ -229,7 +229,7 @@ Feature: upload resources on share using TUS protocol Then the HTTP status code should be "406" And for user "Alice" folder "FOLDER" of the space "Personal" should not contain these entries: | textFile.txt | - And for user "Brian" folder "FOLDER" of the space "Shares Jail" should not contain these entries: + And for user "Brian" folder "FOLDER" of the space "Shares" should not contain these entries: | textFile.txt | @@ -243,20 +243,20 @@ Feature: upload resources on share using TUS protocol And user "Alice" sends a chunk to the last created TUS Location with offset "5" and data "56789" with checksum "MD5 099ebea48ea9666a7da2177267983138" via TUS inside of the space "Personal" using the WebDAV API And user "Alice" shares file "textFile.txt" with user "Brian" using the sharing API And user "Brian" accepts share "/textFile.txt" offered by user "Alice" using the sharing API - Then for user "Brian" the content of the file "/textFile.txt" of the space "Shares Jail" should be "0123456789" + Then for user "Brian" the content of the file "/textFile.txt" of the space "Shares" should be "0123456789" Scenario: Sharee uploads a chunked file with correct checksum to a received share folder should work Given user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" And user "Brian" has accepted share "/FOLDER" offered by user "Alice" - And user "Brian" has created a new TUS resource for the space "Shares Jail" using the WebDAV API with these headers: + And user "Brian" has created a new TUS resource for the space "Shares" using the WebDAV API with these headers: | Upload-Length | 10 | # L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt | Upload-Metadata | filename L0ZPTERFUi90ZXh0RmlsZS50eHQ= | | Tus-Resumable | 1.0.0 | - When user "Brian" sends a chunk to the last created TUS Location with offset "0" and data "01234" with checksum "MD5 4100c4d44da9177247e44a5fc1546778" via TUS inside of the space "Shares Jail" using the WebDAV API - And user "Brian" sends a chunk to the last created TUS Location with offset "5" and data "56789" with checksum "MD5 099ebea48ea9666a7da2177267983138" via TUS inside of the space "Shares Jail" using the WebDAV API + When user "Brian" sends a chunk to the last created TUS Location with offset "0" and data "01234" with checksum "MD5 4100c4d44da9177247e44a5fc1546778" via TUS inside of the space "Shares" using the WebDAV API + And user "Brian" sends a chunk to the last created TUS Location with offset "5" and data "56789" with checksum "MD5 099ebea48ea9666a7da2177267983138" via TUS inside of the space "Shares" using the WebDAV API Then the HTTP status code should be "204" And for user "Alice" folder "FOLDER" of the space "Personal" should contain these entries: | textFile.txt | @@ -272,7 +272,7 @@ Feature: upload resources on share using TUS protocol And user "Alice" has uploaded file with checksum "SHA1 c1dab0c0864b6ac9bdd3743a1408d679f1acd823" to the last created TUS Location with offset "0" and content "original content" via TUS inside of the space "Personal" using the WebDAV API And user "Alice" has shared file "/textFile.txt" with user "Brian" And user "Brian" has accepted share "/textFile.txt" offered by user "Alice" - When user "Brian" overwrites recently shared file with offset "0" and data "overwritten content" with checksum "SHA1 fe990d2686a0fc86004efc31f5bf2475a45d4905" via TUS inside of the space "Shares Jail" using the WebDAV API with these headers: + When user "Brian" overwrites recently shared file with offset "0" and data "overwritten content" with checksum "SHA1 fe990d2686a0fc86004efc31f5bf2475a45d4905" via TUS inside of the space "Shares" using the WebDAV API with these headers: | Upload-Length | 19 | # dGV4dEZpbGUudHh0 is the base64 encode of textFile.txt | Upload-Metadata | filename dGV4dEZpbGUudHh0 | @@ -290,7 +290,7 @@ Feature: upload resources on share using TUS protocol And user "Alice" has uploaded file with checksum "SHA1 c1dab0c0864b6ac9bdd3743a1408d679f1acd823" to the last created TUS Location with offset "0" and content "original content" via TUS inside of the space "Personal" using the WebDAV API And user "Alice" has shared file "/textFile.txt" with user "Brian" And user "Brian" has accepted share "/textFile.txt" offered by user "Alice" - When user "Brian" overwrites recently shared file with offset "0" and data "overwritten content" with checksum "SHA1 fe990d2686a0fc86004efc31f5bf2475a45d4906" via TUS inside of the space "Shares Jail" using the WebDAV API with these headers: + When user "Brian" overwrites recently shared file with offset "0" and data "overwritten content" with checksum "SHA1 fe990d2686a0fc86004efc31f5bf2475a45d4906" via TUS inside of the space "Shares" using the WebDAV API with these headers: | Upload-Length | 19 | # dGV4dEZpbGUudHh0 is the base64 encode of textFile.txt | Upload-Metadata | filename dGV4dEZpbGUudHh0 | diff --git a/tests/acceptance/features/bootstrap/SpacesContext.php b/tests/acceptance/features/bootstrap/SpacesContext.php index 331e5c5ab..dc1ba86f6 100644 --- a/tests/acceptance/features/bootstrap/SpacesContext.php +++ b/tests/acceptance/features/bootstrap/SpacesContext.php @@ -101,7 +101,7 @@ class SpacesContext implements Context { * "Personal" => [ * "file1.txt": "etag1", * ], - * "Shares Jail" => [] + * "Shares" => [] * ], * "user2" => [ * ...