diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature index e57d9cb2fd91..3f654ac014f1 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature @@ -8,6 +8,7 @@ Feature: cannot share resources with invalid permissions And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has created folder "/PARENT" + Scenario Outline: Cannot create a share of a file or folder with invalid permissions Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiShareManagementBasicToRoot/createShareFromLocalStorageToRootFolder.feature b/tests/acceptance/features/apiShareManagementBasicToRoot/createShareFromLocalStorageToRootFolder.feature index e2fbe7da7891..154b87c8e4fc 100644 --- a/tests/acceptance/features/apiShareManagementBasicToRoot/createShareFromLocalStorageToRootFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToRoot/createShareFromLocalStorageToRootFolder.feature @@ -7,7 +7,6 @@ Feature: local-storage | Alice | | Brian | - @skipOnEncryptionType:user-keys @encryption-issue-181 Scenario Outline: Share a file inside a local external storage Given using OCS API version "" diff --git a/tests/acceptance/features/apiShareManagementBasicToRoot/createShareToRootFolder.feature b/tests/acceptance/features/apiShareManagementBasicToRoot/createShareToRootFolder.feature index 75740eb06abd..8c4a31539607 100644 --- a/tests/acceptance/features/apiShareManagementBasicToRoot/createShareToRootFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToRoot/createShareToRootFolder.feature @@ -4,8 +4,7 @@ Feature: sharing Background: Given user "Alice" has been created with default attributes and without skeleton files - @smokeTest - @skipOnEncryptionType:user-keys @issue-32322 @skipOnOcV10.8 @skipOnOcV10.9.0 @skipOnOcV10.9.1 + @smokeTest @skipOnEncryptionType:user-keys @issue-32322 @skipOnOcV10.8 @skipOnOcV10.9.0 @skipOnOcV10.9.1 Scenario Outline: Creating a share of a file with a user, the default permissions are read(1)+update(2)+can-share(16) Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -32,8 +31,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest - @skipOnEncryptionType:user-keys @issue-32322 + @smokeTest @skipOnEncryptionType:user-keys @issue-32322 Scenario Outline: Creating a share of a file containing commas in the filename, with a user, the default permissions are read(1)+update(2)+can-share(16) Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -59,6 +57,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: Creating a share of a file with a user and asking for various permission combinations Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -93,6 +92,7 @@ Feature: sharing | 1 | 2 | 2 | 100 | | 2 | 2 | 2 | 200 | + Scenario Outline: Creating a share of a file with no permissions should fail Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -106,6 +106,7 @@ Feature: sharing | 1 | 200 | | 2 | 400 | + Scenario Outline: Creating a share of a folder with no permissions should fail Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -119,6 +120,7 @@ Feature: sharing | 1 | 200 | | 2 | 400 | + Scenario Outline: Creating a share of a folder with a user, the default permissions are all permissions(31) Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -143,6 +145,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: Creating a share of a file with a group, the default permissions are read(1)+update(2)+can-share(16) Given using OCS API version "" And group "grp1" has been created @@ -167,6 +170,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: Creating a share of a folder with a group, the default permissions are all permissions(31) Given using OCS API version "" And group "grp1" has been created @@ -219,6 +223,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: sharing again an own file while belonging to a group Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -235,6 +240,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + 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: @@ -266,6 +272,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: user shares a file with file name longer than 64 chars to another user Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -280,6 +287,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + 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 @@ -296,6 +304,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: user shares a folder with folder name longer than 64 chars to another user Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -311,6 +320,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + 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 @@ -362,6 +372,7 @@ Feature: sharing | /randomfile.txt | And the content of file "randomfile.txt" for user "Brian" should be "Random data" + 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: @@ -469,6 +480,7 @@ Feature: sharing | /common/sub/textfile0.txt | | /textfile0.txt | + Scenario Outline: sharing back to resharer is not allowed Given using OCS API version "" And these users have been created with default attributes and without skeleton files: @@ -488,6 +500,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | + Scenario Outline: sharing back to original sharer is not allowed Given using OCS API version "" And these users have been created with default attributes and without skeleton files: @@ -529,6 +542,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | + Scenario Outline: shares to a deleted user should not be listed as shares for the sharer Given using OCS API version "" And these users have been created with default attributes and without skeleton files: diff --git a/tests/acceptance/features/apiShareManagementBasicToRoot/deleteShareFromRoot.feature b/tests/acceptance/features/apiShareManagementBasicToRoot/deleteShareFromRoot.feature index 4f141b0ec33e..ffdc7eb86154 100644 --- a/tests/acceptance/features/apiShareManagementBasicToRoot/deleteShareFromRoot.feature +++ b/tests/acceptance/features/apiShareManagementBasicToRoot/deleteShareFromRoot.feature @@ -7,6 +7,7 @@ Feature: sharing | Alice | | Brian | + Scenario Outline: Delete all group shares Given using OCS API version "" And group "grp1" has been created @@ -36,6 +37,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario: orphaned shares Given using OCS API version "1" And user "Alice" has created folder "/common" @@ -93,6 +95,7 @@ Feature: sharing And the etag of element "/" of user "Brian" should have changed And the etag of element "/PARENT" of user "Carol" should not have changed + Scenario: sharee of a read-only share folder tries to delete the shared folder Given using OCS API version "1" And user "Alice" has created folder "/shared" @@ -102,6 +105,7 @@ Feature: sharing Then the HTTP status code should be "403" And as "Brian" file "/shared/shared_file.txt" should exist + Scenario: sharee of a upload-only shared folder tries to delete a file in the shared folder Given using OCS API version "1" And user "Alice" has created folder "/shared" @@ -111,6 +115,7 @@ Feature: sharing Then the HTTP status code should be "403" And as "Alice" file "/shared/shared_file.txt" should exist + Scenario: sharee of an upload-only shared folder tries to delete their file in the folder Given using OCS API version "1" And user "Alice" has created folder "/shared" @@ -120,6 +125,7 @@ Feature: sharing Then the HTTP status code should be "403" And as "Alice" file "/shared/textfile.txt" should exist + Scenario Outline: A Group share recipient tries to delete the share Given using OCS API version "" And group "grp1" has been created @@ -144,6 +150,7 @@ Feature: sharing | /PARENT | 1 | 200 | PARENT | | /PARENT | 2 | 404 | PARENT | + Scenario Outline: An individual share recipient tries to delete the share Given using OCS API version "" And user "Alice" has created folder "PARENT" @@ -161,6 +168,7 @@ Feature: sharing | /PARENT | 1 | 200 | PARENT | | /PARENT | 2 | 404 | PARENT | + Scenario Outline: delete a share with wrong authentication Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt" diff --git a/tests/acceptance/features/apiShareManagementBasicToRoot/excludeGroupFromReceivingShares.feature b/tests/acceptance/features/apiShareManagementBasicToRoot/excludeGroupFromReceivingShares.feature index 1283631a56be..ca5ef40231d3 100644 --- a/tests/acceptance/features/apiShareManagementBasicToRoot/excludeGroupFromReceivingShares.feature +++ b/tests/acceptance/features/apiShareManagementBasicToRoot/excludeGroupFromReceivingShares.feature @@ -16,6 +16,7 @@ Feature: Exclude groups from receiving shares And user "Brian" has been added to group "grp1" And user "David" has been added to group "grp2" + Scenario Outline: user cannot share with a group that is excluded from receiving shares but can share with other groups Given using OCS API version "" And user "Alice" has created folder "PARENT" @@ -40,6 +41,7 @@ Feature: Exclude groups from receiving shares | 1 | 200 | | 2 | 403 | + Scenario Outline: exclude multiple groups from receiving shares stops the user to share with any of them Given using OCS API version "" And user "Alice" has created folder "PARENT" @@ -70,6 +72,7 @@ Feature: Exclude groups from receiving shares | 1 | 200 | | 2 | 403 | + Scenario Outline: user cannot reshare a received share with a group that is excluded from receiving shares but can share with other groups Given using OCS API version "" And user "Carol" has created folder "PARENT" @@ -96,6 +99,7 @@ Feature: Exclude groups from receiving shares | 1 | 200 | | 2 | 403 | + Scenario Outline: sharing with a user that is part of a group that is excluded from receiving shares still works Given using OCS API version "" And user "Alice" has created folder "PARENT" @@ -114,6 +118,7 @@ Feature: Exclude groups from receiving shares | 1 | 100 | | 2 | 200 | + Scenario Outline: sharing with a user that is part of a group that is excluded from receiving shares using an other group works Given using OCS API version "" And user "Alice" has created folder "PARENT" @@ -134,6 +139,7 @@ Feature: Exclude groups from receiving shares | 1 | 100 | | 2 | 200 | + Scenario Outline: a user that is part of a group that is excluded from receiving shares still can initiate shares Given using OCS API version "" And user "Brian" has created folder "PARENT" diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/createShareFromLocalStorageToSharesFolder.feature b/tests/acceptance/features/apiShareManagementBasicToShares/createShareFromLocalStorageToSharesFolder.feature index 9feb2e8cdfd5..6f34fa077772 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/createShareFromLocalStorageToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/createShareFromLocalStorageToSharesFolder.feature @@ -9,7 +9,6 @@ Feature: local-storage | Alice | | Brian | - @skipOnEncryptionType:user-keys @encryption-issue-181 Scenario Outline: Share a file inside a local external storage Given using OCS API version "" diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature index 20909ee8f771..91d6b8b37e58 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature @@ -6,8 +6,7 @@ Feature: sharing And auto-accept shares has been disabled And user "Alice" has been created with default attributes and without skeleton files - @smokeTest @skipOnOcV10.8 @skipOnOcV10.9.0 @skipOnOcV10.9.1 - @skipOnEncryptionType:user-keys @issue-32322 + @smokeTest @skipOnOcV10.8 @skipOnOcV10.9.0 @skipOnOcV10.9.1 @skipOnEncryptionType:user-keys @issue-32322 Scenario Outline: Creating a share of a file with a user, the default permissions are read(1)+update(2)+can-share(16) Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -37,8 +36,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @skipOnOcV10.6 @skipOnOcV10.7 @skipOnOcV10.8.0 - @skipOnEncryptionType:user-keys @issue-32322 @issue-ocis-2133 + @smokeTest @skipOnOcV10.6 @skipOnOcV10.7 @skipOnOcV10.8.0 @skipOnEncryptionType:user-keys @issue-32322 @issue-ocis-2133 Scenario Outline: Creating a share of a file containing commas in the filename, with a user, the default permissions are read(1)+update(2)+can-share(16) Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -102,6 +100,7 @@ Feature: sharing | 1 | 2 | 2 | 100 | | 2 | 2 | 2 | 200 | + Scenario Outline: Creating a share of a file with no permissions should fail Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -117,6 +116,7 @@ Feature: sharing | 1 | 200 | | 2 | 400 | + Scenario Outline: Creating a share of a folder with no permissions should fail Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -274,7 +274,6 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @skipOnOcV10.6 @skipOnOcV10.7 @skipOnOcV10.8.0 Scenario Outline: sharing again an own file while belonging to a group Given using OCS API version "" @@ -535,7 +534,6 @@ Feature: sharing | 1 | 100 | /textfile0.txt | | 2 | 200 | /textfile0.txt | - @skipOnFilesClassifier @issue-files-classifier-291 @issue-ocis-2146 @skipOnOcV10.6 @skipOnOcV10.7 @skipOnOcV10.8.0 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: diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature b/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature index 846d0427e65e..a035862af9cb 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature @@ -10,6 +10,7 @@ Feature: sharing | Brian | And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" + Scenario Outline: Delete all group shares Given using OCS API version "" And group "grp1" has been created @@ -43,6 +44,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: orphaned shares Given using OCS API version "1" And user "Alice" has created folder "/common" @@ -136,6 +138,7 @@ Feature: sharing And as "Alice" file "/shared/shared_file.txt" should exist And as "Brian" file "/Shares/shared/shared_file.txt" should exist + Scenario: sharee of a upload-only shared folder tries to delete a file in the shared folder Given using OCS API version "1" And user "Alice" has created folder "/shared" @@ -148,6 +151,7 @@ Feature: sharing # Note: for Brian, the file does not "exist" because he only has "create" permission, not "read" And as "Brian" file "/Shares/shared/shared_file.txt" should not exist + Scenario: sharee of an upload-only shared folder tries to delete their file in the folder Given using OCS API version "1" And user "Alice" has created folder "/shared" @@ -160,6 +164,7 @@ Feature: sharing # Note: for Brian, the file does not "exist" because he only has "create" permission, not "read" And as "Brian" file "/Shares/shared/textfile.txt" should not exist + Scenario Outline: A Group share recipient tries to delete the share Given using OCS API version "" And group "grp1" has been created @@ -195,6 +200,7 @@ Feature: sharing | /shared | 1 | 200 | /Shares/shared | /shared | | /shared | 2 | 404 | /Shares/shared | /shared | + Scenario Outline: An individual share recipient tries to delete the share Given using OCS API version "" And user "Alice" has created folder "/shared" diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature b/tests/acceptance/features/apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature index 928b85189ef1..df3bbcdfd9a4 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature @@ -108,6 +108,7 @@ Feature: Exclude groups from receiving shares | 1 | 200 | | 2 | 403 | + Scenario Outline: sharing with a user that is part of a group that is excluded from receiving shares still works Given using OCS API version "" And user "Alice" has created folder "PARENT" @@ -128,6 +129,7 @@ Feature: Exclude groups from receiving shares | 1 | 100 | | 2 | 200 | + Scenario Outline: sharing with a user that is part of a group that is excluded from receiving shares using an other group works Given using OCS API version "" And group "grp3" has been created @@ -150,6 +152,7 @@ Feature: Exclude groups from receiving shares | 1 | 100 | | 2 | 200 | + Scenario Outline: a user that is part of a group that is excluded from receiving shares still can initiate shares Given using OCS API version "" And user "Brian" has created folder "PARENT" diff --git a/tests/acceptance/features/apiShareManagementToRoot/disableSharing.feature b/tests/acceptance/features/apiShareManagementToRoot/disableSharing.feature index e6dc85e9c9d2..f851abb62d26 100644 --- a/tests/acceptance/features/apiShareManagementToRoot/disableSharing.feature +++ b/tests/acceptance/features/apiShareManagementToRoot/disableSharing.feature @@ -23,6 +23,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | + Scenario Outline: user tries to share a folder with another user when the sharing api has been disabled Given using OCS API version "" And user "Alice" has created folder "/FOLDER" @@ -35,6 +36,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | + Scenario Outline: user tries to share a file with group when the sharing api has been disabled Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt" @@ -49,6 +51,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | + Scenario Outline: user tries to share a folder with group when the sharing api has been disabled Given using OCS API version "" And user "Alice" has created folder "/FOLDER" @@ -63,6 +66,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | + Scenario Outline: user tries to create public link share of a file when the sharing api has been disabled Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt" @@ -103,6 +107,7 @@ Feature: sharing | 1 | 200 | | 2 | 403 | + Scenario Outline: user shares a file with user who is in their group when sharing outside the group has been restricted Given using OCS API version "" And group "grp1" has been created @@ -119,6 +124,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: user shares a file with the group they are not member of when sharing outside the group has been restricted Given using OCS API version "" And group "grp2" has been created @@ -151,6 +157,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | + Scenario Outline: user who is a member of a group tries to share a file in the group when group sharing has been disabled Given using OCS API version "" And group "grp1" has been created diff --git a/tests/acceptance/features/apiShareManagementToRoot/mergeShare.feature b/tests/acceptance/features/apiShareManagementToRoot/mergeShare.feature index fbdd1e1ba31b..466572d8ba28 100644 --- a/tests/acceptance/features/apiShareManagementToRoot/mergeShare.feature +++ b/tests/acceptance/features/apiShareManagementToRoot/mergeShare.feature @@ -20,6 +20,7 @@ Feature: sharing And as "Brian" folder "/merge-test-outside" should exist And as "Brian" folder "/merge-test-outside (2)" should not exist + Scenario: Merging shares for recipient when shared from outside with group and member with different permissions Given user "Alice" has created folder "/merge-test-outside-perms" When user "Alice" shares folder "/merge-test-outside-perms" with group "grp1" with permissions "read" using the sharing API @@ -29,6 +30,7 @@ Feature: sharing And as user "Brian" folder "/merge-test-outside-perms" should contain a property "oc:permissions" with value "SRDNVCK" And as "Brian" folder "/merge-test-outside-perms (2)" should not exist + Scenario: Merging shares for recipient when shared from outside with two groups Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -40,6 +42,7 @@ Feature: sharing And as "Brian" folder "/merge-test-outside-twogroups" should exist And as "Brian" folder "/merge-test-outside-twogroups (2)" should not exist + Scenario: Merging shares for recipient when shared from outside with two groups with different permissions Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -51,6 +54,7 @@ Feature: sharing And as user "Brian" folder "/merge-test-outside-twogroups-perms" should contain a property "oc:permissions" with value "SRDNVCK" And as "Brian" folder "/merge-test-outside-twogroups-perms (2)" should not exist + Scenario: Merging shares for recipient when shared from outside with two groups and member Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -63,6 +67,7 @@ Feature: sharing And as user "Brian" folder "/merge-test-outside-twogroups-member-perms" should contain a property "oc:permissions" with value "SRDNVCK" And as "Brian" folder "/merge-test-outside-twogroups-member-perms (2)" should not exist + Scenario: Merging shares for recipient when shared from inside with group Given user "Brian" has created folder "/merge-test-inside-group" When user "Brian" shares folder "/merge-test-inside-group" with group "grp1" using the sharing API @@ -71,6 +76,7 @@ Feature: sharing And as "Brian" folder "/merge-test-inside-group" should exist And as "Brian" folder "/merge-test-inside-group (2)" should not exist + Scenario: Merging shares for recipient when shared from inside with two groups Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -83,6 +89,7 @@ Feature: sharing And as "Brian" folder "/merge-test-inside-twogroups (2)" should not exist And as "Brian" folder "/merge-test-inside-twogroups (3)" should not exist + Scenario: Merging shares for recipient when shared from inside with group with less permissions Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -95,6 +102,7 @@ Feature: sharing And as "Brian" folder "/merge-test-inside-twogroups-perms (2)" should not exist And as "Brian" folder "/merge-test-inside-twogroups-perms (3)" should not exist + Scenario: Merging shares for recipient when shared from outside with group then user and recipient renames in between Given user "Alice" has created folder "/merge-test-outside-groups-renamebeforesecondshare" When user "Alice" shares folder "/merge-test-outside-groups-renamebeforesecondshare" with group "grp1" using the sharing API @@ -106,6 +114,7 @@ Feature: sharing And as user "Brian" folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" should contain a property "oc:permissions" with value "SRDNVCK" And as "Brian" folder "/merge-test-outside-groups-renamebeforesecondshare" should not exist + Scenario: Merging shares for recipient when shared from outside with user then group and recipient renames in between Given user "Alice" has created folder "/merge-test-outside-groups-renamebeforesecondshare" When user "Alice" shares folder "/merge-test-outside-groups-renamebeforesecondshare" with user "Brian" using the sharing API diff --git a/tests/acceptance/features/apiShareManagementToRoot/moveReceivedShare.feature b/tests/acceptance/features/apiShareManagementToRoot/moveReceivedShare.feature index 1c94ea47972a..eda9ca5561bc 100644 --- a/tests/acceptance/features/apiShareManagementToRoot/moveReceivedShare.feature +++ b/tests/acceptance/features/apiShareManagementToRoot/moveReceivedShare.feature @@ -9,6 +9,7 @@ Feature: sharing | Brian | | Carol | + Scenario: Keep usergroup shares (#22143) Given group "grp1" has been created And user "Brian" has been added to group "grp1" @@ -23,6 +24,7 @@ Feature: sharing And user "Brian" should see the following elements | /myFOLDER/myTMP/ | + Scenario: keep user shared file name same after one of recipient has renamed the file Given user "Alice" has uploaded file with content "foo" to "/sharefile.txt" And user "Alice" has shared file "/sharefile.txt" with user "Brian" @@ -33,6 +35,7 @@ Feature: sharing And as "Alice" file "/sharefile.txt" should exist And as "Brian" file "/sharefile.txt" should exist + Scenario: keep user shared file directory same in respect to respective user if one of the recipient has moved the file Given user "Alice" has uploaded file with content "foo" to "/sharefile.txt" And user "Alice" has shared file "/sharefile.txt" with user "Brian" @@ -44,6 +47,7 @@ Feature: sharing And as "Alice" file "/sharefile.txt" should exist And as "Brian" file "/sharefile.txt" should exist + Scenario Outline: move folder inside received folder with special characters Given group "grp1" has been created And user "Carol" has been added to group "grp1" @@ -69,6 +73,7 @@ Feature: sharing | ?abc=oc # | ?abc=oc g%rp# | # oc?test=oc&a | | @a#8a=b?c=d | @a#8a=b?c=d grp | ?a#8 a=b?c=d | + Scenario: receiver renames a received share with share, read, change permissions Given user "Alice" has created folder "folderToShare" And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/folderToShare/fileInside" diff --git a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature index 4f0de54f4675..ddc968cee68d 100644 --- a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature +++ b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature @@ -299,7 +299,6 @@ Feature: accept/decline shares coming from internal users | pending_share_path_1 | pending_share_path_2 | | /PARENT/ | /textfile0.txt | - @issue-ocis-2131 @skipOnOcV10.6 @skipOnOcV10.7 @skipOnOcV10.8.0 Scenario: receive two shares with identical names from different users, accept one by one Given user "Alice" has created folder "/shared" @@ -576,7 +575,6 @@ Feature: accept/decline shares coming from internal users | declined_share_path | | /PARENT | - @issue-ocis-765 @issue-ocis-2131 @skipOnOcV10.6 @skipOnOcV10.7 @skipOnOcV10.8.0 Scenario: shares exist after restoring already shared file to a previous version And user "Alice" has uploaded file with content "Test Content." to "/toShareFile.txt" diff --git a/tests/acceptance/features/apiShareManagementToShares/acceptSharesToSharesFolder.feature b/tests/acceptance/features/apiShareManagementToShares/acceptSharesToSharesFolder.feature index fe5f07820d94..3f81ec190b5e 100644 --- a/tests/acceptance/features/apiShareManagementToShares/acceptSharesToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementToShares/acceptSharesToSharesFolder.feature @@ -14,6 +14,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder | Alice | | Brian | + Scenario: When accepting a share of a file, the received file is accessible Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt" And user "Alice" has shared file "/textfile0.txt" with user "Brian" @@ -22,6 +23,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder And the HTTP status code should be "200" And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0" + Scenario: When accepting a share of a folder, the received folder is accessible Given user "Alice" has created folder "/PARENT" And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt" diff --git a/tests/acceptance/features/apiShareManagementToShares/mergeShare.feature b/tests/acceptance/features/apiShareManagementToShares/mergeShare.feature index 1e17a833b91b..1a77f7c2d983 100644 --- a/tests/acceptance/features/apiShareManagementToShares/mergeShare.feature +++ b/tests/acceptance/features/apiShareManagementToShares/mergeShare.feature @@ -23,6 +23,7 @@ Feature: sharing And as "Brian" folder "/Shares/merge-test-outside" should exist And as "Brian" folder "/Shares/merge-test-outside (2)" should not exist + Scenario: Merging shares for recipient when shared from outside with group and member with different permissions Given user "Alice" has created folder "/merge-test-outside-perms" When user "Alice" shares folder "/merge-test-outside-perms" with group "grp1" with permissions "read" using the sharing API @@ -33,6 +34,7 @@ Feature: sharing And as user "Brian" folder "/Shares/merge-test-outside-perms" should contain a property "oc:permissions" with value "SRDNVCK" And as "Brian" folder "/Shares/merge-test-outside-perms (2)" should not exist + Scenario: Merging shares for recipient when shared from outside with two groups Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -45,6 +47,7 @@ Feature: sharing And as "Brian" folder "/Shares/merge-test-outside-twogroups" should exist And as "Brian" folder "/Shares/merge-test-outside-twogroups (2)" should not exist + Scenario: Merging shares for recipient when shared from outside with two groups with different permissions Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -57,6 +60,7 @@ Feature: sharing And as user "Brian" folder "/Shares/merge-test-outside-twogroups-perms" should contain a property "oc:permissions" with value "SRDNVCK" And as "Brian" folder "/Shares/merge-test-outside-twogroups-perms (2)" should not exist + Scenario: Merging shares for recipient when shared from outside with two groups and member Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -70,6 +74,7 @@ Feature: sharing And as user "Brian" folder "/Shares/merge-test-outside-twogroups-member-perms" should contain a property "oc:permissions" with value "SRDNVCK" And as "Brian" folder "/Shares/merge-test-outside-twogroups-member-perms (2)" should not exist + Scenario: Merging shares for recipient when shared from inside with group Given user "Brian" has created folder "/merge-test-inside-group" When user "Brian" shares folder "/merge-test-inside-group" with group "grp1" using the sharing API @@ -78,6 +83,7 @@ Feature: sharing And as "Brian" folder "/merge-test-inside-group" should exist And as "Brian" folder "/Shares/merge-test-inside-group" should not exist + Scenario: Merging shares for recipient when shared from inside with two groups Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -90,6 +96,7 @@ Feature: sharing And as "Brian" folder "/Shares/merge-test-inside-twogroups" should not exist And as "Brian" folder "/Shares/merge-test-inside-twogroups (2)" should not exist + Scenario Outline: Merging shares for recipient when shared from inside with group with less permissions Given group "grp2" has been created And user "Brian" has been added to group "grp2" @@ -110,6 +117,7 @@ Feature: sharing | expected_permission_1 | expected_permission_2 | | RDNVCK | RMDNVCK | + Scenario: Merging shares for recipient when shared from outside with group then user and recipient renames in between Given user "Alice" has created folder "/merge-test-outside-groups-renamebeforesecondshare" # Section 1: Brian receives and accepts the group share from Alice and moves and renames it out of the "Shares" folder @@ -129,6 +137,7 @@ Feature: sharing And as "Brian" folder "/Shares/merge-test-outside-groups-renamebeforesecondshare" should exist But as "Brian" folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" should not exist + Scenario: Merging shares for recipient when shared from outside with user then group and recipient renames in between Given user "Alice" has created folder "/merge-test-outside-groups-renamebeforesecondshare" # Section 1: Brian receives and accepts the user share from Alice and moves and renames it out of the "Shares" folder diff --git a/tests/acceptance/features/apiShareManagementToShares/moveReceivedShareFromLocalStorage.feature b/tests/acceptance/features/apiShareManagementToShares/moveReceivedShareFromLocalStorage.feature index 3379e6f018c1..13cf688b72b8 100644 --- a/tests/acceptance/features/apiShareManagementToShares/moveReceivedShareFromLocalStorage.feature +++ b/tests/acceptance/features/apiShareManagementToShares/moveReceivedShareFromLocalStorage.feature @@ -57,7 +57,6 @@ Feature: local-storage | 1 | /local_storage/foo | | 2 | /local_storage/foo | - @skipOnEncryptionType:user-keys @encryption-issue-181 Scenario Outline: sub-folders,file inside a renamed received folder shared from local storage are accessible Given using OCS API version "" @@ -90,7 +89,6 @@ Feature: local-storage | 1 | /local_storage/foo | | 2 | /local_storage/foo | - @skipOnEncryptionType:user-keys @encryption-issue-181 Scenario Outline: receiver renames a received file share from local storage in group sharing Given using OCS API version "" diff --git a/tests/acceptance/features/apiShareOperationsToRoot1/gettingShares.feature b/tests/acceptance/features/apiShareOperationsToRoot1/gettingShares.feature index 241ea14e0754..0256b0aae3e3 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot1/gettingShares.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot1/gettingShares.feature @@ -22,6 +22,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: getting all shares of a user using another user Given using OCS API version "" And user "Alice" has shared file "textfile0.txt" with user "Brian" @@ -134,6 +135,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | + Scenario Outline: getting all the shares inside the folder Given using OCS API version "" And user "Alice" has created folder "/PARENT" diff --git a/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesReceivedFiltered.feature b/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesReceivedFiltered.feature index 609d3a95f8cc..ab15d1218938 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesReceivedFiltered.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesReceivedFiltered.feature @@ -28,6 +28,7 @@ Feature: get the received shares filtered by type (user, group etc) | path | /fileToShareWithPublic.txt | | permissions | read | + Scenario Outline: getting shares received from users Given using OCS API version "" When user "Brian" gets the user shares shared with him using the sharing API @@ -41,6 +42,7 @@ Feature: get the received shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares received from groups Given using OCS API version "" When user "Brian" gets the group shares shared with him using the sharing API diff --git a/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesReceivedFilteredEmpty.feature b/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesReceivedFilteredEmpty.feature index e6b818c2948c..a3332cf9b7c6 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesReceivedFilteredEmpty.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesReceivedFilteredEmpty.feature @@ -18,6 +18,7 @@ Feature: get the received shares filtered by type (user, group etc) And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt" And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt" + Scenario Outline: getting shares received from users when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1" @@ -37,6 +38,7 @@ Feature: get the received shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares received from groups when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian" @@ -56,6 +58,7 @@ Feature: get the received shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares received from public links when there are none # Note: public links are purposely created in this scenario # users do not receive public links, so asking for a list of public links diff --git a/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesSharedFiltered.feature b/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesSharedFiltered.feature index 227fada5b6b7..95c7af420d4f 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesSharedFiltered.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesSharedFiltered.feature @@ -28,6 +28,7 @@ Feature: get shares filtered by type (user, group etc) | path | /fileToShareWithPublic.txt | | permissions | read | + Scenario Outline: getting shares shared to users Given using OCS API version "" When user "Alice" gets the user shares shared by him using the sharing API @@ -41,6 +42,7 @@ Feature: get shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares shared to groups Given using OCS API version "" When user "Alice" gets the group shares shared by him using the sharing API @@ -54,6 +56,7 @@ Feature: get shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares shared to public links Given using OCS API version "" When user "Alice" gets the public link shares shared by him using the sharing API @@ -67,6 +70,7 @@ Feature: get shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares shared to users and groups Given using OCS API version "" When user "Alice" gets the user and group shares shared by him using the sharing API diff --git a/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesSharedFilteredEmpty.feature b/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesSharedFilteredEmpty.feature index 4cd43544364b..f96fbced0ca9 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesSharedFilteredEmpty.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot1/gettingSharesSharedFilteredEmpty.feature @@ -18,6 +18,7 @@ Feature: get shares filtered by type (user, group etc) And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt" And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt" + Scenario Outline: getting shares shared to users when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1" @@ -37,6 +38,7 @@ Feature: get shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares shared to groups when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian" @@ -56,6 +58,7 @@ Feature: get shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares shared to public links when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian" diff --git a/tests/acceptance/features/apiShareOperationsToRoot2/getWebDAVSharePermissions.feature b/tests/acceptance/features/apiShareOperationsToRoot2/getWebDAVSharePermissions.feature index beb880633eff..693c988e0372 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot2/getWebDAVSharePermissions.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot2/getWebDAVSharePermissions.feature @@ -22,6 +22,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received file with edit and reshare permissions Given using DAV path And user "Alice" has uploaded file with content "foo" to "/tmp.txt" @@ -36,6 +37,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared file with edit and reshare permissions Given using DAV path And group "grp1" has been created @@ -56,6 +58,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received file with edit permissions but no reshare permissions Given using DAV path And user "Alice" has uploaded file with content "foo" to "/tmp.txt" @@ -69,6 +72,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared file with edit permissions but no reshare permissions Given using DAV path And group "grp1" has been created @@ -89,6 +93,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received file with reshare permissions but no edit permissions Given using DAV path And user "Alice" has uploaded file with content "foo" to "/tmp.txt" @@ -102,6 +107,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared file with reshare permissions but no edit permissions Given using DAV path And group "grp1" has been created @@ -123,6 +129,7 @@ Feature: sharing | new | + Scenario Outline: Correct webdav share-permissions for owned folder Given using DAV path And user "Alice" has created folder "/tmp" @@ -136,6 +143,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received folder with all permissions Given using DAV path And user "Alice" has created folder "/tmp" @@ -150,6 +158,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared folder with all permissions Given using DAV path And group "grp1" has been created @@ -169,6 +178,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received folder with all permissions but edit Given using DAV path And user "Alice" has created folder "/tmp" @@ -182,6 +192,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared folder with all permissions but edit Given using DAV path And group "grp1" has been created @@ -202,6 +213,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received folder with all permissions but create Given using DAV path And user "Alice" has created folder "/tmp" @@ -215,6 +227,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared folder with all permissions but create Given using DAV path And group "grp1" has been created @@ -235,6 +248,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received folder with all permissions but delete Given using DAV path And user "Alice" has created folder "/tmp" @@ -248,6 +262,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared folder with all permissions but delete Given using DAV path And group "grp1" has been created @@ -268,6 +283,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received folder with all permissions but share Given using DAV path And user "Alice" has created folder "/tmp" @@ -281,6 +297,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared folder with all permissions but share Given using DAV path And group "grp1" has been created diff --git a/tests/acceptance/features/apiShareOperationsToRoot2/shareAccessByID.feature b/tests/acceptance/features/apiShareOperationsToRoot2/shareAccessByID.feature index 02bc52fb0e52..c128edf8e1c4 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot2/shareAccessByID.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot2/shareAccessByID.feature @@ -7,6 +7,7 @@ Feature: share access by ID | Alice | | Brian | + Scenario Outline: Get a share with a valid share ID Given using OCS API version "" And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" @@ -32,6 +33,7 @@ Feature: share access by ID | 1 | 100 | | 2 | 200 | + Scenario Outline: accept a share using the share Id Given parameter "shareapi_auto_accept_share" of app "core" has been set to "yes" And using OCS API version "" @@ -50,6 +52,7 @@ Feature: share access by ID | 1 | 100 | | 2 | 200 | + Scenario Outline: decline a share using the share Id Given using OCS API version "" And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" diff --git a/tests/acceptance/features/apiShareOperationsToRoot2/uploadToShare.feature b/tests/acceptance/features/apiShareOperationsToRoot2/uploadToShare.feature index ff53912aacd3..6204a0ca6a71 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot2/uploadToShare.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot2/uploadToShare.feature @@ -5,6 +5,7 @@ Feature: sharing Given user "Alice" has been created with default attributes and without skeleton files And user "Alice" has created folder "FOLDER" + Scenario: Uploading file to a user read-only share folder does not work Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created a share with settings @@ -16,6 +17,7 @@ Feature: sharing Then the HTTP status code should be "403" And as "Alice" file "/FOLDER/textfile.txt" should not exist + Scenario Outline: Uploading file to a group read-only share folder does not work Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -34,6 +36,7 @@ Feature: sharing | old | | new | + Scenario Outline: Uploading file to a user upload-only share folder works Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -57,6 +60,7 @@ Feature: sharing | old | | new | + Scenario Outline: Uploading file to a group upload-only share folder works Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -104,6 +108,7 @@ Feature: sharing | old | | new | + Scenario Outline: Uploading file to a group read/write share folder works Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -149,6 +154,7 @@ Feature: sharing | old | | new | + Scenario Outline: Uploading to a user shared folder with read/write permission when the sharer has unsufficient quota does not work Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -166,6 +172,7 @@ Feature: sharing | old | | new | + Scenario Outline: Uploading to a group shared folder with read/write permission when the sharer has unsufficient quota does not work Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -185,6 +192,7 @@ Feature: sharing | old | | new | + Scenario Outline: Uploading to a user shared folder with upload-only permission when the sharer has insufficient quota does not work Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -202,6 +210,7 @@ Feature: sharing | old | | new | + Scenario Outline: Uploading to a group shared folder with upload-only permission when the sharer has insufficient quota does not work Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -221,6 +230,7 @@ Feature: sharing | old | | new | + Scenario: Uploading a file in to a shared folder without edit permissions Given using new DAV path And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature b/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature index 2e17f0a3e7e8..952701a8de9a 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature @@ -25,7 +25,6 @@ Feature: sharing | old | | new | - @smokeTest @files_trashbin-app-required @notToImplementOnOCIS Scenario Outline: moving a file out of a share as recipient creates a backup for the owner Given using DAV path @@ -110,6 +109,7 @@ Feature: sharing | old | | new | + Scenario Outline: Move files between shares by different users Given using DAV path And user "Carol" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesPendingFiltered.feature b/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesPendingFiltered.feature index e88f4e73f9cc..b9c4c593cfa7 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesPendingFiltered.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesPendingFiltered.feature @@ -32,6 +32,7 @@ Feature: get the pending shares filtered by type (user, group etc) | path | /fileToShareWithPublic.txt | | permissions | read | + Scenario Outline: getting pending shares received from users Given using OCS API version "" When user "Brian" gets the pending user shares shared with him using the sharing API @@ -44,6 +45,7 @@ Feature: get the pending shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting pending shares received from groups Given using OCS API version "" When user "Brian" gets the pending group shares shared with him using the sharing API diff --git a/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesReceivedFiltered.feature b/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesReceivedFiltered.feature index 646fd4993dcc..1079a8f0fec8 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesReceivedFiltered.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesReceivedFiltered.feature @@ -34,6 +34,7 @@ Feature: get the received shares filtered by type (user, group etc) | path | /fileToShareWithPublic.txt | | permissions | read | + Scenario Outline: getting shares received from users Given using OCS API version "" When user "Brian" gets the user shares shared with him using the sharing API @@ -47,6 +48,7 @@ Feature: get the received shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares received from groups Given using OCS API version "" When user "Brian" gets the group shares shared with him using the sharing API diff --git a/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature b/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature index 615e3834b2b3..ad0b79e45c8b 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature @@ -20,6 +20,7 @@ Feature: get the received shares filtered by type (user, group etc) And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt" And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt" + Scenario Outline: getting shares received from users when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1" @@ -41,6 +42,7 @@ Feature: get the received shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares received from groups when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian" @@ -62,6 +64,7 @@ Feature: get the received shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares received from public links when there are none # Note: public links are purposely created in this scenario # users do not receive public links, so asking for a list of public links diff --git a/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature b/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature index 65b87e956e91..d8999e4bf547 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature @@ -18,6 +18,7 @@ Feature: get shares filtered by type (user, group etc) And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt" And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt" + Scenario Outline: getting shares shared to users when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1" @@ -39,6 +40,7 @@ Feature: get shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares shared to groups when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian" @@ -60,6 +62,7 @@ Feature: get shares filtered by type (user, group etc) | 1 | 100 | | 2 | 200 | + Scenario Outline: getting shares shared to public links when there are none Given using OCS API version "" And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian" diff --git a/tests/acceptance/features/apiShareOperationsToShares2/getWebDAVSharePermissions.feature b/tests/acceptance/features/apiShareOperationsToShares2/getWebDAVSharePermissions.feature index be145a47b71f..f7ce6d51d6ae 100644 --- a/tests/acceptance/features/apiShareOperationsToShares2/getWebDAVSharePermissions.feature +++ b/tests/acceptance/features/apiShareOperationsToShares2/getWebDAVSharePermissions.feature @@ -119,6 +119,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for received group shared file with reshare permissions but no edit permissions Given using DAV path And group "grp1" has been created @@ -140,6 +141,7 @@ Feature: sharing | old | | new | + Scenario Outline: Correct webdav share-permissions for owned folder Given using DAV path And user "Alice" has created folder "/tmp" @@ -341,4 +343,4 @@ Feature: sharing Examples: | dav-path | | old | - | new | \ No newline at end of file + | new |