diff --git a/.drone.star b/.drone.star index 7177fd73ead..0cc995a2bde 100644 --- a/.drone.star +++ b/.drone.star @@ -96,7 +96,6 @@ config = { ], "suites": { "oCISBasic": [ - "webUIPrivateLinks", "webUIPreview", "webUILogin", ], @@ -121,7 +120,6 @@ config = { ], "oCISFiles5": [ "webUIFilesCopy", - "webUIFilesActionMenu", "webUITextEditor", ], "oCISSharingInternal1": [ @@ -138,8 +136,6 @@ config = { ], "oCISSharingAutocompletionResharing": [ "webUISharingAutocompletion", - "webUIResharing1", - "webUIResharing2", ], "oCISSharingPerm1": [ "webUISharingPermissionsUsers", @@ -156,7 +152,6 @@ config = { "webUISharingPublicBasic", ], "oCISSharingPublic2": [ - "webUISharingPublicExpire", "webUISharingPublicManagement", ], "oCISSharingPublic3": [ @@ -189,40 +184,18 @@ config = { "build": True, } -# UI Test Suites -# These list contains all the test suites that are present -# When adding new test suites, make sure to update these lists -rootSharingTestSuites = [ - "webUIResharingToRoot", - "webUISharingAcceptSharesToRoot", - "webUISharingInternalGroupsToRoot", - "webUISharingInternalGroupsToRootEdgeCases", - "webUISharingInternalGroupsToRootSharingIndicator", - "webUISharingInternalUsersToRoot", - "webUISharingInternalUsersToRootBlacklisted", - "webUISharingInternalUsersToRootCollaborator", - "webUISharingInternalUsersToRootPreviews", - "webUISharingInternalUsersToRootShareWithPage", - "webUISharingInternalUsersToRootSharingIndicator", - "webUISharingPermissionToRoot", -] - basicTestSuites = [ "webUICreateFilesFolders", "webUIDeleteFilesFolders", "webUIFiles", - "webUIFilesActionMenu", "webUIFilesCopy", "webUIFilesDetails", "webUIFilesList", "webUILogin", "webUIMoveFilesFolders", "webUIPreview", - "webUIPrivateLinks", "webUIRenameFiles", "webUIRenameFolders", - "webUIResharing1", - "webUIResharing2", "webUISharingAcceptShares", "webUISharingAutocompletion", "webUISharingFilePermissionMultipleUsers", @@ -240,7 +213,6 @@ basicTestSuites = [ "webUISharingPermissionsUsers", "webUISharingPublicBasic", "webUISharingPublicDifferentRoles", - "webUISharingPublicExpire", "webUISharingPublicManagement", "webUITextEditor", "webUITrashbinDelete", diff --git a/tests/acceptance/expected-failures-with-ocis-server-ocis-storage.md b/tests/acceptance/expected-failures-with-ocis-server-ocis-storage.md index ce49c0d244a..396b890e84b 100644 --- a/tests/acceptance/expected-failures-with-ocis-server-ocis-storage.md +++ b/tests/acceptance/expected-failures-with-ocis-server-ocis-storage.md @@ -14,7 +14,7 @@ Other free text and markdown formatting can be used elsewhere in the document if - [webUILogin/openidLogin.feature:60](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUILogin/openidLogin.feature#L60) ### [Share additional info](https://github.com/owncloud/ocis/issues/1253) -- [webUISharingInternalUsersShareWithPage/shareWithUsers.feature:126](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingInternalUsersShareWithPage/shareWithUsers.feature#L126) +- [webUISharingInternalUsersShareWithPage/shareWithUsers.feature:115](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingInternalUsersShareWithPage/shareWithUsers.feature#L115) ### [Different path for shares inside folder](https://github.com/owncloud/ocis/issues/1231) @@ -32,7 +32,7 @@ Other free text and markdown formatting can be used elsewhere in the document if - [webUISharingPublicManagement/shareByPublicLink.feature:24](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingPublicManagement/shareByPublicLink.feature#L24) ### [Uploading folders does not work in files-drop](https://github.com/owncloud/web/issues/2443) -- [webUISharingPublicDifferentRoles/shareByPublicLinkDifferentRoles.feature:265](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingPublicDifferentRoles/shareByPublicLinkDifferentRoles.feature#L265) +- [webUISharingPublicDifferentRoles/shareByPublicLinkDifferentRoles.feature:263](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingPublicDifferentRoles/shareByPublicLinkDifferentRoles.feature#L263) ### [Resources cannot be locked under ocis](https://github.com/owncloud/ocis/issues/1284) - [webUIWebdavLockProtection/delete.feature:33](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIWebdavLockProtection/delete.feature#L33) @@ -52,4 +52,4 @@ Other free text and markdown formatting can be used elsewhere in the document if - [webUIUpload/upload.feature:43](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIUpload/upload.feature#L43) ### [PROPFIND to sub-folder of a shared resources with same name gives 404](https://github.com/owncloud/ocis/issues/3859) -- [webUISharingAcceptShares/acceptShares.feature:105](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAcceptShares/acceptShares.feature#L105) +- [webUISharingAcceptShares/acceptShares.feature:88](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAcceptShares/acceptShares.feature#L88) diff --git a/tests/acceptance/features/webUIFilesActionMenu/fileFolderActionMenu.feature b/tests/acceptance/features/webUIFilesActionMenu/fileFolderActionMenu.feature deleted file mode 100644 index 6ae7c276ad2..00000000000 --- a/tests/acceptance/features/webUIFilesActionMenu/fileFolderActionMenu.feature +++ /dev/null @@ -1,45 +0,0 @@ -Feature: User can see the file or folder actions menu options - As a user - I want to be able to see the actions menu options of file or folder - So that the menu options of the selected file type or folder are visible to me - - Background: prepare user and files - Given user "Alice" has been created with default attributes and without skeleton files in the server - And user "Alice" has created folder "simple-folder" in the server - And user "Alice" has uploaded file "lorem.txt" to "lorem.txt" in the server - And user "Alice" has uploaded file "testavatar.png" to "testavatar.png" in the server - And user "Alice" has logged in using the webUI - And the user has browsed to the personal page - - - @skipOnOCIS - Scenario: observe different actions menu options on selecting different file types - Given user "Alice" has uploaded file with content "pdf file" to "lorem.pdf" in the server - And the user has reloaded the current page of the webUI - When the user opens the actions sidebar panel of file "lorem.txt" on the webUI - Then the app-sidebar for file "lorem.txt" should be visible on the webUI - And only the following items with default items should be visible in the actions menu on the webUI - | items | - | open in text editor | - | download | - When the user opens the actions sidebar panel of file "lorem.pdf" on the webUI - Then the app-sidebar for file "lorem.pdf" should be visible on the webUI - And only the following items with default items should be visible in the actions menu on the webUI - | items | - | open in pdf viewer | - | download | - When the user opens the actions sidebar panel of file "testavatar.png" on the webUI - Then the app-sidebar for file "testavatar.png" should be visible on the webUI - And only the following items with default items should be visible in the actions menu on the webUI - | items | - | preview | - | download | - - @skipOnOCIS - Scenario: observe different actions menu options on selecting a folder - When the user opens the actions sidebar panel of folder "simple-folder" on the webUI - Then the app-sidebar for folder "simple-folder" should be visible on the webUI - And only the following items with default items should be visible in the actions menu on the webUI - | items | - | open folder | - | download | diff --git a/tests/acceptance/features/webUIFilesActionMenu/versions.feature b/tests/acceptance/features/webUIFilesActionMenu/versions.feature deleted file mode 100644 index 2f4feadf6a0..00000000000 --- a/tests/acceptance/features/webUIFilesActionMenu/versions.feature +++ /dev/null @@ -1,76 +0,0 @@ -@files_versions-app-required -Feature: Versions of a file - - As a user - I would like to see different versions of a file and delete and restore them - So that I can have more control over the files - - Background: - Given these users have been created with default attributes and without skeleton files in the server: - | username | - | user0 | - | Alice | - - @ocis-reva-issue-110 @skipOnStorage:ceph @files_primary_s3-issue-1 @skipOnOCIS - Scenario: file versions cannot be seen on the webUI after deleting versions - Given user "user0" has uploaded file with content "lorem content" to "lorem-file.txt" in the server - And user "user0" has uploaded file with content "lorem" to "lorem-file.txt" in the server - And user "user0" has uploaded file with content "new lorem content" to "lorem-file.txt" in the server - And user "user0" has logged in using the webUI - And the administrator has cleared the versions for user "user0" in the server - When the user browses to display the "versions" details of file "lorem-file.txt" - Then the versions list should contain 0 entries - - @ocis-reva-issue-110 @skipOnStorage:ceph @files_primary_s3-issue-155 @skipOnOCIS - Scenario: file versions cannot be seen on the webUI only for user whose versions is deleted - Given user "user0" has uploaded file with content "lorem content" to "lorem-file.txt" in the server - And user "user0" has uploaded file with content "lorem" to "lorem-file.txt" in the server - And user "Alice" has uploaded file with content "lorem content" to "lorem-file.txt" in the server - And user "Alice" has uploaded file with content "lorem" to "lorem-file.txt" in the server - And user "user0" has logged in using the webUI - And the administrator has cleared the versions for user "user0" in the server - When the user browses to display the "versions" details of file "lorem-file.txt" - Then the versions list should contain 0 entries - When the user re-logs in as "Alice" using the webUI - And the user browses to display the "versions" details of file "lorem-file.txt" - Then the versions list should contain 1 entries - - @ocis-reva-issue-110 @skipOnStorage:ceph @files_primary_s3-issue-155 @skipOnOCIS - Scenario: file versions cannot be seen on the webUI for all users after deleting versions for all users - Given user "user0" has uploaded file with content "lorem content" to "/lorem-file.txt" in the server - And user "user0" has uploaded file with content "lorem" to "/lorem-file.txt" in the server - And user "Alice" has uploaded file with content "lorem content" to "/lorem-file.txt" in the server - And user "Alice" has uploaded file with content "lorem" to "/lorem-file.txt" in the server - And user "user0" has logged in using the webUI - And the administrator has cleared the versions for all users in the server - When the user browses to display the "versions" details of file "lorem-file.txt" - Then the versions list should contain 0 entries - When the user re-logs in as "Alice" using the webUI - And the user browses to display the "versions" details of file "lorem-file.txt" - Then the versions list should contain 0 entries - - @issue-ocis-2319 @skipOnOCIS - Scenario: change the file content of a received shared file - Given the administrator has set the default folder for received shares to "Shares" in the server - And user "Brian" has been created with default attributes and without skeleton files in the server - And user "Brian" has created folder "simple-folder" in the server - And user "Brian" has uploaded file with content "a text file" to "simple-folder/lorem.txt" in the server - And user "Brian" has shared folder "simple-folder" with user "Alice" with "all" permissions in the server - And user "Alice" has logged in using the webUI - And the user has opened folder "Shares" - And the user has opened folder "simple-folder" - When the user uploads overwriting file "lorem.txt" using the webUI - And the user browses to display the "versions" details of file "lorem.txt" - Then the versions list should contain 1 entries - - @issue-ocis-1328 @disablePreviews @skipOnOCIS - Scenario: sharee can see the versions of a file - Given the setting "shareapi_auto_accept_share" of app "core" has been set to "yes" in the server - And user "user0" has uploaded file with content "lorem content" to "lorem-file.txt" in the server - And user "user0" has uploaded file with content "lorem" to "lorem-file.txt" in the server - And user "user0" has uploaded file with content "new lorem content" to "lorem-file.txt" in the server - And user "user0" has shared file "lorem-file.txt" with user "Alice" in the server - And user "Alice" has logged in using the webUI - When the user browses to display the "versions" details of file "lorem-file.txt" - Then the content of file "lorem-file.txt" for user "Alice" should be "new lorem content" in the server - And the versions list should contain 2 entries diff --git a/tests/acceptance/features/webUIFilesCopy/copy.feature b/tests/acceptance/features/webUIFilesCopy/copy.feature index 79b7698cda6..0557a7059ba 100644 --- a/tests/acceptance/features/webUIFilesCopy/copy.feature +++ b/tests/acceptance/features/webUIFilesCopy/copy.feature @@ -84,27 +84,6 @@ Feature: copy files and folders And as "Alice" file "simple-folder/simple-empty-folder/data.zip" should exist in the server And as "Alice" file "simple-folder/data.zip" should exist in the server - @issue-6892 @issue-6896 @notToImplementOnOCIS - Scenario: copy a file into another folder with no change permission - Given user "Alice" has created file "lorem.txt" in the server - And user "Brian" has been created with default attributes and without skeleton files in the server - And user "Brian" has created folder "simple-folder" in the server - And user "Brian" has shared folder "simple-folder" with user "Alice" with "read" permissions in the server - And user "Alice" has logged in using the webUI - When the user tries to copy file "lorem.txt" into folder "Shares/simple-folder" using the webUI - Then as "Alice" file "Shares/simple-folder/lorem.txt" should not exist in the server - - - @issue-6892 @issue-ocis-1328 @issue-6896 @notToImplementOnOCIS - Scenario: copy a folder into another folder with no change permission - Given user "Alice" has created folder "simple-empty-folder" in the server - And user "Brian" has been created with default attributes and without skeleton files in the server - And user "Brian" has created folder "simple-folder" in the server - And user "Brian" has shared folder "simple-folder" with user "Alice" with "read" permissions in the server - And user "Alice" has logged in using the webUI - When the user tries to copy folder "simple-empty-folder" into folder "Shares/simple-folder" using the webUI - Then as "Alice" file "Shares/simple-folder/simple-empty-folder" should not exist in the server - Scenario: copy a folder into the same folder Given user "Alice" has created folder "simple-empty-folder" in the server diff --git a/tests/acceptance/features/webUIPrivateLinks/accessingPrivateLinks.feature b/tests/acceptance/features/webUIPrivateLinks/accessingPrivateLinks.feature deleted file mode 100644 index c71b8007bc2..00000000000 --- a/tests/acceptance/features/webUIPrivateLinks/accessingPrivateLinks.feature +++ /dev/null @@ -1,18 +0,0 @@ -@notToImplementOnOCIS @issue-6844 -Feature: Access private link - As a user I want to directly access item which I have received private link for - - Background: - Given user "Alice" has been created with default attributes and without skeleton files in the server - And user "Alice" has uploaded file "lorem.txt" to "lorem.txt" in the server - - - @issue-3243 - Scenario: Access the private link as an user that does not have permissions to see the file - Given user "Brian" has been created with default attributes and without skeleton files in the server - And user "Brian" has logged in using the webUI - When the user navigates to the private link created by user "Alice" for file "lorem.txt" - Then the user should see the following error message on the link resolve page - """ - An error occurred while resolving the private link - """ diff --git a/tests/acceptance/features/webUIResharing1/reshareUsers.feature b/tests/acceptance/features/webUIResharing1/reshareUsers.feature deleted file mode 100644 index 5e407b7b4d1..00000000000 --- a/tests/acceptance/features/webUIResharing1/reshareUsers.feature +++ /dev/null @@ -1,76 +0,0 @@ -# Reshare permission is not available now in the oCIS webUI -Feature: Resharing shared files with different permissions - As a user - I want to reshare received files and folders with other users with different permissions - So that I can control the access on those files/folders by other collaborators - - Background: - Given the administrator has set the default folder for received shares to "Shares" in the server - And these users have been created with default attributes and without skeleton files in the server: - | username | - | Alice | - | Brian | - | Carol | - And user "Brian" has created folder "simple-folder" in the server - - - @skipOnOCIS - Scenario: User is allowed to reshare a file/folder with the equivalent received permissions, and collaborators should not be listed for the receiver - Given user "Brian" has shared folder "simple-folder" with user "Alice" with "read, share, delete" permissions in the server - And user "Alice" has logged in using the webUI - And the user opens folder "Shares" using the webUI - When the user shares folder "simple-folder" with user "Carol King" as "Custom permissions" with permissions "share, delete" using the webUI - And the user re-logs in as "Carol" using the webUI - And the user opens folder "Shares" using the webUI - And the collaborators list for folder "simple-folder" should be empty - # Then the current collaborators list should have order "Brian Murphy,Carol King" - # And user "Brian Murphy" should be listed as "Owner" reshared through "Alice Hansen" in the collaborators list on the webUI - And user "Carol" should have received a share with these details in the server: - | field | value | - | uid_owner | Alice | - | share_with | Carol | - | file_target | /Shares/simple-folder | - | item_type | folder | - | permissions | share, delete, read | - - @skipOnOCIS - Scenario: User is allowed to reshare a file/folder with the lesser permissions, and check if it is listed for original owner - Given user "Brian" has shared folder "simple-folder" with user "Alice" with "read, share, delete" permissions in the server - And user "Alice" has logged in using the webUI - And the user opens folder "Shares" using the webUI - When the user shares folder "simple-folder" with user "Carol King" as "Custom permissions" with permissions "delete" using the webUI - And the user re-logs in as "Brian" using the webUI - Then user "Alice Hansen" should be listed as "Custom permissions" in the collaborators list for folder "simple-folder" on the webUI - And custom permissions "share, delete" should be set for user "Alice Hansen" for folder "simple-folder" on the webUI - And user "Carol King" should be listed as "Custom permissions" in the collaborators list for folder "simple-folder" on the webUI - And custom permissions "delete" should be set for user "Carol King" for folder "simple-folder" on the webUI - And user "Carol" should have received a share with these details in the server: - | field | value | - | uid_owner | Alice | - | share_with | Carol | - | file_target | /Shares/simple-folder | - | item_type | folder | - | permissions | delete, read | - - - Scenario: Reshare a file and folder from shared with others page - Given user "Brian" has created file "lorem.txt" in the server - And user "Brian" has shared folder "simple-folder" with user "Alice" in the server - And user "Brian" has shared file "lorem.txt" with user "Alice" in the server - And user "Brian" has logged in using the webUI - And the user has browsed to the shared-with-others page - When the user shares folder "simple-folder" with user "Carol King" as "Editor" using the webUI - And the user shares file "lorem.txt" with user "Carol King" as "Editor" using the webUI - Then as "Carol" folder "/Shares/simple-folder" should exist in the server - And as "Carol" file "/Shares/lorem.txt" should exist in the server - - - @issue-product-270 - Scenario: Resource owner sees resharer in collaborators list - Given user "Brian" has created file "lorem.txt" in the server - And user "Brian" has shared folder "simple-folder" with user "Alice" in the server - And user "Alice" has shared folder "/Shares/simple-folder" with user "Carol" in the server - When user "Brian" has logged in using the webUI - And the user opens the share dialog for folder "simple-folder" using the webUI - Then user "Alice Hansen" should be listed as "Can edit" in the collaborators list on the webUI - And user "Carol King" should be listed as "Can edit" in the collaborators list on the webUI diff --git a/tests/acceptance/features/webUIResharing2/reshareUsers.feature b/tests/acceptance/features/webUIResharing2/reshareUsers.feature deleted file mode 100644 index 7b93b86ba31..00000000000 --- a/tests/acceptance/features/webUIResharing2/reshareUsers.feature +++ /dev/null @@ -1,94 +0,0 @@ -# Reshare permission is not available now in the oCIS webUI -Feature: Resharing shared files with different permissions - As a user - I want to reshare received files and folders with other users with different permissions - So that I can control the access on those files/folders by other collaborators - - Background: - Given the administrator has set the default folder for received shares to "Shares" in the server - And these users have been created with default attributes and without skeleton files in the server: - | username | - | Alice | - | Brian | - | Carol | - And user "Brian" has created folder "simple-folder" in the server - - @issue-ocis-1922 - Scenario: Reshare a folder without share permissions using API and check if it is listed on the collaborators list for original owner - Given user "Brian" has shared folder "simple-folder" with user "Alice" with "read, share" permissions in the server - And user "Alice" has shared folder "Shares/simple-folder" with user "Carol" with "read" permissions in the server - And user "Brian" has logged in using the webUI - When the user opens the share dialog for folder "simple-folder" using the webUI - Then user "Carol King" should be listed as "Custom permissions" in the collaborators list for folder "simple-folder" on the webUI - And no custom permissions should be set for collaborator "Carol King" for folder "simple-folder" on the webUI - - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS - Scenario: Reshare a folder without share permissions using API and check if it is listed on the collaborators list for resharer - Given user "Brian" has shared folder "simple-folder" with user "Alice" with "read, share" permissions in the server - And user "Alice" has logged in using the webUI - And the user opens folder "Shares" using the webUI - When the user opens the share dialog for folder "simple-folder" using the webUI - Then user "Carol King" should be listed as "Custom permissions" in the collaborators list for folder "simple-folder" on the webUI - And no custom permissions should be set for collaborator "Carol King" for folder "simple-folder" on the webUI - - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS - Scenario Outline: share a received folder with another user with same permissions(including share permissions) and check if the user is displayed in collaborators list for resharer - Given user "Brian" has shared folder "simple-folder" with user "Alice" with "" permissions in the server - And user "Alice" has logged in using the webUI - And the user opens folder "Shares" using the webUI - When the user shares folder "simple-folder" with user "Carol King" as "" with permissions "" using the webUI - Then user "Carol King" should be listed as "" in the collaborators list for folder "simple-folder" on the webUI - And custom permissions "" should be set for user "Carol King" for folder "simple-folder" on the webUI - And user "Carol" should have received a share with these details in the server: - | field | value | - | uid_owner | Alice | - | share_with | Carol | - | file_target | /Shares/simple-folder | - | item_type | folder | - | permissions | | - Examples: - | role | displayed-role | collaborators-permissions | displayed-permissions | permissions | - | Viewer | Can view | , | share | read, share | - | Editor | Can edit | , | share, delete, update, create | all | - | Custom permissions | Custom permissions | update, share | share, update | read, update, share | - | Custom permissions | Custom permissions | share, create | share, create | read, share, create | - | Custom permissions | Can edit | delete, share, create, update | share, delete, update, create | read, share, delete, update, create | - - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS - Scenario Outline: share a received folder with another user with same permissions(including share permissions) and check if the user is displayed in collaborators list for original owner - Given user "Brian" has shared folder "simple-folder" with user "Alice" with "" permissions in the server - And user "Alice" has logged in using the webUI - And the user opens folder "Shares" using the webUI - When the user shares folder "simple-folder" with user "Carol King" as "" with permissions "" using the webUI - And the user re-logs in as "Brian" using the webUI - Then user "Carol King" should be listed as "" in the collaborators list for folder "simple-folder" on the webUI - And custom permissions "" should be set for user "Carol King" for folder "simple-folder" on the webUI - And user "Alice Hansen" should be listed as "" in the collaborators list for folder "simple-folder" on the webUI - And custom permissions "" should be set for user "Alice Hansen" for folder "simple-folder" on the webUI - And user "Carol" should have received a share with these details in the server: - | field | value | - | uid_owner | Alice | - | share_with | Carol | - | file_target | /Shares/simple-folder | - | item_type | folder | - | permissions | | - And user "Alice" should have received a share with these details in the server: - | field | value | - | uid_owner | Brian | - | share_with | Alice | - | file_target | /Shares/simple-folder | - | item_type | folder | - | permissions | | - Examples: - | role | displayed-role | collaborators-permissions | displayed-permissions | permissions | - | Viewer | Can view | , | share | read, share | - | Editor | Can edit | , | share, delete, update, create | all | - | Custom permissions | Custom permissions | share, create | share, create | read, share, create | - | Custom permissions | Custom permissions | update, share | share, update | read, update, share | - | Custom permissions | Can edit | delete, share, create, update | share, delete, update, create | read, share, delete, update, create | diff --git a/tests/acceptance/features/webUISharingAcceptShares/acceptShares.feature b/tests/acceptance/features/webUISharingAcceptShares/acceptShares.feature index 6b77902ac5d..2422c05afac 100644 --- a/tests/acceptance/features/webUISharingAcceptShares/acceptShares.feature +++ b/tests/acceptance/features/webUISharingAcceptShares/acceptShares.feature @@ -26,23 +26,6 @@ Feature: accept/decline shares coming from internal users When the user browses to the files page Then folder "/Shares" should not be listed on the webUI - @issue-2512 @issue-4102 @issue-6896 @skipOnOCIS - Scenario: reshare a share that you received to a group that you are member of - Given these groups have been created in the server: - | groupname | - | grp1 | - And user "Alice" has created folder "/simple-folder" in the server - And user "Brian" has been added to group "grp1" in the server - And user "Alice" has shared folder "/simple-folder" with user "Brian" in the server - And the user has browsed to the personal page - And the user opens folder "Shares" using the webUI - When the user shares folder "simple-folder" with group "grp1" as "Viewer" using the webUI - And the user deletes folder "simple-folder" using the webUI - And the user browses to the shared-with-me page in declined shares view - Then folder "simple-folder" shared by "Alice Hansen" should be in "Declined" state on the webUI - And folder "simple-folder" shared by "Brian Murphy" should not be listed on the webUI - And folder "simple-folder" should not be listed on the webUI - Scenario: User receives files when auto accept share is disabled - oCIS behavior Given user "Alice" has created file "toshare.txt" in the server diff --git a/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletion.feature b/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletion.feature index 7efefd0e5d1..c55cfb31073 100644 --- a/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletion.feature +++ b/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletion.feature @@ -31,26 +31,6 @@ Feature: Autocompletion of share-with names | users-finance | | other | - @smokeTest @issue-ocis-1961 @skipOnOCIS - Scenario: autocompletion of regular existing users - Given user "regularuser" has created folder "simple-folder" in the server - And user "regularuser" has logged in using the webUI - And the user has opened the share dialog for folder "simple-folder" - When the user types "us" in the share-with-field - Then all users and groups that contain the string "us" in their name should be listed in the autocomplete list on the webUI - But only users and groups that contain the string "us" in their name or displayname should be listed in the autocomplete list on the webUI - And the users own name should not be listed in the autocomplete list on the webUI - - @smokeTest @issue-ocis-1961 @skipOnOCIS - Scenario: autocompletion of regular existing groups - Given user "regularuser" has created folder "simple-folder" in the server - And user "regularuser" has logged in using the webUI - And the user has opened the share dialog for folder "simple-folder" - When the user types "fi" in the share-with-field - Then all users and groups that contain the string "fi" in their name should be listed in the autocomplete list on the webUI - But only users and groups that contain the string "fi" in their name or displayname should be listed in the autocomplete list on the webUI - And the users own name should not be listed in the autocomplete list on the webUI - Scenario: autocompletion for a pattern that does not match any user or group Given user "regularuser" has created folder "simple-folder" in the server @@ -69,104 +49,6 @@ Feature: Autocompletion of share-with names When the user types "u" in the share-with-field Then the autocomplete list should not be displayed on the webUI - @skipOnOCIS - Scenario: autocompletion when minimum characters is increased and not enough characters are typed - Given the administrator has set the minimum characters for sharing autocomplete to "4" in the server - And user "regularuser" has created folder "simple-folder" in the server - And user "regularuser" has logged in using the webUI - And the user has browsed to the personal page - And the user has opened the share dialog for folder "simple-folder" - When the user types "use" in the share-with-field - Then the autocomplete list should not be displayed on the webUI - - @issue-ocis-1961 @skipOnOCIS - Scenario: autocomplete short user/display names when completely typed - Given the administrator has set the minimum characters for sharing autocomplete to "3" in the server - And user "regularuser" has created folder "simple-folder" in the server - And user "regularuser" has logged in using the webUI - And the user has browsed to the personal page - And these users have been created without initialization and without skeleton files in the server: - | username | password | displayname | email | - | use | %alt1% | Use | uz@oc.com.np | - And the user has opened the share dialog for folder "simple-folder" - When the user types "Use" in the share-with-field - Then "user" "Use" should be listed in the autocomplete list on the webUI - - @issue-ocis-1961 @skipOnOCIS - Scenario: autocomplete short group names when completely typed - Given the administrator has set the minimum characters for sharing autocomplete to "2" in the server - And user "regularuser" has created folder "simple-folder" in the server - And these groups have been created in the server: - | groupname | - | fi | - And user "regularuser" has logged in using the webUI - And the user has browsed to the personal page - And the user has opened the share dialog for folder "simple-folder" - When the user types "fi" in the share-with-field - Then "group" "fi" should be listed in the autocomplete list on the webUI - - @skipOnOCIS - Scenario: autocompletion when increasing the minimum characters for sharing autocomplete - Given the administrator has set the minimum characters for sharing autocomplete to "3" in the server - And user "regularuser" has created folder "simple-folder" in the server - And user "regularuser" has logged in using the webUI - And the user has browsed to the personal page - And the user has opened the share dialog for folder "simple-folder" - When the user types "use" in the share-with-field - Then all users and groups that contain the string "use" in their name should be listed in the autocomplete list on the webUI - But only users and groups that contain the string "use" in their name or displayname should be listed in the autocomplete list on the webUI - And the users own name should not be listed in the autocomplete list on the webUI - - @skipOnOCIS - Scenario: autocompletion of a pattern that matches regular existing users but also a user with whom the item is already shared (folder) - Given user "regularuser" has created folder "simple-folder" in the server - And user "regularuser" has logged in using the webUI - And the user has browsed to the personal page - And user "regularuser" has shared folder "simple-folder" with user "Alice" in the server - And the user has opened the share dialog for folder "simple-folder" - When the user types "user" in the share-with-field - Then all users and groups that contain the string "user" in their name should be listed in the autocomplete list on the webUI except user "Alice Hansen" - But only users and groups that contain the string "user" in their name or displayname should be listed in the autocomplete list on the webUI - And the users own name should not be listed in the autocomplete list on the webUI - - @skipOnOCIS - Scenario: autocompletion of a pattern that matches regular existing users but also a user with whom the item is already shared (file) - Given user "regularuser" has created file "data.zip" in the server - And user "regularuser" has logged in using the webUI - And the user has browsed to the personal page - And user "regularuser" has shared file "data.zip" with user "usergrp" in the server - And the user has opened the share dialog for file "data.zip" - When the user types "user" in the share-with-field - Then all users and groups that contain the string "user" in their name should be listed in the autocomplete list on the webUI except user "User Grp" - But only users and groups that contain the string "user" in their name or displayname should be listed in the autocomplete list on the webUI - And the users own name should not be listed in the autocomplete list on the webUI - - @skipOnOCIS - Scenario: autocompletion of a pattern that matches regular existing groups but also a group with whom the item is already shared (folder) - Given the administrator has set the minimum characters for sharing autocomplete to "2" in the server - And user "regularuser" has created folder "simple-folder" in the server - And user "regularuser" has logged in using the webUI - And the user has browsed to the personal page - And user "regularuser" has shared folder "simple-folder" with group "finance1" in the server - And the user has opened the share dialog for folder "simple-folder" - When the user types "fi" in the share-with-field - Then all users and groups that contain the string "fi" in their name should be listed in the autocomplete list on the webUI except group "finance1" - But only users and groups that contain the string "fi" in their name or displayname should be listed in the autocomplete list on the webUI - And the users own name should not be listed in the autocomplete list on the webUI - - @skipOnOCIS - Scenario: autocompletion of a pattern that matches regular existing groups but also a group with whom the item is already shared (file) - Given the administrator has set the minimum characters for sharing autocomplete to "2" in the server - And user "regularuser" has created file "data.zip" in the server - And user "regularuser" has logged in using the webUI - And the user has browsed to the personal page - And user "regularuser" has shared file "data.zip" with group "finance1" in the server - And the user has opened the share dialog for file "data.zip" - When the user types "fi" in the share-with-field - Then all users and groups that contain the string "fi" in their name should be listed in the autocomplete list on the webUI except group "finance1" - But only users and groups that contain the string "fi" in their name or displayname should be listed in the autocomplete list on the webUI - And the users own name should not be listed in the autocomplete list on the webUI - Scenario: add collaborators in the invite list and remove some of them Given user "regularuser" has created folder "simple-folder" in the server diff --git a/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature b/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature index 196b7a621df..228a883114f 100644 --- a/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature +++ b/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature @@ -30,15 +30,9 @@ Feature: Autocompletion of share-with names And the user has opened the share dialog for file "data.zip" When the user types "" in the share-with-field Then only users and groups that contain the string "" in their name or displayname should be listed in the autocomplete list on the webUI - - @skipOnOCIS Examples: | displayName | search | | -_.ocusr | -_ | - | ocusr-_. | oc | - - Examples: - | displayName | search | | _ocusr@ | _u | @issue-ocis-1317 @issue-ocis-1675 @@ -57,8 +51,3 @@ Feature: Autocompletion of share-with names | @-_. | @- | | _ocgrp@ | _u | | -_.ocgrp | -_ | - - @skipOnOCIS - Examples: - | group | search | - | ocgrp-_. | oc | diff --git a/tests/acceptance/features/webUISharingInternalGroups/shareWithGroups.feature b/tests/acceptance/features/webUISharingInternalGroups/shareWithGroups.feature index 57fa0dca08e..193f789b851 100644 --- a/tests/acceptance/features/webUISharingInternalGroups/shareWithGroups.feature +++ b/tests/acceptance/features/webUISharingInternalGroups/shareWithGroups.feature @@ -25,132 +25,6 @@ Feature: Sharing files and folders with internal groups And the user shares folder "simple-folder" with user "Alice Hansen" as "Viewer" using the webUI Then the current collaborators list should have order "Alice Hansen,Brian Murphy,grp1,grp11" - @issue-6896 @skipOnOCIS - Scenario Outline: share a file & folder with another internal user - Given user "Carol" has created folder "simple-folder" in the server - And user "Carol" has created file "simple-folder/lorem.txt" in the server - And user "Carol" has created file "testimage.jpg" in the server - And user "Carol" has logged in using the webUI - When the user shares folder "simple-folder" with group "grp1" as "" using the webUI - And the user shares file "testimage.jpg" with group "grp1" as "" using the webUI - Then group "grp1" should be listed as "" in the collaborators list for folder "simple-folder" on the webUI - And group "grp1" should be listed as "" in the collaborators list for file "testimage.jpg" on the webUI - And user "Alice" should have received a share with these details in the server: - | field | value | - | uid_owner | Carol | - | share_with | grp1 | - | file_target | /Shares/simple-folder | - | item_type | folder | - | permissions | | - And user "Brian" should have received a share with these details in the server: - | field | value | - | uid_owner | Carol | - | share_with | grp1 | - | file_target | /Shares/testimage.jpg | - | item_type | file | - | permissions | | - And as "Alice" these resources should be listed in the folder "Shares" on the webUI - | entry_name | - | simple-folder | - | testimage.jpg | - And these resources should be listed in the folder "/Shares/simple-folder" on the webUI - | entry_name | - | lorem.txt | - But these resources should not be listed in the folder "/Shares/simple-folder" on the webUI - | entry_name | - | simple-folder | - When the user browses to the shared-with-me page - Then folder "simple-folder" should be marked as shared by "Carol King" on the webUI - And file "testimage.jpg" should be marked as shared by "Carol King" on the webUI - Examples: - | set-role | expected-role | permissions-folder | permissions-file | - | Viewer | Can view | read,share | read,share | - | Editor | Can edit | read,update,create,delete,share | read,update,share | - | Custom permissions | Custom permissions | read | read | - - @issue-4102 @issue-ocis-2267 @issue-6896 @notToImplementOnOCIS - Scenario: share a file with an internal group a member overwrites and unshares the file - Given user "Carol" has created file "lorem.txt" in the server - And user "Carol" has logged in using the webUI - When the user renames file "lorem.txt" to "new-lorem.txt" using the webUI - And the user shares file "new-lorem.txt" with group "grp1" as "Editor" using the webUI - And the user re-logs in as "Alice" using the webUI - Then as "Alice" the content of "/Shares/new-lorem.txt" in the server should not be the same as the content of local file "new-lorem.txt" - # overwrite the received shared file - When the user opens folder "Shares" using the webUI - And the user uploads overwriting file "new-lorem.txt" using the webUI - Then file "new-lorem.txt" should be listed on the webUI - And as "Alice" the content of "/Shares/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - # unshare the received shared file - When the user deletes file "new-lorem.txt" using the webUI - Then file "new-lorem.txt" should not be listed on the webUI - # check that another group member can still see the file - And as "Brian" the content of "/Shares/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - # check that the original file owner can still see the file - And as "Carol" the content of "new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - - @issue-ocis-1943 @skipOnOCIS - Scenario: share a folder with an internal group and a member uploads, overwrites and deletes files - Given user "Carol" has created folder "simple-folder" in the server - And user "Carol" has created file "simple-folder/lorem.txt" in the server - And user "Carol" has created file "simple-folder/data.zip" in the server - And user "Carol" has logged in using the webUI - When the user renames folder "simple-folder" to "new-simple-folder" using the webUI - And the user shares folder "new-simple-folder" with group "grp1" as "Editor" using the webUI - And the user re-logs in as "Alice" using the webUI - And the user opens folder "Shares" using the webUI - And the user opens folder "new-simple-folder" using the webUI - Then as "Alice" the content of "/Shares/new-simple-folder/lorem.txt" in the server should not be the same as the content of local file "lorem.txt" - # overwrite an existing file in the received share - When the user uploads overwriting file "lorem.txt" using the webUI - Then file "lorem.txt" should be listed on the webUI - And as "Alice" the content of "/Shares/new-simple-folder/lorem.txt" in the server should be the same as the content of local file "lorem.txt" - # upload a new file into the received share - When the user uploads file "new-lorem.txt" using the webUI - Then as "Alice" the content of "/Shares/new-simple-folder/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - # delete a file in the received share - When the user deletes file "data.zip" using the webUI - Then file "data.zip" should not be listed on the webUI - # check that the file actions by the sharee are visible to another group member - When the user re-logs in as "Brian" using the webUI - And the user opens folder "Shares" using the webUI - And the user opens folder "new-simple-folder" using the webUI - Then as "Brian" the content of "/Shares/new-simple-folder/lorem.txt" in the server should be the same as the content of local file "lorem.txt" - And as "Brian" the content of "/Shares/new-simple-folder/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - And file "data.zip" should not be listed on the webUI - # check that the file actions by the sharee are visible for the share owner - When the user re-logs in as "Carol" using the webUI - And the user opens folder "new-simple-folder" using the webUI - Then as "Carol" the content of "new-simple-folder/lorem.txt" in the server should be the same as the content of local file "lorem.txt" - And as "Carol" the content of "new-simple-folder/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - And file "data.zip" should not be listed on the webUI - - @issue-4102 @skipOnOCIS - Scenario: share a folder with an internal group and a member unshares the folder - Given user "Carol" has created folder "simple-folder" in the server - And user "Carol" has uploaded file with content "lorem content" to "simple-folder/lorem.txt" in the server - And user "Carol" has logged in using the webUI - When the user renames folder "simple-folder" to "new-simple-folder" using the webUI - And the user shares folder "new-simple-folder" with group "grp1" as "Editor" using the webUI - # unshare the received shared folder and check it is gone - And the user re-logs in as "Alice" using the webUI - And the user opens folder "Shares" using the webUI - And the user deletes folder "new-simple-folder" using the webUI - Then folder "new-simple-folder" should not be listed on the webUI - # check that the folder is still visible to another group member - When the user re-logs in as "Brian" using the webUI - And the user opens folder "Shares" using the webUI - Then folder "new-simple-folder" should be listed on the webUI - When the user opens folder "new-simple-folder" using the webUI - Then file "lorem.txt" should be listed on the webUI - And the content of file "/Shares/new-simple-folder/lorem.txt" for user "Brian" should be "lorem content" in the server - # check that the folder is still visible for the share owner - When the user re-logs in as "Carol" using the webUI - Then folder "new-simple-folder" should be listed on the webUI - When the user opens folder "new-simple-folder" using the webUI - Then file "lorem.txt" should be listed on the webUI - And the content of file "/new-simple-folder/lorem.txt" for user "Carol" should be "lorem content" in the server - Scenario: user shares the file/folder with a group and delete the share with group Given user "Alice" has created file "lorem.txt" in the server @@ -182,17 +56,6 @@ Feature: Sharing files and folders with internal groups And as "Brian" file "/Shares/lorem.txt" should not exist in the server But as "Carol" file "/Shares/lorem.txt" should exist in the server - @issue-ocis-1328 @skipOnOCIS - Scenario: Auto-completion for a group that is excluded from receiving shares - Given group "system-group" has been created in the server - And user "Alice" has created folder "simple-folder" in the server - And the administrator has excluded group "system-group" from receiving shares in the server - When the user re-logs in as "Alice" using the webUI - And the user browses to the files page - And the user opens the share dialog for folder "simple-folder" using the webUI - And the user types "system-group" in the share-with-field - Then the autocomplete list should not be displayed on the webUI - Scenario: share a folder with other group and then it should be listed on Shared with Others page Given user "Alice" has created folder "simple-folder" in the server diff --git a/tests/acceptance/features/webUISharingInternalGroupsSharingIndicator/shareWithGroups.feature b/tests/acceptance/features/webUISharingInternalGroupsSharingIndicator/shareWithGroups.feature index c1dadece853..15f5bae3871 100644 --- a/tests/acceptance/features/webUISharingInternalGroupsSharingIndicator/shareWithGroups.feature +++ b/tests/acceptance/features/webUISharingInternalGroupsSharingIndicator/shareWithGroups.feature @@ -36,65 +36,6 @@ Feature: Sharing files and folders with internal groups | fileName | expectedIndicators | | inside.txt | user-indirect | - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS @issue-2060 @issue-6894 - Scenario: sharing indicator of items inside a re-shared folder - Given user "Alice" has created folder "simple-folder" in the server - And user "Alice" has created folder "simple-folder/simple-empty-folder" in the server - And user "Alice" has created file "simple-folder/lorem.txt" in the server - And user "Alice" has shared folder "simple-folder" with user "Brian" in the server - And user "Brian" has shared folder "Shares/simple-folder" with group "grp1" in the server - When user "Brian" has logged in using the webUI - And the user opens folder "Shares" using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | simple-folder | user-direct | - And the user opens folder "simple-folder" using the webUI - And the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | simple-empty-folder | user-indirect | - | lorem.txt | user-indirect | - - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS @issue-2060 - Scenario: sharing indicator of items inside a re-shared subfolder - Given user "Alice" has created folder "simple-folder" in the server - And user "Alice" has created folder "simple-folder/simple-empty-folder" in the server - And user "Alice" has created file "simple-folder/lorem.txt" in the server - And user "Alice" has shared folder "simple-folder" with user "Brian" in the server - And user "Brian" has shared folder "/Shares/simple-folder/simple-empty-folder" with group "grp1" in the server - When user "Brian" has logged in using the webUI - And the user opens folder "Shares" using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | simple-folder | user-indirect | - When the user opens folder "simple-folder" using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | simple-empty-folder | user-direct | - | lorem.txt | user-indirect | - - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS @issue-2060 - Scenario: sharing indicator of items inside an incoming shared folder - Given user "Alice" has created folder "simple-folder" in the server - And user "Alice" has created folder "simple-folder/simple-empty-folder" in the server - And user "Alice" has created file "simple-folder/lorem.txt" in the server - And user "Alice" has shared folder "simple-folder" with user "Brian" in the server - When user "Brian" has logged in using the webUI - And the user opens folder "Shares" using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | simple-folder | user-indirect | - When the user opens folder "simple-folder" using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | simple-empty-folder | user-indirect | - | lorem.txt | user-indirect | - @issue-2060 Scenario: no sharing indicator of items inside a not shared folder Given user "Brian" has created folder "simple-folder" in the server diff --git a/tests/acceptance/features/webUISharingInternalUsers/shareWithUsers.feature b/tests/acceptance/features/webUISharingInternalUsers/shareWithUsers.feature index 83849dfdf2c..50ae6c89d43 100644 --- a/tests/acceptance/features/webUISharingInternalUsers/shareWithUsers.feature +++ b/tests/acceptance/features/webUISharingInternalUsers/shareWithUsers.feature @@ -11,119 +11,6 @@ Feature: Sharing files and folders with internal users | Brian | And user "Brian" has created folder "simple-folder" in the server - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @smokeTest @disablePreviews @skipOnOCIS - Scenario Outline: share a file & folder with another internal user - Given user "Brian" has created file "testimage.jpg" in the server - And user "Brian" has created file "simple-folder/lorem.txt" in the server - And user "Brian" has logged in using the webUI - When the user shares folder "simple-folder" with user "Alice Hansen" as "" using the webUI - And the user shares file "testimage.jpg" with user "Alice Hansen" as "" using the webUI - Then user "Alice Hansen" should be listed as "" in the collaborators list for folder "simple-folder" on the webUI - And user "Alice Hansen" should be listed as "" in the collaborators list for file "testimage.jpg" on the webUI - And user "Alice" should have received a share with these details in the server: - | field | value | - | uid_owner | Brian | - | share_with | Alice | - | file_target | /Shares/simple-folder | - | item_type | folder | - | permissions | | - And user "Alice" should have received a share with these details in the server: - | field | value | - | uid_owner | Brian | - | share_with | Alice | - | file_target | /Shares/testimage.jpg | - | item_type | file | - | permissions | | - When the user re-logs in as "Alice" using the webUI - And the user opens folder "Shares" using the webUI - Then these files should be listed on the webUI - | files | - | simple-folder | - | testimage.jpg | - Examples: - | set-role | expected-role | permissions-folder | permissions-file | - | Viewer | Can view | read,share | read, share | - | Editor | Can edit | read,update,create,delete,share | read,update,share | - | Custom permissions | Custom permissions | read | read | - - @issue-4102 @issue-ocis-2267 @disablePreviews @issue-6896 @notToImplementOnOCIS - Scenario: share a file with another internal user who overwrites and unshares the file - Given user "Brian" has created file "lorem.txt" in the server - And user "Brian" has logged in using the webUI - And user "Brian" has renamed file "lorem.txt" to "new-lorem.txt" in the server - And user "Brian" has shared file "new-lorem.txt" with user "Alice" with "all" permissions in the server - When the user re-logs in as "Alice" using the webUI - And the user opens folder "Shares" using the webUI - Then as "Alice" the content of "Shares/new-lorem.txt" in the server should not be the same as the content of local file "new-lorem.txt" - # overwrite the received shared file - When the user uploads overwriting file "new-lorem.txt" using the webUI - Then file "new-lorem.txt" should be listed on the webUI - And as "Alice" the content of "Shares/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - # unshare the received shared file - When the user deletes file "new-lorem.txt" using the webUI - Then file "new-lorem.txt" should not be listed on the webUI - # check that the original file owner can still see the file - And as "Brian" the content of "new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - - @disablePreviews @skipOnOCIS - Scenario: share a folder with another internal user who uploads, overwrites and deletes files - Given user "Brian" has created file "simple-folder/lorem.txt" in the server - And user "Brian" has created file "simple-folder/data.zip" in the server - And user "Brian" has logged in using the webUI - When the user shares folder "simple-folder" with user "Alice Hansen" as "Editor" using the webUI - And the user re-logs in as "Alice" using the webUI - And the user browses to the folder "Shares" on the files page - And the user reloads the current page of the webUI - And the user opens folder "simple-folder" using the webUI - Then as "Alice" the content of "Shares/simple-folder/lorem.txt" in the server should not be the same as the content of local file "lorem.txt" - # overwrite an existing file in the received share - When the user uploads overwriting file "lorem.txt" using the webUI - Then file "lorem.txt" should be listed on the webUI - And as "Alice" the content of "Shares/simple-folder/lorem.txt" in the server should be the same as the content of local file "lorem.txt" - # upload a new file into the received share - When the user uploads file "new-lorem.txt" using the webUI - Then as "Alice" the content of "Shares/simple-folder/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - # delete a file in the received share - When the user deletes file "data.zip" using the webUI - Then file "data.zip" should not be listed on the webUI - # check that the file actions by the sharee are visible for the share owner - When the user re-logs in as "Brian" using the webUI - And the user opens folder "simple-folder" using the webUI - Then file "lorem.txt" should be listed on the webUI - And as "Brian" the content of "simple-folder/lorem.txt" in the server should be the same as the content of local file "lorem.txt" - And file "new-lorem.txt" should be listed on the webUI - And as "Brian" the content of "simple-folder/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - But file "data.zip" should not be listed on the webUI - - @issue-product-270 @disablePreviews @skipOnOCIS - Scenario: share a folder with another internal user who unshares the folder - Given user "Brian" has uploaded file with content "text file" to "simple-folder/lorem.txt" in the server - And user "Brian" has logged in using the webUI - When the user renames folder "simple-folder" to "new-simple-folder" using the webUI - And the user shares folder "new-simple-folder" with user "Alice Hansen" as "Editor" using the webUI - # unshare the received shared folder and check it is gone - And the user re-logs in as "Alice" using the webUI - And the user browses to the folder "Shares" on the files page - Then folder "new-simple-folder" should be listed on the webUI - And the user deletes folder "new-simple-folder" using the webUI - And folder "new-simple-folder" should not be listed on the webUI - # check that the folder is still visible for the share owner - When the user re-logs in as "Brian" using the webUI - Then folder "new-simple-folder" should be listed on the webUI - And the content of file "new-simple-folder/lorem.txt" for user "Brian" should be "text file" in the server - - @issue-product-270 @disablePreviews @skipOnOCIS - Scenario: share a folder with another internal user and prohibit deleting - Given user "Brian" has created file "simple-folder/lorem.txt" in the server - And user "Brian" has logged in using the webUI - And user "Brian" has shared folder "simple-folder" with user "Alice" with "create, read, share" permissions in the server - When the user re-logs in as "Alice" using the webUI - And the user opens folder "Shares" using the webUI - And the user opens folder "simple-folder" using the webUI - Then it should not be possible to delete file "lorem.txt" using the webUI - @issue-ocis-2260 @disablePreviews Scenario: user shares the file/folder with multiple internal users and delete the share with one user Given user "Carol" has been created with default attributes and without skeleton files in the server @@ -181,60 +68,6 @@ Feature: Sharing files and folders with internal users When the user opens the details dialog for file "lorem.txt" using the webUI Then the shared-via path in the details dialog should be "/simple-folder" - # Share permission is not available in oCIS webUI so when setting all permissions, it is displayed as "Custom permissions" there - @issue-2897 @issue-ocis-2260 @disablePreviews @skipOnOCIS - Scenario: sharing details of items inside a re-shared folder ("via" info) - Given user "Alice" has created folder "simple-folder" in the server - And user "Alice" has created folder "simple-folder/simple-empty-folder" in the server - And user "Carol" has been created with default attributes and without skeleton files in the server - And user "Alice" has uploaded file with content "test" to "/simple-folder/lorem.txt" in the server - And user "Alice" has shared folder "simple-folder" with user "Brian" in the server - And user "Brian" has shared folder "Shares/simple-folder" with user "Carol" in the server - And user "Brian" has logged in using the webUI - And the user has opened folder "Shares" - And the user has opened folder "simple-folder" - When the user opens the details dialog for folder "simple-empty-folder" using the webUI - Then the shared-via path in the details dialog should be "/Shares/simple-folder" - When the user opens the details dialog for file "lorem.txt" using the webUI - Then the shared-via path in the details dialog should be "/Shares/simple-folder" - - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS @disablePreviews - Scenario Outline: Share files/folders with special characters in their name - Given user "Brian" has created folder "Sample,Folder,With,Comma" in the server - And user "Brian" has created file "sample,1.txt" in the server - And user "Brian" has logged in using the webUI - When the user shares folder "Sample,Folder,With,Comma" with user "Alice Hansen" as "" using the webUI - And the user shares file "sample,1.txt" with user "Alice Hansen" as "" using the webUI - Then user "Alice Hansen" should be listed as "" in the collaborators list for folder "Sample,Folder,With,Comma" on the webUI - And user "Alice Hansen" should be listed as "" in the collaborators list for file "sample,1.txt" on the webUI - And user "Alice" should have received a share with these details in the server: - | field | value | - | uid_owner | Brian | - | share_with | Alice | - | file_target | /Shares/Sample,Folder,With,Comma | - | item_type | folder | - | permissions | | - And user "Alice" should have received a share with these details in the server: - | field | value | - | uid_owner | Brian | - | share_with | Alice | - | file_target | /Shares/sample,1.txt | - | item_type | file | - | permissions | | - When the user re-logs in as "Alice" using the webUI - And the user opens folder "Shares" using the webUI - Then these files should be listed on the webUI - | files | - | Sample,Folder,With,Comma | - | sample,1.txt | - Examples: - | set-role | expected-role | permissions-folder | permissions-file | - | Viewer | Can view | read,share | read,share | - | Editor | Can edit | read,update,create,delete,share | read,update,share | - | Custom permissions | Custom permissions | read | read | - @issue-4192 @disablePreviews Scenario: sharing file after renaming it is possible Given user "Alice" has created file "lorem.txt" in the server diff --git a/tests/acceptance/features/webUISharingInternalUsersShareWithPage/shareWithUsers.feature b/tests/acceptance/features/webUISharingInternalUsersShareWithPage/shareWithUsers.feature index bb65b93b576..6cda890524c 100644 --- a/tests/acceptance/features/webUISharingInternalUsersShareWithPage/shareWithUsers.feature +++ b/tests/acceptance/features/webUISharingInternalUsersShareWithPage/shareWithUsers.feature @@ -87,17 +87,6 @@ Feature: Shares in share-with pages And the user browses to the files page Then folder "Shares" should not be listed on the webUI - @skipOnOCIS - Scenario: unsharing an entry on the shared-with-me page unshares from self - Given user "Alice" has created folder "simple-folder" in the server - And user "Alice" has shared folder "simple-folder" with user "Brian" in the server - And user "Brian" has logged in using the webUI - When the user browses to the shared-with-me page - And the user unshares folder "simple-folder" using the webUI - And the user browses to the files page - And the user opens folder "Shares" using the webUI - Then folder "simple-folder" should not be listed on the webUI - @issue-4582 @issue-ocis-2266 Scenario: unsharing multiple entries on the shared-with-me page Given user "Alice" has created folder "simple-folder" in the server diff --git a/tests/acceptance/features/webUISharingPermissionsUsers/sharePermissionsUsers.feature b/tests/acceptance/features/webUISharingPermissionsUsers/sharePermissionsUsers.feature index 7bc494c8071..9126111f77a 100644 --- a/tests/acceptance/features/webUISharingPermissionsUsers/sharePermissionsUsers.feature +++ b/tests/acceptance/features/webUISharingPermissionsUsers/sharePermissionsUsers.feature @@ -171,22 +171,3 @@ Feature: Sharing files and folders with internal users with different permission | file_target | /Shares/simple-folder | | item_type | folder | | permissions | delete, read, update | - - # this scenario is skipped on ocis because it opens share folder which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS - Scenario: User is allowed to update permissions of a reshared sub-folder within the permissions that the user has received - Given user "Carol" has been created with default attributes and without skeleton files in the server - And user "Brian" has shared folder "simple-folder" with user "Alice" with "all" permissions in the server - And user "Alice" has shared folder "/Shares/simple-folder" with user "Carol" with "share, delete" permissions in the server - And user "Alice" has logged in using the webUI - When the user opens folder "Shares" using the webUI - And the user opens folder "simple-folder" using the webUI - And the user shares folder "simple-empty-folder" with user "Carol King" as "Custom permissions" with permissions "share, delete, create, update" using the webUI - Then user "Carol" should have received a share with these details in the server: - | field | value | - | uid_owner | Alice | - | share_with | Carol | - | file_target | /Shares/simple-empty-folder | - | item_type | folder | - | permissions | all | diff --git a/tests/acceptance/features/webUISharingPublicBasic/publicLinkEdit.feature b/tests/acceptance/features/webUISharingPublicBasic/publicLinkEdit.feature index e2add85638e..9cb3a4f25ca 100644 --- a/tests/acceptance/features/webUISharingPublicBasic/publicLinkEdit.feature +++ b/tests/acceptance/features/webUISharingPublicBasic/publicLinkEdit.feature @@ -7,57 +7,6 @@ Feature: Edit public link shares Background: Given user "Alice" has been created with default attributes and without skeleton files in the server - @issue-ocis-1328 @skipOnOCIS - Scenario Outline: user tries to change the role of an existing public link role without entering share password while enforce password for that role is enforced - Given the setting "" of app "core" has been set to "yes" in the server - And user "Alice" has created folder "simple-folder" in the server - And user "Alice" has created a public link with following settings in the server - | path | simple-folder | - | name | Public-link | - | permissions | | - And user "Alice" has logged in using the webUI - When the user tries to edit the public link named "Public-link" of folder "simple-folder" changing the role to "" - Then the user should see a password modal dialog with message "Passwords for links are required." on the webUI - # Doesn't check settings the password - And user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | | - | path | /simple-folder | - Examples: - | initial-permissions | role | setting-name | - | read, create | Viewer | shareapi_enforce_links_password_read_only | - | read | Contributor | shareapi_enforce_links_password_read_write | - | read | Editor | shareapi_enforce_links_password_read_write_delete | - | read, create | Uploader | shareapi_enforce_links_password_write_only | - - @issue-ocis-1328 @skipOnOCIS - Scenario Outline: user tries to delete the password of an existing public link role while enforce password for that role is enforced - Given the setting "" of app "core" has been set to "yes" in the server - And user "Alice" has created folder "simple-folder" in the server - And user "Alice" has created a public link with following settings in the server - | path | simple-folder | - | name | Public-link | - | permissions | | - | password | 123 | - And user "Alice" has logged in using the webUI - When the user opens the link edit dialog of folder "simple-folder" with name "Public-link" using the webUI - Then it should not be possible to remove password for the link with name "Public-link" - And user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | | - | path | /simple-folder | - Examples: - | initial-permissions | setting-name | - | read | shareapi_enforce_links_password_read_only | - | read, create | shareapi_enforce_links_password_read_write | - | read, update, create, delete | shareapi_enforce_links_password_read_write_delete | - | create | shareapi_enforce_links_password_write_only | - - Scenario: user edits a name of an already existing public link Given user "Alice" has created folder "simple-folder" in the server And user "Alice" has created file "simple-folder/lorem.txt" in the server diff --git a/tests/acceptance/features/webUISharingPublicDifferentRoles/shareByPublicLinkDifferentRoles.feature b/tests/acceptance/features/webUISharingPublicDifferentRoles/shareByPublicLinkDifferentRoles.feature index d91ca3ff8fe..b49511f064d 100644 --- a/tests/acceptance/features/webUISharingPublicDifferentRoles/shareByPublicLinkDifferentRoles.feature +++ b/tests/acceptance/features/webUISharingPublicDifferentRoles/shareByPublicLinkDifferentRoles.feature @@ -54,8 +54,7 @@ Feature: Share by public link with different roles | Editor | Anyone with the link can edit | read, update, create, delete | | Contributor | Anyone with the link can upload | read, create | - @skipOnOC10 @issue-ocis-reva-383 - #after fixing the issue delete this scenario and use the one above by deleting the @skipOnOCIS tag there + @issue-ocis-reva-383 Scenario Outline: simple sharing by public link with different roles (ocis bug demonstration) Given user "Alice" has created file "simple-folder/lorem.txt" in the server And user "Alice" has logged in using the webUI @@ -91,8 +90,7 @@ Feature: Share by public link with different roles When the public uses the webUI to access the last public link created by user "Alice" in a new session Then the user should be redirected to the files-drop page - @skipOnOC10 @issue-ocis-reva-383 - #after fixing the issue delete this scenario and use the one above by deleting the @skipOnOCIS tag there + @issue-ocis-reva-383 Scenario: sharing by public link with "Uploader" role (ocis bug demonstration) Given user "Alice" has logged in using the webUI And the user creates a new public link for folder "simple-folder" using the webUI @@ -289,18 +287,3 @@ Feature: Share by public link with different roles | new-lorem.txt | And as "Alice" the content of "simple-folder/'single'quotes.txt" in the server should be the same as the content of local file "'single'quotes.txt" And as "Alice" the content of "simple-folder/new-lorem.txt" in the server should be the same as the content of local file "new-lorem.txt" - - @issue-ocis-1328 @skipOnOCIS - Scenario: user tries to create a public link with Viewer role without entering share password while enforce password on read only public share is enforced - Given the setting "shareapi_enforce_links_password_read_only" of app "core" has been set to "yes" in the server - And user "Alice" has logged in using the webUI - When the user creates a new public link for folder "simple-folder" using the webUI - Then user "Alice" should not have created any shares in the server - When the user sets a password "#Passw0rd" for the public link in the modal - Then user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | read | - | path | /simple-folder | - | name | Link | diff --git a/tests/acceptance/features/webUISharingPublicExpire/shareByPublicLinkExpiringLinks.feature b/tests/acceptance/features/webUISharingPublicExpire/shareByPublicLinkExpiringLinks.feature deleted file mode 100644 index 12b211befe6..00000000000 --- a/tests/acceptance/features/webUISharingPublicExpire/shareByPublicLinkExpiringLinks.feature +++ /dev/null @@ -1,141 +0,0 @@ -@mailhog @public_link_share-feature-required -Feature: Share by public link - As a user - I want to be able to set an expiry date on my public links - So that I don't have to remember to unshare - - Background: - Given user "Alice" has been created with default attributes and without skeleton files in the server - - @skip - Scenario: user changes the expiration date of an already existing public link using webUI - Given user "Alice" has created file "lorem.txt" in the server - And user "Alice" has created a public link with following settings in the server - | path | lorem.txt | - | name | Public link | - | expireDate | +10 | - And user "Alice" has logged in using the webUI - When the user edits the public link named "Public link" of file "lorem.txt" changing expireDate to "+5" - Then user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | name | Public link | - | uid_owner | Alice | - | expiration | +5 | - - @issue-ocis-1328 @skipOnOCIS - Scenario Outline: auto set expiration date on public link (with default amount of expiry days) - Given the setting "shareapi_default_expire_date" of app "core" has been set to "yes" in the server - And user "Alice" has created "" in the server - And user "Alice" has logged in using the webUI - When the user creates a new public link for resource "" using the webUI - Then user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | read | - | path | / | - | name | Link | - | expiration | +7 | - Examples: - | element | shared-resource | - | file | lorem.txt | - | folder | simple-folder | - - @issue-ocis-1328 @skipOnOCIS - Scenario Outline: auto set expiration date on public link (with set amount expiry days) - Given the setting "shareapi_default_expire_date" of app "core" has been set to "yes" in the server - And the setting "shareapi_expire_after_n_days" of app "core" has been set to "42" in the server - And user "Alice" has created "" in the server - And user "Alice" has logged in using the webUI - When the user creates a new public link for resource "" using the webUI - Then user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | read | - | path | / | - | name | Link | - | expiration | +42 | - Examples: - | element | shared-resource | - | file | lorem.txt | - | folder | simple-folder | - - @issue-ocis-1328 @skipOnOCIS - Scenario: user cannot change the expiry date of an existing public link to a date that is past the enforced max expiry date - Given the setting "shareapi_default_expire_date" of app "core" has been set to "yes" in the server - And the setting "shareapi_enforce_expire_date" of app "core" has been set to "yes" in the server - And user "Alice" has created file "lorem.txt" in the server - And user "Alice" has created a public link with following settings in the server - | path | lorem.txt | - | name | Public link | - | expireDate | +6 | - And user "Alice" has logged in using the webUI - When the user tries to edit expiration of the public link named "Public link" of file "lorem.txt" to past date "+15 days" - Then user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | read | - | path | /lorem.txt | - | name | Public link | - | expiration | +6 | - - @issue-ocis-1328 @skipOnOCIS - Scenario: user cannot change the expiry date on existing public link to a date past the enforced max expiry date once max expiry date is changed - Given the setting "shareapi_default_expire_date" of app "core" has been set to "yes" in the server - And the setting "shareapi_expire_after_n_days" of app "core" has been set to "16" in the server - And the setting "shareapi_enforce_expire_date" of app "core" has been set to "yes" in the server - And user "Alice" has created file "lorem.txt" in the server - And user "Alice" has created a public link with following settings in the server - | path | lorem.txt | - | name | Public link | - | expireDate | +16 | - And user "Alice" has logged in using the webUI - And the setting "shareapi_expire_after_n_days" of app "core" has been set to "7" in the server - When the user edits the public link named "Public link" of file "lorem.txt" changing expireDate to "+15" - And user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | read | - | path | /lorem.txt | - | name | Public link | - | expiration | +16 | - - @issue-ocis-1328 @skipOnOCIS - Scenario: user can set an expiry date when creating a public link to a date that is before the enforced max expiry date - Given the setting "shareapi_default_expire_date" of app "core" has been set to "yes" in the server - And the setting "shareapi_enforce_expire_date" of app "core" has been set to "yes" in the server - And user "Alice" has created file "lorem.txt" in the server - And user "Alice" has logged in using the webUI - When the user creates a new public link for resource "lorem.txt" using the webUI - Then user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | read | - | path | /lorem.txt | - | name | Link | - | expiration | +7 | - - @issue-ocis-1328 @skipOnOCIS @skip - Scenario: user can change the expiry date of an existing public link to a date that is before the enforced max expiry date - Given the setting "shareapi_default_expire_date" of app "core" has been set to "yes" in the server - And the setting "shareapi_enforce_expire_date" of app "core" has been set to "yes" in the server - And user "Alice" has created file "lorem.txt" in the server - And user "Alice" has created a public link with following settings in the server - | path | lorem.txt | - | name | Public link | - | expireDate | +5 | - And user "Alice" has logged in using the webUI - When the user edits the public link named "Public link" of file "lorem.txt" changing expireDate to "+7" - Then user "Alice" should have a share with these details in the server: - | field | value | - | share_type | public_link | - | uid_owner | Alice | - | permissions | read | - | path | /lorem.txt | - | name | Public link | - | expiration | +7 | diff --git a/tests/acceptance/features/webUISharingPublicManagement/publicLinkIndicator.feature b/tests/acceptance/features/webUISharingPublicManagement/publicLinkIndicator.feature index 96a3236390e..a93ad6db9af 100644 --- a/tests/acceptance/features/webUISharingPublicManagement/publicLinkIndicator.feature +++ b/tests/acceptance/features/webUISharingPublicManagement/publicLinkIndicator.feature @@ -60,58 +60,6 @@ Feature: Public link share indicator | sub-folder | link-indirect,user-indirect | | textfile.txt | link-indirect,user-indirect | - # this scenario is skipped on ocis because it makes request to shared folder in root (All Files) which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS @issue-2060 - Scenario: sharing indicators public link from reshare - Given user "Brian" has been created with default attributes and without skeleton files in the server - And user "Alice" has created folder "/simple-folder/sub-folder" in the server - And user "Alice" has uploaded file with content "test" to "/simple-folder/textfile.txt" in the server - And user "Alice" has shared folder "simple-folder" with user "Brian" in the server - And user "Brian" has shared folder "simple-folder" with link with "read" permissions in the server - When user "Brian" has logged in using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | simple-folder | link-direct,user-indirect | - When the user opens folder "simple-folder" using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | sub-folder | link-indirect,user-indirect | - | textfile.txt | link-indirect,user-indirect | - - # this scenario is skipped on ocis because it makes request to shared folder in root (All Files) which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS @issue-2060 - Scenario: sharing indicators public link from child of reshare - Given user "Brian" has been created with default attributes and without skeleton files in the server - And user "Alice" has created folder "/simple-folder/sub-folder" in the server - And user "Alice" has uploaded file with content "test" to "/simple-folder/textfile.txt" in the server - And user "Alice" has shared folder "simple-folder" with user "Brian" in the server - And user "Brian" has shared folder "simple-folder/sub-folder" with link with "read" permissions in the server - When user "Brian" has logged in using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | simple-folder | user-indirect | - When the user opens folder "simple-folder" using the webUI - Then the following resources should have share indicators on the webUI - | fileName | expectedIndicators | - | sub-folder | link-direct,user-indirect | - | textfile.txt | user-indirect | - - # this scenario is skipped on ocis because it makes request to shared folder in root (All Files) which in not possible in OCIS - # but it works for OC10 see issue https://github.com/owncloud/web/issues/6896 for more detail - @skipOnOCIS @issue-2060 - Scenario: no sharing indicator visible in file list from public link - Given user "Brian" has been created with default attributes and without skeleton files in the server - And user "Carol" has been created with default attributes and without skeleton files in the server - And user "Alice" has created folder "simple-folder/simple-empty-folder" in the server - And user "Alice" has shared folder "simple-folder" with user "Brian" in the server - And user "Brian" has shared folder "simple-folder/simple-empty-folder" with user "Carol" in the server - And user "Brian" has shared folder "simple-folder" with link with "read" permissions in the server - When the public uses the webUI to access the last public link created by user "Brian" in a new session - Then the following resources should not have share indicators on the webUI - | simple-empty-folder | - @issue-2939 Scenario: sharing indicator for link shares stays up to date Given user "Brian" has been created with default attributes and without skeleton files in the server diff --git a/tests/acceptance/features/webUITrashbinFilesFolders/trashbinFilesFolders.feature b/tests/acceptance/features/webUITrashbinFilesFolders/trashbinFilesFolders.feature index fc388a44471..3b4cdfa2704 100644 --- a/tests/acceptance/features/webUITrashbinFilesFolders/trashbinFilesFolders.feature +++ b/tests/acceptance/features/webUITrashbinFilesFolders/trashbinFilesFolders.feature @@ -19,100 +19,6 @@ Feature: files and folders exist in the trashbin after being deleted And user "Alice" has uploaded file "lorem.txt" to "strängé नेपाली folder/lorem.txt" in the server And user "Alice" has logged in using the webUI - @smokeTest @ocisSmokeTest @ocis-reva-issue-111 @skipOnOCIS @issue-product-186 @disablePreviews - Scenario: Delete files & folders one by one and check that they are all in the trashbin - When the user deletes the following elements using the webUI - | name | - | simple-folder | - | lorem.txt | - | strängé नेपाली folder | - | strängé filename (duplicate #2 &).txt | - And the user browses to the trashbin page - Then as "Alice" folder "simple-folder" should exist in the trashbin in the server - And as "Alice" file "lorem.txt" should exist in the trashbin in the server - And as "Alice" folder "strängé नेपाली folder" should exist in the trashbin in the server - And as "Alice" file "strängé filename (duplicate #2 &).txt" should exist in the trashbin in the server - And the deleted elements should be listed on the webUI - - @ocis-reva-issue-111 @skipOnOCIS @issue-product-183 @issue-product-186 @disablePreviews - Scenario: Delete a file with problematic characters and check it is in the trashbin - Given user "Alice" has renamed the following files in the server - | from-name-parts | to-name-parts | - | lorem.txt | 'single' | - | lorem-big.txt | "double" quotes | - | textfile0.txt | question? | - | testimage.png | &and#hash | - | sample,1.txt | sämple,1.txt | - When the user reloads the current page of the webUI - And the user deletes the following elements using the webUI - | name-parts | - | 'single' | - | "double" quotes | - | question? | - | &and#hash | - | sämple,1.txt | - And the user browses to the trashbin page - Then these files should be listed on the webUI - | files | - | 'single' | - | "double" quotes | - | question? | - | &and#hash | - | sämple,1.txt | - - @skipOnOCIS @issue-product-186 @skipOnOC10 @issue-4582 - Scenario: Delete multiple files at once and check that they are all in the trashbin - When the user batch deletes these files using the webUI - | name | - | Folder,With,Comma | - | simple-folder | - | data.zip | - | lorem.txt | - | sample,1.txt | - And the user browses to the trashbin page - Then as "Alice" file "data.zip" should exist in the trashbin in the server - And as "Alice" file "lorem.txt" should exist in the trashbin in the server - And as "Alice" file "sample,1.txt" should exist in the trashbin in the server - And as "Alice" folder "simple-folder" should exist in the trashbin in the server - And as "Alice" folder "Folder,With,Comma" should exist in the trashbin in the server - And as "Alice" the file with original path "simple-folder/lorem.txt" should exist in the trashbin in the server - And the deleted elements should be listed on the webUI - - @skipOnOCIS @issue-1725 @issue-1910 @issue-product-186 - Scenario: Delete an empty folder and check it is in the trashbin - Given user "Alice" has created folder "my-empty-folder" in the server - And user "Alice" has created folder "my-other-empty-folder" in the server - When the user reloads the current page of the webUI - And the user deletes folder "my-empty-folder" using the webUI - Then as "Alice" folder "my-empty-folder" should exist in the trashbin in the server - But as "Alice" the folder with original path "my-other-empty-folder" should not exist in the trashbin in the server - When the user browses to the trashbin page - Then folder "my-empty-folder" should be listed on the webUI - But folder "my-other-empty-folder" should not be listed on the webUI - # Uncomment after https://github.com/owncloud/web/issues/1725 is solved - #When the user opens folder "my-empty-folder" using the webUI - #Then there should be no resources listed on the webUI - - @skipOnOCIS @issue-product-186 @disablePreviews - Scenario: Delete multiple file with same filename and check they are in the trashbin - When the user deletes the following elements using the webUI - | name | - | lorem.txt | - And the user opens folder "simple-folder" using the webUI - And the user deletes the following elements using the webUI - | name | - | lorem.txt | - And the user browses to the files page - And the user opens folder "strängé नेपाली folder" using the webUI - And the user deletes the following elements using the webUI - | name | - | lorem.txt | - And the user browses to the trashbin page - Then as "Alice" the file with original path "lorem.txt" should exist in the trashbin in the server - And as "Alice" the file with original path "simple-folder/lorem.txt" should exist in the trashbin in the server - And as "Alice" the file with original path "strängé नेपाली folder/lorem.txt" should exist in the trashbin in the server - And file "lorem.txt" should be listed on the webUI - @issue-1910 Scenario: trashbin list appears empty when no deleted files exist When the user browses to the trashbin page diff --git a/tests/acceptance/package.json b/tests/acceptance/package.json index 5be8528d969..c9964332a8e 100644 --- a/tests/acceptance/package.json +++ b/tests/acceptance/package.json @@ -3,7 +3,7 @@ "description": "ownCloud web test suite", "license": "AGPL-3.0", "scripts": { - "test:acceptance:ocis": "NODE_TLS_REJECT_UNAUTHORIZED=0 cucumber-js --require-module @babel/register --require-module @babel/polyfill --require setup.js --require stepDefinitions --format @cucumber/pretty-formatter -t \"${TEST_TAGS:-not @skip and not @skipOnOCIS and not @notToImplementOnOCIS}\" -f json:report/cucumber_report.json" + "test:acceptance:ocis": "NODE_TLS_REJECT_UNAUTHORIZED=0 cucumber-js --require-module @babel/register --require-module @babel/polyfill --require setup.js --require stepDefinitions --format @cucumber/pretty-formatter -t \"${TEST_TAGS:-not @skip}\" -f json:report/cucumber_report.json" }, "devDependencies": { "@babel/core": "7.23.7",