diff --git a/tests/acceptance/features/apiFavorites/favorites.feature b/tests/acceptance/features/apiFavorites/favorites.feature index 52b3c49510c8..cafd56737aed 100644 --- a/tests/acceptance/features/apiFavorites/favorites.feature +++ b/tests/acceptance/features/apiFavorites/favorites.feature @@ -86,8 +86,8 @@ Feature: favorite | old | | new | - @smokeTest - @skipOnOcis @issue-ocis-reva-21 + @smokeTest @toImplementOnOCIS + @skipOnOcis @issue-ocis-reva-39 Scenario Outline: Get favorited elements of a folder Given using DAV path When user "Alice" favorites element "/FOLDER" using the WebDAV API @@ -103,7 +103,8 @@ Feature: favorite | old | | new | - @skipOnOcis @issue-ocis-reva-21 + @toImplementOnOCIS + @skipOnOcis @issue-ocis-reva-39 Scenario Outline: Get favorited elements of a subfolder Given using DAV path And user "Alice" has created folder "/subfolder" @@ -125,8 +126,8 @@ Feature: favorite | old | | new | - @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @files_sharing-app-required @toImplementOnOCIS + @skipOnOcis @issue-ocis-reva-39 Scenario Outline: moving a favorite file out of a share keeps favorite state Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -142,8 +143,8 @@ Feature: favorite | old | | new | - @issue-33840 - @skipOnOcis @issue-ocis-reva-21 + @issue-33840 @toImplementOnOCIS + @skipOnOcis @issue-ocis-reva-39 Scenario Outline: Get favorited elements and limit count of entries Given using DAV path And user "Alice" has favorited element "/textfile0.txt" @@ -164,8 +165,8 @@ Feature: favorite | old | | new | - @issue-33840 - @skipOnOcis @issue-ocis-reva-21 + @issue-33840 @toImplementOnOCIS + @skipOnOcis @issue-ocis-reva-39 Scenario Outline: Get favorited elements paginated in subfolder Given using DAV path And user "Alice" has created folder "/subfolder" @@ -194,8 +195,8 @@ Feature: favorite | old | | new | - @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @files_sharing-app-required @toImplementOnOCIS + @skipOnOcis @issue-ocis-reva-39 Scenario Outline: sharer file favorite state should not change the favorite state of sharee Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -209,8 +210,8 @@ Feature: favorite | old | | new | - @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @files_sharing-app-required @toImplementOnOCIS + @skipOnOcis @issue-ocis-reva-243 Scenario Outline: sharee file favorite state should not change the favorite state of sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiMain/checksums.feature b/tests/acceptance/features/apiMain/checksums.feature index fbb9be3df3e0..d6eddd1b0dd7 100644 --- a/tests/acceptance/features/apiMain/checksums.feature +++ b/tests/acceptance/features/apiMain/checksums.feature @@ -60,7 +60,7 @@ Feature: checksums | old | | new | - @skipOnOcis @issue-ocis-reva-98 @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-98 Scenario: Downloading a file with checksum should return the checksum in the download header Given using old DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" diff --git a/tests/acceptance/features/apiShareManagementBasic/createShare.feature b/tests/acceptance/features/apiShareManagementBasic/createShare.feature index a47e509c9834..e12a3d64561d 100644 --- a/tests/acceptance/features/apiShareManagementBasic/createShare.feature +++ b/tests/acceptance/features/apiShareManagementBasic/createShare.feature @@ -317,7 +317,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243 + @skipOnOcis @issue-ocis-reva-372 @issue-ocis-reva-243 @toImplementOnOCIS Scenario Outline: sharing subfolder of already shared folder, GET result is correct Given using OCS API version "" And these users have been created with default attributes and without skeleton files: @@ -347,6 +347,39 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + @skipOnOcV10 @issue-ocis-reva-372 @issue-ocis-reva-243 + #after fixing all issues delete this Scenario and use the one above + Scenario Outline: sharing subfolder of already shared folder, GET result is correct + Given using OCS API version "" + And these users have been created with default attributes and without skeleton files: + | username | + | Brian | + | Carol | + | David | + | Emily | + And user "Alice" has created folder "/folder1" + And user "Alice" has shared folder "/folder1" with user "Brian" + And user "Alice" has shared folder "/folder1" with user "Carol" + And user "Alice" has created folder "/folder1/folder2" + And user "Alice" has shared folder "/folder1/folder2" with user "David" + And user "Alice" has shared folder "/folder1/folder2" with user "Emily" + When user "Alice" sends HTTP method "GET" to OCS API endpoint "/apps/files_sharing/api/v1/shares" + Then the OCS status code should be "" + And the HTTP status code should be "200" + And the response should contain 4 entries + And folder "/folder1" should be included as path in the response + And folder "/folder2" should be included as path in the response +# And folder "/folder1/folder2" should be included as path in the response + And user "Alice" sends HTTP method "GET" to OCS API endpoint "/apps/files_sharing/api/v1/shares?path=/folder1/folder2" + And the response should contain 2 entries + And folder "/folder1" should not be included as path in the response + And folder "/folder2" should be included as path in the response +# And folder "/folder1/folder2" should be included as path in the response + Examples: + | ocs_api_version | ocs_status_code | + | 1 | 100 | + | 2 | 200 | + @skipOnOcis @issue-ocis-reva-14 @issue-ocis-reva-243 Scenario Outline: user shares a file with file name longer than 64 chars to another user Given using OCS API version "" @@ -361,7 +394,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243 + @skipOnOcis @issue-ocis-reva-34 @issue-ocis-reva-243 @toImplementOnOCIS Scenario Outline: user shares a file with file name longer than 64 chars to a group Given using OCS API version "" And group "grp1" has been created @@ -392,7 +425,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243 @issue-ocis-reva-12 + @skipOnOcis @issue-ocis-reva-34 @issue-ocis-reva-243 @issue-ocis-reva-12 @toImplementOnOCIS Scenario Outline: user shares a folder with folder name longer than 64 chars to a group Given using OCS API version "" And group "grp1" has been created @@ -446,7 +479,7 @@ Feature: sharing | /randomfile.txt | And the content of file "randomfile.txt" for user "Brian" should be "Random data" - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-34 @toImplementOnOCIS Scenario Outline: Share of folder to a group with emoji in the name Given using OCS API version "" And these users have been created with default attributes and without skeleton files: @@ -529,7 +562,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @skipOnOcis @issue-ocis-reva-21 @skipOnFilesClassifier @issue-files-classifier-291 @issue-ocis-reva-243 + @skipOnOcis @issue-ocis-reva-34 @skipOnFilesClassifier @issue-files-classifier-291 @issue-ocis-reva-243 @toImplementOnOCIS Scenario: Share a file by multiple channels and download from sub-folder and direct file share Given these users have been created with default attributes and without skeleton files: | username | diff --git a/tests/acceptance/features/apiShareOperations/accessToShare.feature b/tests/acceptance/features/apiShareOperations/accessToShare.feature index 1aaca6f8ee91..d06586917dee 100644 --- a/tests/acceptance/features/apiShareOperations/accessToShare.feature +++ b/tests/acceptance/features/apiShareOperations/accessToShare.feature @@ -34,7 +34,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243 + @smokeTest @skipOnOcis @issue-ocis-reva-260 Scenario Outline: Sharee can't see the share that is filtered out Given using OCS API version "" And user "Alice" has shared file "textfile0.txt" with user "Brian" @@ -48,7 +48,22 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243 + @smokeTest @skipOnOcV10 @issue-ocis-reva-260 + #after fixing the issues delete this Scenario and use the one above + Scenario Outline: Sharee can't see the share that is filtered out + Given using OCS API version "" + And user "Alice" has shared file "textfile0.txt" with user "Brian" + And user "Alice" has shared file "textfile1.txt" with user "Brian" + When user "Brian" gets all the shares shared with him that are received as file "textfile0 (2).txt" using the provisioning API + Then the OCS status code should be "" + And the HTTP status code should be "200" + And the last share_id should be included in the response + Examples: + | ocs_api_version | ocs_status_code | + | 1 | 100 | + | 2 | 200 | + + @smokeTest @skipOnOcis @issue-ocis-reva-34 @issue-ocis-reva-194 Scenario Outline: Sharee can see the group share Given using OCS API version "" And group "grp1" has been created diff --git a/tests/acceptance/features/apiShareOperations/gettingShares.feature b/tests/acceptance/features/apiShareOperations/gettingShares.feature index bbdf9fb8ecda..5aef6f900a87 100644 --- a/tests/acceptance/features/apiShareOperations/gettingShares.feature +++ b/tests/acceptance/features/apiShareOperations/gettingShares.feature @@ -54,7 +54,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @skipOnOcis @smokeTest @issue-ocis-reva-243 @issue-ocis-reva-21 + @skipOnOcis @smokeTest @issue-ocis-reva-243 Scenario Outline: getting all shares of a file with reshares Given using OCS API version "" And these users have been created with default attributes and skeleton files: @@ -155,7 +155,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-374 Scenario Outline: Get a share with a user that didn't receive the share Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files @@ -168,6 +168,21 @@ Feature: sharing | 1 | 200 | | 2 | 404 | + @skipOnOcV10 @issue-ocis-reva-374 + #after fixing all issues delete this Scenario and use the one above + Scenario Outline: Get a share with a user that didn't receive the share + Given using OCS API version "" + And user "Carol" has been created with default attributes and without skeleton files + And user "Alice" has shared file "textfile0.txt" with user "Brian" + When user "Carol" gets the info of the last share using the sharing API + Then the OCS status code should be "400" +# Then the OCS status code should be "404" + And the HTTP status code should be "" + Examples: + | ocs_api_version | http_status_code | + | 1 | 200 | + | 2 | 400 | + @skipOnLDAP @skipOnOcis @issue-ocis-reva-194 Scenario: Share of folder to a group, remove user from that group Given using OCS API version "1" @@ -191,7 +206,7 @@ Feature: sharing | /PARENT%20(2)/ | | /PARENT%20(2)/parent.txt | - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-372 Scenario Outline: getting all the shares inside the folder Given using OCS API version "" And user "Alice" has shared file "PARENT/parent.txt" with user "Brian" @@ -203,3 +218,17 @@ Feature: sharing | ocs_api_version | ocs_status_code | | 1 | 100 | | 2 | 200 | + + @skipOnOcV10 @issue-ocis-reva-372 + #after fixing all issues delete this Scenario and use the one above + Scenario Outline: getting all the shares inside the folder + Given using OCS API version "" + And user "Alice" has shared file "PARENT/parent.txt" with user "Brian" + When user "Alice" gets all the shares inside the folder "PARENT/parent.txt" using the sharing API + Then the OCS status code should be "" + And the HTTP status code should be "200" + And file "parent.txt" should be included in the response + Examples: + | ocs_api_version | ocs_status_code | + | 1 | 100 | + | 2 | 200 | diff --git a/tests/acceptance/features/apiVersions/fileVersions.feature b/tests/acceptance/features/apiVersions/fileVersions.feature index 3e74eff4740f..d7819fa590b4 100644 --- a/tests/acceptance/features/apiVersions/fileVersions.feature +++ b/tests/acceptance/features/apiVersions/fileVersions.feature @@ -159,7 +159,7 @@ Feature: dav-versions Then the version folder of fileId "<>" for user "Brian" should contain "1" element @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharer of a file can see the old version information when the sharee changes the content of the file Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "First content" to "sharefile.txt" @@ -169,7 +169,19 @@ Feature: dav-versions And the version folder of file "/sharefile.txt" for user "Alice" should contain "1" element @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcV10 @issue-ocis-reva-243 + #after fixing all issues delete this Scenario and use the one above + Scenario: sharer of a file can see the old version information when the sharee changes the content of the file + Given user "Brian" has been created with default attributes and without skeleton files + And user "Alice" has uploaded file with content "First content" to "sharefile.txt" + And user "Alice" has shared file "sharefile.txt" with user "Brian" + When user "Brian" has uploaded file with content "Second content" to "/sharefile.txt" + Then the HTTP status code should be "201" + And the version folder of file "/sharefile.txt" for user "Alice" should contain "0" element +# And the version folder of file "/sharefile.txt" for user "Alice" should contain "1" element + + @files_sharing-app-required + @skipOnOcis @issue-ocis-reva-243 Scenario: sharer of a file can restore the original content of a shared file after the file has been modified by the sharee Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "First content" to "sharefile.txt" @@ -181,7 +193,22 @@ Feature: dav-versions And the content of file "/sharefile.txt" for user "Brian" should be "First content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcV10 @issue-ocis-reva-243 + #after fixing all issues delete this Scenario and use the one above + Scenario: sharer of a file can restore the original content of a shared file after the file has been modified by the sharee + Given user "Brian" has been created with default attributes and without skeleton files + And user "Alice" has uploaded file with content "First content" to "sharefile.txt" + And user "Alice" has shared file "sharefile.txt" with user "Brian" + And user "Brian" has uploaded file with content "Second content" to "/sharefile.txt" + When user "Alice" restores version index "0" of file "/sharefile.txt" using the WebDAV API +# When user "Alice" restores version index "1" of file "/sharefile.txt" using the WebDAV API + Then the HTTP status code should be "201" + And the content of file "/sharefile.txt" for user "Alice" should be "First content" + And the content of file "/sharefile.txt" for user "Brian" should be "Second content" +# And the content of file "/sharefile.txt" for user "Brian" should be "First content" + + @files_sharing-app-required + @skipOnOcis @issue-ocis-reva-243 Scenario: sharer can restore a file inside a shared folder modified by sharee Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/sharingfolder" @@ -194,7 +221,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Brian" should be "First content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharee can restore a file inside a shared folder modified by sharee Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/sharingfolder" @@ -207,7 +234,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Brian" should be "First content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharer can restore a file inside a shared folder created by sharee and modified by sharer Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/sharingfolder" @@ -220,7 +247,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Brian" should be "First content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharee can restore a file inside a shared folder created by sharee and modified by sharer Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/sharingfolder" @@ -233,7 +260,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Brian" should be "First content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharer can restore a file inside a shared folder created by sharee and modified by sharee Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/sharingfolder" @@ -246,7 +273,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Brian" should be "old content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharee can restore a file inside a shared folder created by sharer and modified by sharer Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/sharingfolder" @@ -259,7 +286,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Brian" should be "old content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharee can restore a file inside a shared folder created by sharer and modified by sharer, when the folder has been moved by the sharee Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/sharingfolder" @@ -274,7 +301,7 @@ Feature: dav-versions And the content of file "/received/sharingfolder/sharefile.txt" for user "Brian" should be "old content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharee can restore a shared file created and modified by sharer, when the file has been moved by the sharee (file is at the top level of the sharer) Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "old content" to "/sharefile.txt" @@ -288,7 +315,7 @@ Feature: dav-versions And the content of file "/received/sharefile.txt" for user "Brian" should be "old content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 Scenario: sharee can restore a shared file created and modified by sharer, when the file has been moved by the sharee (file is inside a folder of the sharer) Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/sharingfolder" @@ -303,7 +330,7 @@ Feature: dav-versions And the content of file "/received/sharefile.txt" for user "Brian" should be "old content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-34 Scenario: sharer can restore a file inside a group shared folder modified by sharee Given user "Brian" has been created with default attributes and without skeleton files And user "Carol" has been created with default attributes and without skeleton files @@ -322,7 +349,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Carol" should be "First content" @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-243 @issue-ocis-reva-386 Scenario Outline: Moving a file (with versions) into a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -350,7 +377,37 @@ Feature: dav-versions | new | Brian | @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcV10 @issue-ocis-reva-243 @issue-ocis-reva-386 + #after fixing all issues delete this Scenario and use the one above + Scenario Outline: Moving a file (with versions) into a shared folder as the sharee and as the sharer + Given using DAV path + And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has created folder "/testshare" + And user "Brian" has created a share with settings + | path | testshare | + | shareType | user | + | permissions | change | + | shareWith | Alice | + And user "Brian" has uploaded file with content "test data 1" to "/testfile.txt" + And user "Brian" has uploaded file with content "test data 2" to "/testfile.txt" + And user "Brian" has uploaded file with content "test data 3" to "/testfile.txt" + And user "Brian" moves file "/testfile.txt" to "/testshare/testfile.txt" using the WebDAV API + Then the HTTP status code should be "201" + And the content of file "/testshare/testfile.txt" for user "Alice" should be "" +# And the content of file "/testshare/testfile.txt" for user "Alice" should be "test data 3" + And the content of file "/testshare/testfile.txt" for user "Brian" should be "test data 3" + And as "Brian" file "/testfile.txt" should not exist + And as "Alice" file "/testshare/testfile.txt" should not exist + And the content of file "/testshare/testfile.txt" for user "Brian" should be "test data 3" +# And the version folder of file "/testshare/testfile.txt" for user "Alice" should contain "2" elements +# And the version folder of file "/testshare/testfile.txt" for user "Brian" should contain "2" elements + Examples: + | dav_version | + | old | + | new | + + @files_sharing-app-required + @skipOnOcis @issue-ocis-reva-243 @issue-ocis-reva-386 Scenario Outline: Moving a file (with versions) out of a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -376,8 +433,34 @@ Feature: dav-versions | old | Brian | | new | Brian | + @files_sharing-app-required + @skipOnOcV10 @issue-ocis-reva-243 @issue-ocis-reva-386 + #after fixing all issues delete this Scenario and use the one above + Scenario Outline: Moving a file (with versions) out of a shared folder as the sharee and as the sharer + Given using DAV path + And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has created folder "/testshare" + And user "Brian" has uploaded file with content "test data 1" to "/testshare/testfile.txt" + And user "Brian" has uploaded file with content "test data 2" to "/testshare/testfile.txt" + And user "Brian" has uploaded file with content "test data 3" to "/testshare/testfile.txt" + And user "Brian" has created a share with settings + | path | testshare | + | shareType | user | + | permissions | change | + | shareWith | Alice | + When user "Brian" moves file "/testshare/testfile.txt" to "/testfile.txt" 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 3" + And as "Alice" file "/testshare/testfile.txt" should not exist + And as "Brian" file "/testshare/testfile.txt" should not exist +# And the version folder of file "/testfile.txt" for user "Brian" should contain "2" elements + Examples: + | dav_version | + | old | + | new | + @skipOnOcV10.3.0 @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-382 Scenario: Receiver tries to get file versions of unshared file from the sharer Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" @@ -387,8 +470,21 @@ Feature: dav-versions Then the HTTP status code should be "404" Then the value of the item "//s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound" + @skipOnOcV10.3.0 @files_sharing-app-required + @skipOnOcV10 @issue-ocis-reva-382 + #after fixing all issues delete this Scenario and use the one above + Scenario: Receiver tries to get file versions of unshared file from the sharer + Given user "Brian" has been created with default attributes and without skeleton files + And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" + And user "Alice" has uploaded file with content "textfile1" to "textfile1.txt" + And user "Alice" has shared file "textfile0.txt" with user "Brian" + When user "Brian" tries to get versions of file "textfile1.txt" from "Alice" + Then the HTTP status code should be "207" +# Then the HTTP status code should be "404" +# Then the value of the item "//s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound" + @skipOnStorage:ceph @files_primary_s3-issue-161 @files_sharing-app-required - @skipOnOcis @issue-ocis-reva-21 + @skipOnOcis @issue-ocis-reva-376 Scenario: Receiver tries get file versions of shared file from the sharer Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" @@ -399,3 +495,18 @@ Feature: dav-versions When user "Brian" tries to get versions of file "textfile0.txt" from "Alice" Then the HTTP status code should be "207" And the number of versions should be "3" + + @skipOnStorage:ceph @files_primary_s3-issue-161 @files_sharing-app-required + @skipOnOcV10 @issue-ocis-reva-376 + #after fixing all issues delete this Scenario and use the one above + Scenario: Receiver tries get file versions of shared file from the sharer + Given user "Brian" has been created with default attributes and without skeleton files + And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" + And user "Alice" has uploaded file with content "version 1" to "textfile0.txt" + And user "Alice" has uploaded file with content "version 2" to "textfile0.txt" + And user "Alice" has uploaded file with content "version 3" to "textfile0.txt" + And user "Alice" has shared file "textfile0.txt" with user "Brian" + When user "Brian" tries to get versions of file "textfile0.txt" from "Alice" + Then the HTTP status code should be "207" + And the number of versions should be "4" +# And the number of versions should be "3"