Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

List of removed/skipped nightwatch acceptance test scenarios to be implemented in playwright #7264

Closed
SwikritiT opened this issue Jul 11, 2022 · 24 comments
Closed

List of removed/skipped nightwatch acceptance test scenarios to be implemented in playwright #7264

SwikritiT opened this issue Jul 11, 2022 · 24 comments
Labels
QA:team

Comments

@SwikritiT
Copy link
Contributor

SwikritiT commented Jul 11, 2022 •
edited
Loading

We have decided that we won't be adding/updating tests in Nightwatch.
The already written failing tests linked with the closed issues in expected to fail that need something to be implemented or updated in order for them to pass, such scenarios will be removed and we will update this list mentioning the removal, so that, if needed, they can be implemented in playwright.

Similarly, the scenarios with un-implemented steps will also be removed and mentioned here.

This issue is just for documentation of the removed scenarios so that they won't be lost. Seperate issues can be created for the implementation in playwright

cc: @individual-it @phil-davis @ScharfViktor
@SwikritiT
Copy link
Contributor Author

SwikritiT commented Jul 11, 2022 •
edited by amrita-shrestha
Loading

Sharing related scenarios: skipped in PR #7246

These scenarios are skipped in ocis because of the implementation of share jail due to which the Shares folder is no longer available on a personal level and these steps. Following skipped tests interact with the Shares folder, opening it and checking if there are certain resources present inside it or some other action.

1. Scenario: Reshare a folder without share permissions using API and check if it is listed on the collaborators list for resharer 
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 accepted the share "Shares/simple-folder" offered by user "Brian" in the server
    And user "Alice" has shared folder "Shares/simple-folder" with user "Carol" with "read" permissions in the server
    And user "Carol" has accepted the share "Shares/simple-folder" offered by user "Alice" 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
2. Scenario: Reshare a folder without share permissions using API and check if the receiver can reshare 
  Scenario: Reshare a folder without share permissions using API and check if the receiver can reshare
    Given user "Brian" has shared folder "simple-folder" with user "Alice" with "read, share" permissions in the server
    And user "Alice" has accepted the share "Shares/simple-folder" offered by user "Brian" in the server
    And user "Alice" has shared folder "/Shares/simple-folder" with user "Carol" with "read" permissions in the server
    And user "Carol" has accepted the share "Shares/simple-folder" offered by user "Alice" in the server
    When user "Carol" logs in using the webUI
    And the user opens folder "Shares" using the webUI
    Then the user should not be able to share folder "simple-folder" using the webUI
3. 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 
   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>" permissions in the server
    And user "Alice" has accepted the share "Shares/simple-folder" offered by user "Brian" 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 "<role>" with permissions "<collaborators-permissions>" using the webUI
    And user "Carol" accepts the share "Shares/simple-folder" offered by user "Alice" using the sharing API in the server
    Then user "Carol King" should be listed as "<displayed-role>" in the collaborators list for folder "simple-folder" on the webUI
    And custom permissions "<displayed-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 | <permissions>         |
    Examples:
      | role                 | displayed-role       | collaborators-permissions     | displayed-permissions         | permissions                         |
      | Viewer               | Viewer               | ,                             | share                         | read, share                         |
      | Editor               | Editor               | ,                             | 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   | Editor               | delete, share, create, update | share, delete, update, create | read, share, delete, update, create |
4. 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 
   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>" permissions in the server
    And user "Alice" has accepted the share "Shares/simple-folder" offered by user "Brian" 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 "<role>" with permissions "<collaborators-permissions>" using the webUI
    And user "Carol" accepts the share "Shares/simple-folder" offered by user "Alice" using the sharing API in the server
    And the user re-logs in as "Brian" using the webUI
    Then user "Carol King" should be listed as "<displayed-role>" in the collaborators list for folder "simple-folder" on the webUI
    And custom permissions "<displayed-permissions>" should be set for user "Carol King" for folder "simple-folder" on the webUI
    And user "Alice Hansen" should be listed as "<displayed-role>" in the collaborators list for folder "simple-folder" on the webUI
    And custom permissions "<displayed-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 | <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 | <permissions>         |
    Examples:
      | role                 | displayed-role       | collaborators-permissions         | displayed-permissions         | permissions                         |
      | Viewer               | Viewer               | ,                             | share                         | read, share                         |
      | Editor               | Editor               | ,                             | 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   | Editor               | delete, share, create, update | share, delete, update, create | read, share, delete, update, create |
5. share a file & folder with another internal user 
 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 "<set-role>" using the webUI
    And the user shares file "testimage.jpg" with group "grp1" as "<set-role>" using the webUI
    And user "Alice" accepts the share "Shares/simple-folder" offered by user "Carol" using the sharing API in the server
    And user "Brian" accepts the share "Shares/simple-folder" offered by user "Carol" using the sharing API in the server
    And user "Alice" accepts the share "Shares/testimage.jpg" offered by user "Carol" using the sharing API in the server
    And user "Brian" accepts the share "Shares/testimage.jpg" offered by user "Carol" using the sharing API in the server
    Then group "grp1" should be listed as "<expected-role>" in the collaborators list for folder "simple-folder" on the webUI
    And group "grp1" should be listed as "<expected-role>" 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 | <permissions-folder>  |
    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 | <permissions-file>    |
    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%2Fsimple-folder" on the webUI
      | entry_name |
      | lorem.txt  |
    But these resources should not be listed in the folder "/Shares%2Fsimple-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               | Viewer               | read,share                      | read,share        |
      | Editor               | Editor               | read,update,create,delete,share | read,update,share |
      | Custom permissions   | Custom permissions   | read                            | read              |
6. Scenario Outline: share a file & folder with another internal user 
  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 "<set-role>" using the webUI
    And user "Alice" accepts the share "Shares/simple-folder" offered by user "Brian" using the sharing API in the server
    And the user shares file "testimage.jpg" with user "Alice Hansen" as "<set-role>" using the webUI
    And user "Alice" accepts the share "Shares/testimage.jpg" offered by user "Brian" using the sharing API in the server
    Then user "Alice Hansen" should be listed as "<expected-role>" in the collaborators list for folder "simple-folder" on the webUI
    And user "Alice Hansen" should be listed as "<expected-role>" 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 | <permissions-folder>  |
    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 | <permissions-file>    |
    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 |
    # When the user opens the share dialog for file "simple-folder" using the webUI
    # Then user "Brian Murphy" should be listed as "Owner" in the collaborators list on the webUI
    # When the user opens the share dialog for file "testimage.jpg" using the webUI
    # Then user "Brian Murphy" should be listed as "Owner" in the collaborators list on the webUI
    Examples:
      | set-role           | expected-role      | permissions-folder              | permissions-file  |
      | Viewer             | Viewer             | read,share                      | read, share       |
      | Editor             | Editor             | read,update,create,delete,share | read,update,share |
      | Custom permissions | Custom permissions | read                            | read              |
7. Scenario Outline: Share files/folders with special characters in their name 
  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 "<set-role>" using the webUI
    And user "Alice" accepts the share "Shares/Sample,Folder,With,Comma" offered by user "Brian" using the sharing API in the server
    And the user shares file "sample,1.txt" with user "Alice Hansen" as "<set-role>" using the webUI
    And user "Alice" accepts the share "Shares/sample,1.txt" offered by user "Brian" using the sharing API in the server
    Then user "Alice Hansen" should be listed as "<expected-role>" in the collaborators list for folder "Sample,Folder,With,Comma" on the webUI
    And user "Alice Hansen" should be listed as "<expected-role>" 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 | <permissions-folder>             |
    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 | <permissions-file>   |
    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             | Viewer             | read,share                      | read,share        |
      | Editor             | Editor             | read,update,create,delete,share | read,update,share |
      | Custom permissions | Custom permissions | read                            | read              |
8. Scenario: User is allowed to update permissions of a reshared sub-folder within the permissions that the user has received 
 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 accepted the share "Shares/simple-folder" offered by user "Brian" 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
    And user "Carol" accepts the share "Shares/simple-empty-folder" offered by user "Alice" using the sharing API in the server
    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                         |
9. Scenario: share a folder with another user with share permissions and reshare without share permissions to different user, and check if user is displayed for original sharer 
Scenario: share a folder with another user with share permissions and reshare without share permissions to different user, and check if user is displayed for original sharer
    Given user "Brian" has shared folder "simple-folder" with user "Alice" with "read, share" permissions in the server
    And user "Alice" has accepted the share "Shares/simple-folder" offered by user "Brian" 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 "," using the webUI
    And user "Carol" accepts the share "Shares/simple-folder" offered by user "Alice" using the sharing API in the server
    And the user re-logs in as "Brian" 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
    And user "Alice Hansen" should be listed as "Viewer" in the collaborators list for folder "simple-folder" 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 | read, share           |
    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 | read                  |
10. Scenario: share a folder with another user with share permissions and reshare without share permissions to different user, and check if user is displayed for the receiver 
Scenario: share a folder with another user with share permissions and reshare without share permissions to different user, and check if user is displayed for the receiver
    Given user "Brian" has shared folder "simple-folder" with user "Alice" with "read, share" permissions in the server
    And user "Alice" has accepted the share "Shares/simple-folder" offered by user "Brian" 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 "Viewer" with permissions "," using the webUI
    And user "Carol" accepts the share "Shares/simple-folder" offered by user "Alice" using the sharing API in the server
    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 | read, share           |
11. Scenario: disable resharing and check if the received resource can be reshared 
  Scenario: disable resharing and check if the received resource can be reshared
    Given the setting "shareapi_allow_resharing" of app "core" has been set to "no" in the server
    And user "Brian" has created folder "simple-folder" in the server
    And user "Brian" has uploaded file "lorem.txt" to "simple-folder/lorem.txt" in the server
    And user "Brian" has shared folder "simple-folder" with user "Alice" in the server
    And user "Alice" has accepted the share "Shares/simple-folder" offered by user "Brian" in the server
    When user "Alice" logs in using the webUI
    And the user browses to the files page
    And the user opens folder "Shares" using the webUI
    When the user marks file "simple-folder" as favorite using the webUI
    Then the user should not be able to share folder "simple-folder" using the webUI
    And as "Carol" folder "simple-folder" should not exist in the server
    When the user browses to the favorites page
    Then the user should not be able to share folder "Shares/simple-folder" using the webUI
12. Scenario: disable resharing and check if the received resource from group share can be reshared 
  Scenario: disable resharing and check if the received resource from group share can be reshared
    Given the setting "shareapi_allow_resharing" of app "core" has been set to "no" in the server
    And user "Carol" has uploaded file "lorem.txt" to "lorem.txt" in the server
    And user "Carol" has shared file "lorem.txt" with group "grp1" in the server
    And user "Alice" has accepted the share "Shares/lorem.txt" offered by user "Carol" in the server
    And user "Brian" has accepted the share "Shares/lorem.txt" offered by user "Carol" in the server
    When user "Alice" logs in using the webUI
    And the user opens folder "Shares" using the webUI
    Then the user should not be able to share file "lorem.txt" using the webUI
    When the user re-logs in as "Brian" using the webUI
    And the user opens folder "Shares" using the webUI
    Then the user should not be able to share file "lorem.txt" using the webUI
13. Scenario: reshare a share that you received to a group that you are member of 
  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 user "Brian" has accepted the share "Shares/simple-folder" offered by user "Alice" 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

@SwikritiT
Copy link
Contributor Author

SwikritiT commented Jul 19, 2022 •
edited
Loading

Scenarios skipped by PR: #7289
These scenarios try to move a resource into a received share:

1. Scenario: move a file into another folder with no change permission 
Scenario: move a file into another folder with no change permission
   Given 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 move file "lorem.txt" into folder "simple-folder (2)" using the webUI
    Then as "Alice" file "simple-folder (2)/lorem.txt" should not exist in the server
2. Scenario: move a folder into another folder with no change permission 
Scenario: move a folder into another folder with no change permission
    Given 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 move folder "simple-empty-folder" into folder "simple-folder (2)" using the webUI
    Then as "Alice" folder "simple-folder (2)/simple-empty-folder" should not exist in the server

@SwikritiT
Copy link
Contributor Author

Scenarios skipped by PR: #7323

These scenarios are related to searching share autocompletion, the tests try to set a minimum length for searching and fail as the configuration for setting minimum chars in search is not the same for OCIS and OC10. Apart from that, the tests fail in assertion because there are certain inconsistencies between OCIS and OC10 behavior like displayName

1. Scenario: autocompletion of regular existing users 
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
2. Scenario: autocompletion of regular existing groups 
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
3. Scenario: autocompletion when minimum characters is increased and not enough characters are typed 
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
4. Scenario: autocomplete short user/display names when completely typed 
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
5. Scenario: autocomplete short group names when completely typed 
 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
6. Scenario: autocompletion when increasing the minimum characters for sharing autocomplete 
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
7. Scenario: autocompletion of a pattern that matches regular existing users but also a user with whom the item is already shared (folder) 
 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
8. Scenario: autocompletion of a pattern that matches regular existing users but also a user with whom the item is already shared (file) 
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
9. Scenario: autocompletion of a pattern that matches regular existing groups but also a group with whom the item is already shared (file) 
 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
10. Scenario: autocompletion of a pattern that matches regular existing groups but also a group with whom the item is already shared (folder) 
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
11. Scenario Outline: autocompletion of user having special characters in their displaynames 
 Scenario Outline: autocompletion of user having special characters in their displaynames
    Given these users have been created without initialization and without skeleton files in the server:
      | username  | password  | displayname   | email             |
      | normalusr | %regular% | <displayName> | msrmail@oc.com.np |
    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 the user has opened the share dialog for file "data.zip"
    When the user types "<search>" in the share-with-field
    Then only users and groups that contain the string "<search>" in their name or displayname should be listed in the autocomplete list on the webUI
    Examples:
      | displayName | search |
      | -_.ocusr    | -_     |
      | ocusr-_.    | oc     |
      | _ocusr@     | _u     |

@grgprarup grgprarup mentioned this issue Sep 15, 2022
Closed
5 tasks
@grgprarup
Copy link
Contributor

grgprarup commented Sep 15, 2022 •
edited
Loading

Scenarios removed by PR: #7642

These scenarios are related to locks files/folder.

1. Scenario: setting a lock shows the lock symbols at the correct files/folders 
Scenario: setting a lock shows the lock symbols at the correct files/folders
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    When the user browses to the files page
    Then folder "simple-folder" should be marked as locked on the webUI
    And file "data.zip" should be marked as locked on the webUI
    But folder "simple-empty-folder" should not be marked as locked on the webUI
    And file "data.tar.gz" should not be marked as locked on the webUI
2. Scenario: setting a lock shows the display name of a user in the locking details 
Scenario: setting a lock shows the display name of a user in the locking details
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    When the user re-logs in as "brand-new-user" using the webUI
    Then folder "simple-folder" should be marked as locked by user "New User" in the locks tab of the details panel on the webUI
    And file "data.zip" should be marked as locked by user "New User" in the locks tab of the details panel on the webUI
3. Scenario: setting a lock shows the current changed display name of a user in the locking details Scenario: setting a lock shows the current changed display name of a user in the locking details Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server | lockscope | shared | And user "brand-new-user" has locked file "data.zip" setting the following properties in the server | lockscope | exclusive | And the administrator has changed the display name of user "brand-new-user" to "Old User" When the user re-logs in as "brand-new-user" using the webUI Then folder "simple-folder" should be marked as locked by user "Old User" in the locks tab of the details panel on the webUI And file "data.zip" should be marked as locked by user "Old User" in the locks tab of the details panel on the webUI ```feature 
</details>

<details>
<summary> 4.   Scenario: setting a lock shows the display name of a user in the locking details (user has set email address)
</summary>

```feature
Scenario: setting a lock shows the display name of a user in the locking details (user has set email address)
    Given these users have been created with default attributes and without skeleton files in the server:
      | username               | displayname   | email       |
      | user-with-display-name | My fancy name | [email protected] |
    And user "user-with-display-name" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "user-with-display-name" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    When the user re-logs in as "user-with-display-name" using the webUI
    Then folder "simple-folder" should be marked as locked by user "My fancy name ([email protected])" in the locks tab of the details panel on the webUI
    And file "data.zip" should be marked as locked by user "My fancy name ([email protected])" in the locks tab of the details panel on the webUI
5. Scenario: setting a lock shows the user name of a user in the locking details (user has set email address) 
Scenario: setting a lock shows the user name of a user in the locking details (user has set email address)
    Given these users have been created with default attributes and without skeleton files in the server:
      | username        | email       |
      | user-with-email | mail@oc.org |
    And user "user-with-email" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "user-with-email" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    When the user re-logs in as "user-with-email" using the webUI
    Then folder "simple-folder" should be marked as locked by user "user-with-email ([email protected])" in the locks tab of the details panel on the webUI
    And file "data.zip" should be marked as locked by user "user-with-email ([email protected])" in the locks tab of the details panel on the webUI
6. Scenario: setting a lock shows the lock symbols at the correct files/folders on the favorites page 
  Scenario: setting a lock shows the lock symbols at the correct files/folders on the favorites page
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    When the user marks folder "simple-folder" as favorite using the webUI
    And the user marks folder "simple-empty-folder" as favorite using the webUI
    And the user marks file "data.zip" as favorite using the webUI
    And the user marks file "data.tar.gz" as favorite using the webUI
    And the user browses to the favorites page
    Then folder "simple-folder" should be marked as locked on the webUI
    And folder "simple-folder" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    But folder "simple-empty-folder" should not be marked as locked on the webUI
    And file "data.zip" should be marked as locked on the webUI
    And file "data.zip" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    But file "data.tar.gz" should not be marked as locked on the webUI
7. Scenario: setting a lock shows the lock symbols at the correct files/folders on the shared-with-others page 
  Scenario: setting a lock shows the lock symbols at the correct files/folders on the shared-with-others page
    Given these users have been created with default attributes and without skeleton files in the server:
      | username |
      | receiver |
    And user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    And user "brand-new-user" has shared file "data.zip" with user "receiver" in the server
    And user "brand-new-user" has shared file "data.tar.gz" with user "receiver" in the server
    And user "brand-new-user" has shared folder "simple-folder" with user "receiver" in the server
    And user "brand-new-user" has shared folder "simple-empty-folder" with user "receiver" in the server
    When the user browses to the shared-with-others page
    Then folder "simple-folder" should be marked as locked on the webUI
    And folder "simple-folder" should be marked as locked on the webUIAnd folder "simple-folder" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    And file "data.zip" should be marked as locked on the webUI
    And file "data.zip" should be marked as locked on the webUIAnd file "data.zip" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    But folder "simple-empty-folder" should not be marked as locked on the webUI
    And file "data.tar.gz" should not be marked as locked on the webUI
8. Scenario: setting a lock shows the lock symbols at the correct files/folders on the shared-by-link page 
  Scenario: setting a lock shows the lock symbols at the correct files/folders on the shared-by-link page
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    And user "brand-new-user" has created a public link with following settings in the server
      | path        | data.zip |
      | permissions | read     |
    And user "brand-new-user" has created a public link with following settings in the server
      | path        | data.tar.gz |
      | permissions | read        |
    And user "brand-new-user" has created a public link with following settings in the server
      | path        | simple-folder |
      | permissions | read          |
    And user "brand-new-user" has created a public link with following settings in the server
      | path        | simple-empty-folder |
      | permissions | read                |
    When the user browses to the shared-via-link page using the webUI
    Then folder "simple-folder" should be marked as locked on the webUI
    And folder "simple-folder" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    But folder "simple-empty-folder" should not be marked as locked on the webUI
    And file "data.zip" should be marked as locked on the webUI
    And file "data.zip" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    But file "data.tar.gz" should not be marked as locked on the webUI
9. Scenario: setting a lock shows the lock symbols at the correct files/folders on the shared-with-you page 
  Scenario: setting a lock shows the lock symbols at the correct files/folders on the shared-with-you page
    Given these users have been created with default attributes and without skeleton files in the server:
      | username |
      | sharer   |
    And user "sharer" has created folder "simple-folder" in the server
    And user "sharer" has created folder "simple-empty-folder" in the server
    And user "sharer" has uploaded file "data.zip" to "data.zip" in the server
    And user "sharer" has uploaded file "data.zip" to "data.tar.gz" in the server
    And user "sharer" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "sharer" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    And user "sharer" has shared file "data.zip" with user "brand-new-user" in the server
    And user "sharer" has shared file "data.tar.gz" with user "brand-new-user" in the server
    And user "sharer" has shared folder "simple-folder" with user "brand-new-user" in the server
    And user "sharer" has shared folder "simple-empty-folder" with user "brand-new-user" in the server
    When the user browses to the shared-with-me page
    Then folder "simple-folder (2)" should be marked as locked on the webUI
    And folder "simple-folder (2)" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    But folder "simple-empty-folder (2)" should not be marked as locked on the webUI
    And file "data (2).zip" should be marked as locked on the webUI
    And file "data (2).zip" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    But file "data.tar (2).gz" should not be marked as locked on the webUI
10. Scenario: clicking other tabs does not change the lock symbol 
  Scenario: clicking other tabs does not change the lock symbol
    When the user opens the share dialog for folder "simple-folder" using the webUI
    Then folder "simple-folder" should not be marked as locked on the webUI
11. Scenario: lock set on a shared file shows the lock information for all involved users 
  Scenario: lock set on a shared file shows the lock information for all involved users
    Given these users have been created with default attributes and without skeleton files in the server:
      | username  |
      | sharer    |
      | receiver  |
      | receiver2 |
    And user "sharer" has uploaded file "data.zip" to "data.zip" in the server
    And user "sharer" has uploaded file "data.zip" to "data.tar.gz" in the server
    And group "receiver-group" has been created in the server
    And user "receiver2" has been added to group "receiver-group" in the server
    And user "sharer" has shared file "data.zip" with user "receiver" in the server
    And user "sharer" has shared file "data.tar.gz" with group "receiver-group" in the server
    And user "receiver" has shared file "data.zip" with user "brand-new-user" in the server
    And user "sharer" has locked file "data.zip" setting the following properties in the server
      | lockscope | shared |
    And user "receiver" has locked file "data.zip" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked file "data (2).zip" setting the following properties in the server
      | lockscope | shared |
    And user "receiver2" has locked file "data.tar.gz" setting the following properties in the server
      | lockscope | shared |
    When the user browses to the files page
    Then file "data (2).zip" should be marked as locked on the webUI
    And file "data (2).zip" should be marked as locked by user "sharer" in the locks tab of the details panel on the webUI
    And file "data (2).zip" should be marked as locked by user "receiver" in the locks tab of the details panel on the webUI
    And file "data (2).zip" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    But file "data.zip" should not be marked as locked on the webUI
    When the user re-logs in as "sharer" using the webUI
    Then file "data.zip" should be marked as locked on the webUI
    And file "data.zip" should be marked as locked by user "sharer" in the locks tab of the details panel on the webUI
    And file "data.zip" should be marked as locked by user "receiver" in the locks tab of the details panel on the webUI
    And file "data.zip" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    And file "data.tar.gz" should be marked as locked on the webUI
    And file "data.tar.gz" should be marked as locked by user "receiver2" in the locks tab of the details panel on the webUI
    When the user re-logs in as "receiver2" using the webUI
    Then file "data.tar.gz" should be marked as locked on the webUI
    And file "data.tar.gz" should be marked as locked by user "receiver2" in the locks tab of the details panel on the webUI
12. Scenario: setting a lock on a folder shows the symbols at the sub-elements 
  Scenario: setting a lock on a folder shows the symbols at the sub-elements
    Given user "brand-new-user" has created folder "simple-folder/simple-empty-folder" in the server
    And user "brand-new-user" has uploaded file "data.zip" to "simple-folder/data.zip" in the server
    And user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    When the user opens folder "simple-folder" using the webUI
    Then folder "simple-empty-folder" should be marked as locked on the webUI
    And folder "simple-empty-folder" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    And file "data.zip" should be marked as locked on the webUI
    And file "data.zip" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
13. Scenario: setting a depth:0 lock on a folder does not show the symbols at the sub-elements 
  Scenario: setting a depth:0 lock on a folder does not show the symbols at the sub-elements
    Given user "brand-new-user" has created folder "simple-folder/simple-empty-folder" in the server
    And user "brand-new-user" has uploaded file "data.zip" to "simple-folder/data.zip" in the server
    And user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | depth | 0 |
    When the user browses to the files page
    Then folder "simple-folder" should be marked as locked on the webUI
    When the user opens folder "simple-folder" using the webUI
    Then folder "simple-empty-folder" should not be marked as locked on the webUI
    And file "data.zip" should not be marked as locked on the webUI
14. Scenario Outline: decline locked folder 
  Scenario Outline: decline locked folder
    Given these users have been created with default attributes and without skeleton files in the server:
      | username |
      | sharer   |
    And user "sharer" has created folder "/to-share-folder" in the server
    And user "sharer" has locked folder "to-share-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And user "sharer" has shared folder "to-share-folder" with user "brand-new-user" in the server
    And the user has browsed to the shared-with-me page
    When the user declines share "to-share-folder" offered by user "sharer" using the webUI
    And the user browses to the files page
    Then folder "to-share-folder" should not be listed on the webUI
    When the user re-logs in as "sharer" using the webUI
    Then folder "to-share-folder" should be listed on the webUI
    And folder "to-share-folder" should be marked as locked on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
15. Scenario Outline: accept previously declined locked folder 
  Scenario Outline: accept previously declined locked folder
    Given these users have been created with default attributes and without skeleton files in the server:
      | username |
      | sharer   |
    And user "sharer" has created folder "/to-share-folder" in the server
    And user "sharer" has locked folder "to-share-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And user "sharer" has shared folder "to-share-folder" with user "brand-new-user" in the server
    And the user has browsed to the shared-with-me page
    When the user declines share "to-share-folder" offered by user "sharer" using the webUI
    And the user accepts share "to-share-folder" offered by user "sharer" using the webUI
    And the user browses to the files page
    Then folder "to-share-folder" should be marked as locked on the webUI
    And folder "to-share-folder" should be marked as locked by user "sharer" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
16. Scenario Outline: accept previously declined locked folder but create a folder with same name in between 
  Scenario Outline: accept previously declined locked folder but create a folder with same name in between
    Given these users have been created with default attributes and without skeleton files in the server:
      | username |
      | sharer   |
    And user "sharer" has created folder "/to-share-folder" in the server
    And user "sharer" has locked folder "to-share-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And user "sharer" has shared folder "to-share-folder" with user "brand-new-user" in the server
    And the user has browsed to the shared-with-me page
    When the user declines share "to-share-folder" offered by user "sharer" using the webUI
    And the user browses to the files page
    And the user creates a folder with the name "to-share-folder" using the webUI
    And the user browses to the shared-with-me page
    And the user accepts share "to-share-folder" offered by user "sharer" using the webUI
    And the user browses to the files page
    Then folder "to-share-folder (2)" should be marked as locked on the webUI
    And folder "to-share-folder (2)" should be marked as locked by user "sharer" in the locks tab of the details panel on the webUI
    But folder "to-share-folder" should not be marked as locked on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
17. Scenario Outline: creating a subfolder structure that is the same as the structure of a declined & locked share 
  Scenario Outline: creating a subfolder structure that is the same as the structure of a declined & locked share
    Given these users have been created with default attributes and without skeleton files in the server:
      | username |
      | sharer   |
    And user "sharer" has created folder "/parent" in the server
    And user "sharer" has created folder "/parent/subfolder" in the server
    And user "sharer" has locked folder "parent" setting the following properties in the server
      | lockscope | <lockscope> |
    And user "sharer" has shared folder "parent" with user "brand-new-user" in the server
    And the user has browsed to the shared-with-me page
    When the user declines share "parent" offered by user "sharer" using the webUI
    And the user browses to the files page
    And the user creates a folder with the name "parent" using the webUI
    And the user opens folder "parent" using the webUI
    And the user creates a folder with the name "subfolder" using the webUI
    And the user browses to the files page
    Then folder "parent" should not be marked as locked on the webUI
    When the user opens folder "parent" using the webUI
    Then folder "subfolder" should not be marked as locked on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
18. Scenario Outline: unsharing a locked file/folder 
  Scenario Outline: unsharing a locked file/folder
    Given these users have been created with default attributes and without skeleton files in the server:
      | username |
      | sharer   |
    And user "sharer" has created file "lorem.txt" in the server
    And user "sharer" has created folder "simple-folder" in the server
    And user "sharer" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | <lockscope> |
    And user "sharer" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And user "sharer" has shared file "lorem.txt" with user "brand-new-user" in the server
    And user "sharer" has shared folder "simple-folder" with user "brand-new-user" in the server
    When the user browses to the files page
    And the user deletes file "lorem (2).txt" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Failed to delete "lorem (2).txt" - the file is locked
      """
    When the user deletes folder "simple-folder (2)" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Failed to delete "simple-folder (2)" - the file is locked
      """
    And file "lorem (2).txt" should be listed on the webUI
    And folder "simple-folder (2)" should be listed on the webUI
    And folder "lorem (2).txt" should be marked as locked on the webUI
    And folder "simple-folder (2)" should be marked as locked on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |

@grgprarup grgprarup mentioned this issue Sep 15, 2022
Merged
9 tasks
@grgprarup
Copy link
Contributor

grgprarup commented Sep 15, 2022 •
edited
Loading

Scenarios removed by PR: #7642
Related issue: #5417
These scenarios are related to unlock locked files/folders.

1. Scenario: unlocking file/folder deletes the lock symbols 
  Scenario: unlocking file/folder deletes the lock symbols
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked folder "lorem.txt" setting the following properties in the server
      | lockscope | shared |
    When user "brand-new-user" unlocks the lock of folder "simple-folder" using the webUI
    Then folder "simple-folder" should not be marked as locked on the webUI
    When user "brand-new-user" unlocks the lock of folder "lorem.txt" using the webUI
    Then folder "lorem.txt" should not be marked as locked on the webUI
2. Scenario: unlocking file/folder after the display name has been changed deletes the lock symbols 
  Scenario: unlocking file/folder after the display name has been changed deletes the lock symbols
    Given these users have been created with default attributes and without skeleton files in the server:
      | username               | displayname   |
      | user-with-display-name | My fancy name |
    And user "user-with-display-name" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | shared |
    And user "user-with-display-name" has locked file "data.zip" setting the following properties in the server
      | lockscope | exclusive |
    And the administrator has changed the display name of user "user-with-display-name" to "An ordinary name"
    When user "user-with-display-name" unlocks the lock of folder "simple-folder" using the webUI
    Then folder "simple-folder" should not be marked as locked on the webUI
    But folder "data.zip" should be marked as locked on the webUI
3. Scenario Outline: deleting the only remaining lock of a file/folder and reloading the page 
  Scenario Outline: deleting the only remaining lock of a file/folder and reloading the page
    Given user "brand-new-user" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | <lockscope> |
    And user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    When the user unlocks the lock no 1 of file "lorem.txt" on the webUI
    And the user unlocks the lock no 1 of folder "simple-folder" on the webUI
    Then file "lorem.txt" should not be marked as locked on the webUI
    And folder "simple-folder" should not be marked as locked on the webUI
    When the user reloads the current page of the webUI
    Then file "lorem.txt" should not be marked as locked on the webUI
    And folder "simple-folder" should not be marked as locked on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
4. Scenario Outline: deleting the only remaining lock of a folder by deleting it from a file (inside the folder) and reloading the page 
  Scenario Outline: deleting the only remaining lock of a folder by deleting it from a file (inside the folder) and reloading the page
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    And the user has opened folder "simple-folder" using the webUI
    When the user unlocks the lock no 1 of file "lorem.txt" on the webUI
    Then file "lorem.txt" should not be marked as locked on the webUI
    And folder "simple-empty-folder" should not be marked as locked on the webUI
    When the user reloads the current page of the webUI
    Then file "lorem.txt" should not be marked as locked on the webUI
    And folder "simple-empty-folder" should not be marked as locked on the webUI
    When the user browses to the files page
    Then folder "simple-folder" should not be marked as locked on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
5. Scenario: deleting the first lock of the multiple locks of shared file/folder 
  Scenario: deleting the first lock of the multiple locks of shared file/folder
    Given these users have been created with default attributes and without skeleton files in the server:
      | username  |
      | receiver1 |
      | receiver2 |
    And user "brand-new-user" has created folder "/FOLDER_TO_SHARE" in the server
    And user "brand-new-user" has shared file "/lorem.txt" with user "receiver1" in the server
    And user "brand-new-user" has shared folder "/FOLDER_TO_SHARE" with user "receiver1" in the server
    And user "brand-new-user" has shared file "/lorem.txt" with user "receiver2" in the server
    And user "brand-new-user" has shared folder "/FOLDER_TO_SHARE" with user "receiver2" in the server
    And user "brand-new-user" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And user "receiver1" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | shared |
    And user "receiver1" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And user "receiver2" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | shared |
    And user "receiver2" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And the user has browsed to the personal page
    When the user unlocks the lock no 1 of file "lorem.txt" on the webUI
    Then file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "receiver1" in the locks tab of the details panel on the webUI
    And file "lorem.txt" should be marked as locked by user "receiver2" in the locks tab of the details panel on the webUI
    When the user unlocks the lock no 1 of folder "FOLDER_TO_SHARE" on the webUI
    Then folder "FOLDER_TO_SHARE" should be marked as locked on the webUI
    And folder "FOLDER_TO_SHARE" should be marked as locked by user "receiver1" in the locks tab of the details panel on the webUI
    And folder "FOLDER_TO_SHARE" should be marked as locked by user "receiver2" in the locks tab of the details panel on the webUI
6. Scenario: deleting the second lock of the multiple locks of shared file/folder 
  Scenario: deleting the second lock of the multiple locks of shared file/folder
    Given these users have been created with default attributes and without skeleton files in the server:
      | username  |
      | receiver1 |
      | receiver2 |
    And user "brand-new-user" has created folder "/FOLDER_TO_SHARE" in the server
    And user "brand-new-user" has shared file "/lorem.txt" with user "receiver1" in the server
    And user "brand-new-user" has shared folder "/FOLDER_TO_SHARE" with user "receiver1" in the server
    And user "brand-new-user" has shared file "/lorem.txt" with user "receiver2" in the server
    And user "brand-new-user" has shared folder "/FOLDER_TO_SHARE" with user "receiver2" in the server
    And user "receiver1" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | shared |
    And user "receiver1" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And user "receiver2" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | shared |
    And user "receiver2" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And the user has browsed to the personal page
    When the user unlocks the lock no 2 of file "lorem.txt" on the webUI
    Then file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "receiver1" in the locks tab of the details panel on the webUI
    And file "lorem.txt" should be marked as locked by user "receiver2" in the locks tab of the details panel on the webUI
    When the user unlocks the lock no 2 of folder "FOLDER_TO_SHARE" on the webUI
    Then folder "FOLDER_TO_SHARE" should be marked as locked on the webUI
    And folder "FOLDER_TO_SHARE" should be marked as locked by user "receiver1" in the locks tab of the details panel on the webUI
    And folder "FOLDER_TO_SHARE" should be marked as locked by user "receiver2" in the locks tab of the details panel on the webUI
7. Scenario: deleting the last lock of the multiple locks of shared file/folder 
    Scenario: deleting the last lock of the multiple locks of shared file/folder
    Given these users have been created with default attributes and without skeleton files in the server:
      | username  |
      | receiver1 |
      | receiver2 |
    And user "brand-new-user" has created folder "/FOLDER_TO_SHARE" in the server
    And user "brand-new-user" has shared file "/lorem.txt" with user "receiver1" in the server
    And user "brand-new-user" has shared folder "/FOLDER_TO_SHARE" with user "receiver1" in the server
    And user "brand-new-user" has shared file "/lorem.txt" with user "receiver2" in the server
    And user "brand-new-user" has shared folder "/FOLDER_TO_SHARE" with user "receiver2" in the server
    And user "receiver1" has locked file "lorem (2).txt" setting the following properties in the server
      | lockscope | shared |
    And user "receiver1" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And user "receiver2" has locked file "lorem (2).txt" setting the following properties in the server
      | lockscope | shared |
    And user "receiver2" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | shared |
    And user "brand-new-user" has locked folder "FOLDER_TO_SHARE" setting the following properties in the server
      | lockscope | shared |
    And the user has browsed to the personal page
    When the user unlocks the lock no 3 of file "lorem.txt" on the webUI
    Then file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "receiver1" in the locks tab of the details panel on the webUI
    And file "lorem.txt" should be marked as locked by user "receiver2" in the locks tab of the details panel on the webUI
    When the user unlocks the lock no 3 of folder "FOLDER_TO_SHARE" on the webUI
    Then folder "FOLDER_TO_SHARE" should be marked as locked on the webUI
    And folder "FOLDER_TO_SHARE" should be marked as locked by user "receiver1" in the locks tab of the details panel on the webUI
    And folder "FOLDER_TO_SHARE" should be marked as locked by user "receiver2" in the locks tab of the details panel on the webUI
8. Scenario Outline: deleting a lock that was created by an other user 
    Scenario Outline: deleting a lock that was created by an other user
    Given these users have been created with default attributes and without skeleton files in the server:
      | username  |
      | receiver1 |
    And user "brand-new-user" has shared file "/lorem.txt" with user "receiver1" in the server
    And user "receiver1" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    When the user unlocks the lock no 1 of file "lorem.txt" on the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Could not unlock, please contact the lock owner receiver1
      """
    And file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "receiver1" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |

@grgprarup
Copy link
Contributor

grgprarup commented Sep 15, 2022 •
edited
Loading

Scenarios removed by PR: #7642
Related issue: #5417
These scenarios are related to deleting locked files/folders.

1. Scenario Outline: deleting a locked file 
  Scenario Outline: deleting a locked file
    Given user "brand-new-user" has locked folder "lorem.txt" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    When the user tries to delete folder "lorem.txt" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Failed to delete "lorem.txt" - the file is locked
      """
    When the user reloads the current page of the webUI
    Then file "lorem.txt" should be listed on the webUI
    And file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
2. Scenario Outline: deleting a file in a locked folder 
    Scenario Outline: deleting a file in a locked folder
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    And the user has opened folder "simple-folder"
    When the user tries to delete folder "lorem.txt" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Failed to delete "lorem.txt" - the file is locked
      """
    When the user reloads the current page of the webUI
    Then file "lorem.txt" should be listed on the webUI
    When the user browses to the files page
    Then folder "simple-folder" should be marked as locked on the webUI
    And folder "simple-folder" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |

@grgprarup
Copy link
Contributor

grgprarup commented Sep 15, 2022 •
edited
Loading

Scenarios removed by PR: #7642
Related issue: #5417
These scenarios are related to moving locked files/folders.

1. Scenario Outline: moving a locked file 
    Scenario Outline: moving a locked file
    Given user "brand-new-user" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    When the user tries to move file "lorem.txt" into folder "simple-empty-folder" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Failed to move "lorem.txt"
      """
    When the user browses to the files page
    Then file "lorem.txt" should be listed on the webUI
    And file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    When the user opens folder "simple-empty-folder" using the webUI
    Then file "lorem.txt" should not be listed on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
2. Scenario Outline: moving a file trying to overwrite a locked file 
    Scenario Outline: moving a file trying to overwrite a locked file
    Given user "brand-new-user" has locked file "/simple-folder/lorem.txt" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    When the user tries to move file "lorem.txt" into folder "simple-folder" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Failed to move "lorem.txt"
      """
    When the user browses to the files page
    Then file "lorem.txt" should be listed on the webUI
    And file "lorem.txt" should not be marked as locked on the webUI
    When the user opens folder "simple-folder" using the webUI
    Then file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
3. Scenario Outline: moving a file into a locked folder 
    Scenario Outline: moving a file into a locked folder
    Given user "brand-new-user" has locked file "/simple-empty-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    When the user tries to move file "lorem.txt" into folder "simple-empty-folder" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Failed to move "lorem.txt"
      """
    When the user browses to the files page
    Then file "lorem.txt" should be listed on the webUI
    And file "lorem.txt" should not be marked as locked on the webUI
    And file "simple-empty-folder" should be marked as locked on the webUI
    And file "simple-empty-folder" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    When the user opens folder "simple-empty-folder" using the webUI
    Then file "lorem.txt" should not be listed on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
4. Scenario Outline: renaming of a locked file 
    Scenario Outline: renaming of a locked file
    Given user "brand-new-user" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    When the user tries to rename file "lorem.txt" to "a-renamed-file.txt" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      Failed to move "lorem.txt" to "a-renamed-file.txt" - the file is locked
      """
    When the user closes rename dialog
    And the user reloads the current page of the webUI
    Then file "lorem.txt" should be listed on the webUI
    And file "a-renamed-file.txt" should not be listed on the webUI
    And file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |

@grgprarup
Copy link
Contributor

grgprarup commented Sep 15, 2022 •
edited
Loading

Scenarios removed by PR: #7642
Related issue: #5417
These scenarios are related to uploading locked files/folders.

1. Scenario Outline: uploading a file, trying to overwrite a locked file 
      Scenario Outline: uploading a file, trying to overwrite a locked file
    Given user "brand-new-user" has locked file "lorem.txt" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    When the user uploads overwriting file "lorem.txt" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      The file lorem.txt is currently locked, please try again later
      """
    And the content of file "lorem.txt" for user "brand-new-user" should be "locked file"
    And file "lorem.txt" should be marked as locked on the webUI
    And file "lorem.txt" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
2. Scenario Outline: uploading a file, trying to overwrite a file in a locked folder 
   Scenario Outline: uploading a file, trying to overwrite a file in a locked folder
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    And the user has opened folder "simple-folder"
    When the user uploads overwriting file "lorem.txt" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      The file lorem.txt is currently locked, please try again later
      """
    And the content of file "simple-folder/lorem.txt" for user "brand-new-user" should be "file inside locked folder" in the server
    When the user browses to the files page
    Then file "simple-folder" should be marked as locked on the webUI
    And file "simple-folder" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |
3. Scenario Outline: uploading a new file into a locked folder 
  Scenario Outline: uploading a new file into a locked folder
    Given user "brand-new-user" has locked folder "simple-folder" setting the following properties in the server
      | lockscope | <lockscope> |
    And the user has browsed to the personal page
    And the user has opened folder "simple-folder"
    When the user uploads file "new-lorem.txt" using the webUI
    Then notifications should be displayed on the webUI with the text
      """
      The file lorem.txt is currently locked, please try again later
      """
    And file "new-lorem.txt" should not be listed on the webUI
    When the user browses to the files page
    Then file "simple-folder" should be marked as locked on the webUI
    And file "simple-folder" should be marked as locked by user "brand-new-user" in the locks tab of the details panel on the webUI
    Examples:
      | lockscope |
      | exclusive |
      | shared    |

@grgprarup
Copy link
Contributor

Scenarios removed by PR: #7642
Related issue: #2422, owncloud/ocis#1328
These scenarios are related to Share public link shares via email

1. Scenario: user shares a public link via email 
     Scenario: user shares a public link via email
    When the user creates a new public link for folder "simple-folder" using the webUI with
      | email | foo@bar.co |
    Then the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email containing the last shared public link
2. Scenario: user shares a public link via email and sends a copy to self 
       Scenario: user shares a public link via email and sends a copy to self
    When the user creates a new public link for folder "simple-folder" using the webUI with
      | email       | foo@bar.co |
      | emailToSelf | true       |
    Then the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email containing the last shared public link
    And the email address "[email protected]" should have received an email containing the last shared public link
3. Scenario: user shares a public link via email with multiple addresses 
     Scenario: user shares a public link via email with multiple addresses
    When the user creates a new public link for folder "simple-folder" using the webUI with
      | email | foo@bar.co, foo@barr.co |
    Then the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email containing the last shared public link
    And the email address "[email protected]" should have received an email containing the last shared public link
4. Scenario: user shares a public link via email with a personal message 
  Scenario: user shares a public link via email with a personal message
    When the user creates a new public link for folder "simple-folder" using the webUI with
      | email           | foo@bar.co  |
      | personalMessage | lorem ipsum |
    Then the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email with the body containing
      """
      lorem ipsum
      """
    And the email address "[email protected]" should have received an email containing the last shared public link
5. Scenario: user shares a public link via email adding few addresses before and then removing some addresses afterwards 
  Scenario: user shares a public link via email adding few addresses before and then removing some addresses afterwards
    When the user opens the link share dialog for folder "simple-folder" using the webUI
    And the user opens the create public link share popup
    And the user adds the following email addresses using the webUI:
      | email           |
      | foo1234@bar.co  |
      | foo5678@bar.co  |
      | foo1234@barr.co |
      | foo5678@barr.co |
    And the user removes the following email addresses using the webUI:
      | email           |
      | foo1234@bar.co  |
      | foo5678@barr.co |
    And the user creates the public link using the webUI
    Then the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email containing the last shared public link
    And the email address "[email protected]" should have received an email containing the last shared public link
    But the email address "[email protected]" should not have received an email
    And the email address "[email protected]" should not have received an email
6. Scenario: user shares a public link via email with a personal message (duplicate) 
   Scenario: user shares a public link via email with a personal message (duplicate)
    When the user creates a new public link for folder "simple-folder" using the webUI with
      | email           | foo@bar.co  |
      | personalMessage | lorem ipsum |
    Then the email address "[email protected]" should have received an email with the body containing
      """
      Alice Hansen shared simple-folder with you
      """
    And the email address "[email protected]" should have received an email with the body containing
      """
      lorem ipsum
      """
    And the email address "[email protected]" should have received an email containing the last shared public link

@grgprarup
Copy link
Contributor

grgprarup commented Sep 16, 2022 •
edited
Loading

Scenarios removed by PR: #7642
Related issue: #5106, #6996
These scenarios are related to File Upload

1. Scenario: keep new and existing file 
    Scenario: keep new and existing file
    When the user uploads file "lorem.txt" using the webUI
    And the user chooses to keep the new files in the upload dialog
    And the user chooses to keep the existing files in the upload dialog
    And the user chooses "Continue" in the upload dialog
    Then no dialog should be displayed on the webUI
    And no message should be displayed on the webUI
    And file "lorem.txt" should be listed on the webUI
    And the content of "lorem.txt" should not have changed in the server
    And file "lorem (2).txt" should be listed on the webUI
    And as "Alice" the content of "lorem (2).txt" in the server should be the same as the content of local file "lorem.txt"
2. Scenario: cancel conflict dialog 
   Scenario: cancel conflict dialog
    When the user uploads file "lorem.txt" using the webUI
    And the user chooses "Cancel" in the upload dialog
    Then no dialog should be displayed on the webUI
    And no message should be displayed on the webUI
    And file "lorem.txt" should be listed on the webUI
    And the content of "lorem.txt" should not have changed in the server
    And file "lorem (2).txt" should not be listed on the webUI
3. Scenario: keep new and existing file in a sub-folder 
  Scenario: keep new and existing file in a sub-folder
    When the user opens folder "simple-folder" using the webUI
    And the user uploads file "lorem.txt" using the webUI
    And the user chooses to keep the new files in the upload dialog
    And the user chooses to keep the existing files in the upload dialog
    And the user chooses "Continue" in the upload dialog
    Then no dialog should be displayed on the webUI
    And no message should be displayed on the webUI
    And file "lorem.txt" should be listed on the webUI
    And the content of "lorem.txt" should not have changed in the server
    And file "lorem (2).txt" should be listed on the webUI
    And as "Alice" the content of "lorem (2).txt" in the server should be the same as the content of local file "lorem.txt"

@grgprarup
Copy link
Contributor

grgprarup commented Sep 16, 2022 •
edited
Loading

Scenarios removed by PR: #7642
Related issue: #5106, #6996
These scenarios are related to File Upload edge cases

1. Scenario: keep new and existing file 
   Scenario: keep new and existing file
    When the user uploads file "'single'quotes.txt" keeping both new and existing files using the webUI
    Then file "'single'quotes.txt" should be listed on the webUI
    And the content of "'single'quotes.txt" should not have changed in the server
    And file "'single'quotes (2).txt" should be listed on the webUI
    And as "Alice" the content of "'single'quotes (2).txt" in the server should be the same as the content of local file "'single'quotes.txt"

    When the user uploads file "strängé filename (duplicate #2 &).txt" keeping both new and existing files using the webUI
    Then file "strängé filename (duplicate #2 &).txt" should be listed on the webUI
    And the content of "strängé filename (duplicate #2 &).txt" should not have changed in the server
    And file "strängé filename (duplicate #2 &) (2).txt" should be listed on the webUI
    And as "Alice" the content of "strängé filename (duplicate #2 &) (2).txt" in the server should be the same as the content of local file "strängé filename (duplicate #2 &).txt"

    When the user uploads file "zzzz-must-be-last-file-in-folder.txt" keeping both new and existing files using the webUI
    Then file "zzzz-must-be-last-file-in-folder.txt" should be listed on the webUI
    And the content of "zzzz-must-be-last-file-in-folder.txt" should not have changed in the server
    And file "zzzz-must-be-last-file-in-folder (2).txt" should be listed on the webUI
    And as "Alice" the content of "zzzz-must-be-last-file-in-folder (2).txt" in the server should be the same as the content of local file "zzzz-must-be-last-file-in-folder.txt"

@grgprarup
Copy link
Contributor

Scenarios removed by PR: #7642
Related issue: #1725
These scenarios are related to files and folders can be deleted from the trashbin

1. Scenario: Delete files and check that they are gone 
  Scenario: Delete files and check that they are gone
    When the user deletes file "lorem.txt" using the webUI
    And the user deletes file "sample,1.txt" using the webUI
    And the user opens folder "simple-folder" using the webUI
    Then file "lorem.txt" should not be listed on the webUI
    And file "sample,1.txt" should not be listed on the webUI
    But file "lorem.txt" should be listed in the trashbin folder "simple-folder" on the webUI
    And file "lorem-big.txt" should not be listed in the trashbin folder "simple-folder" on the webUI
    But file "lorem-big.txt" should be listed on the webUI

@grgprarup
Copy link
Contributor

Scenarios removed by PR: #7642
Related issue: #5464, #1158
These scenarios are related to browse directly to details tab

1. Scenario Outline: Browse directly to the sharing details of a file 
  Scenario Outline: Browse directly to the sharing details of a file
    When the user browses directly to display the "sharing" details of file "lorem.txt" in folder "<folder>"
    Then the thumbnail should be visible in the details panel
    And the "sharing" details panel should be visible
    And the share-with field should be visible in the details panel
    Examples:
      | folder        |
      | /             |
      | simple-folder |
2. Scenario Outline: Browse directly to the comments details of a file 
  Scenario Outline: Browse directly to the comments details of a file
    When the user browses directly to display the "comments" details of file "lorem.txt" in folder "<folder>"
    Then the thumbnail should be visible in the details panel
    And the "comments" details panel should be visible
    Examples:
      | folder        |
      | /             |
      | simple-folder |
3. Scenario Outline: Browse directly to the versions details of a file 
  Scenario Outline: Browse directly to the versions details of a file
    When the user browses directly to display the "versions" details of file "lorem.txt" in folder "<folder>"
    Then the thumbnail should be visible in the details panel
    And the "versions" details panel should be visible
    Examples:
      | folder        |
      | /             |
      | simple-folder |

@grgprarup
Copy link
Contributor

Scenarios removed by PR: #7642
Related issue: #1158, #5017
These scenarios are related to User can open the details panel for any file or folder

1. Scenario: View different areas of details panel for the folder with given tag in Tags page 
 Scenario: View different areas of details panel for the folder with given tag in Tags page
    Given user "Alice" has created folder "simple-folder" in the server
    And the user has browsed to the personal page
    Given user "Alice" has created a "normal" tag with name "simple"
    And user "Alice" has added tag "simple" to folder "simple-folder"
    When the user browses to the tags page
    And the user searches for tag "simple" using the webUI
    Then folder "simple-folder" should be listed on the webUI
    When the user opens the actions sidebar panel of folder "simple-folder" on the webUI
    And the "small" preview of thumbnail should be visible in the "actions" panel
    When the user switches to "people" panel in details panel using the webUI
    Then the "people" details panel should be visible
    When the user switches to "links" panel in details panel using the webUI
    Then the "links" details panel should be visible
    When the user switches to "versions" panel in details panel using the webUI
    Then the "versions" details panel should be visible
    When the user switches to "comments" panel in details panel using the webUI
    Then the "comments" details panel should be visible

@grgprarup
Copy link
Contributor

Scenarios removed by PR: #7642
Related issue: #5017
These scenarios are related to search

1. Scenario: search for a file using a tag 
  Scenario: search for a file using a tag
    Given user "Alice" has created a "normal" tag with name "ipsum"
    And user "Alice" has added tag "ipsum" to file "/lorem.txt"
    When the user browses to the tags page
    And the user searches for tag "ipsum" using the webUI
    Then file "lorem.txt" should be listed on the webUI
2. Scenario: search for a file with multiple tags 
  Scenario: search for a file with multiple tags
    Given user "Alice" has created a "normal" tag with name "lorem"
    And user "Alice" has created a "normal" tag with name "ipsum"
    And user "Alice" has added tag "lorem" to file "/lorem.txt"
    And user "Alice" has added tag "lorem" to file "/testimage.jpg"
    And user "Alice" has added tag "ipsum" to file "/lorem.txt"
    When the user browses to the tags page
    And the user searches for tag "lorem" using the webUI
    And the user searches for tag "ipsum" using the webUI
    Then file "lorem.txt" should be listed on the webUI
    And file "testimage.jpg" should not be listed on the webUI
3. Scenario: search for a file with tags 
  Scenario: search for a file with tags
    Given user "Alice" has created a "normal" tag with name "lorem"
    And user "Alice" has added tag "lorem" to file "/lorem.txt"
    And user "Alice" has added tag "lorem" to file "/simple-folder/lorem.txt"
    When the user browses to the tags page
    And the user searches for tag "lorem" using the webUI
    Then file "lorem.txt" should be listed on the webUI
    And file "lorem.txt" with path "" should be listed in the tags page on the webUI
    And file "lorem.txt" with path "/simple-folder" should be listed in the tags page on the webUI

@grgprarup
Copy link
Contributor

Scenarios removed by PR: #7642
Related issue: #5017
These scenarios are related to delete files from tags page

1. Scenario: delete files from tags page 
 Scenario: delete files from tags page
    Given user "Alice" has created file "lorem.txt" in the server
    And user "Alice" has created a "normal" tag with name "lorem" in the server
    And user "Alice" has added tag "lorem" to file "/lorem.txt" in the server
    And user "Alice" has logged in using the webUI
    When the user browses to the tags page
    And the user searches for tag "lorem" using the webUI
    Then file "lorem.txt" should be listed on the webUI
    When the user deletes file "lorem.txt" using the webUI
    Then as "Alice" file "lorem.txt" should not exist in the server
    And file "lorem.txt" should not be listed on the webUI
    When the user browses to the files page
    Then file "lorem.txt" should not be listed on the webUI

@amrita-shrestha
Copy link
Contributor

Scenarios skipped by PR:
These scenarios try to set shareapi_only_share_with_membership_groups settings

1. Scenario: Restrict users to only share with users in their groups 
  Scenario: Restrict users to only share with users in their groups
    Given the setting "shareapi_only_share_with_group_members" of app "core" has been set to "yes" in the server
    When the user opens the share dialog for folder "simple-folder" using the webUI
    And the user types "Ali" in the share-with-field
    Then "user" "Alice Hansen" should be listed in the autocomplete list on the webUI
    But "user" "Alison Cooper" should not be listed in the autocomplete list on the webUI
1. Scenario: Restrict users to only share with groups they are member of 
  Scenario: Restrict users to only share with groups they are member of
    Given the setting "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" in the server
    When the user opens the share dialog for folder "simple-folder" using the webUI

    And the user types "grp" in the share-with-field
    Then "group" "grp1" should be listed in the autocomplete list on the webUI
    But "group" "grp2" should not be listed in the autocomplete list on the webUI

@amrita-shrestha
Copy link
Contributor

Scenarios skipped by PR:
These scenarios try to set shareapi_allow_group_sharing settings

1. Scenario: Forbid sharing with groups 
  Scenario: Forbid sharing with groups
    Given the setting "shareapi_allow_group_sharing" of app "core" has been set to "no" in the server
    When the user opens the share dialog for folder "simple-folder" using the webUI

    And the user types "grp" in the share-with-field
    Then "group" "grp1" should not be listed in the autocomplete list on the webUI
    And "group" "grp2" should not be listed in the autocomplete list on the webUI

@SagarGi
Copy link
Member

SagarGi commented Oct 11, 2022

Scenarios skipped by PR: #7766
Related Issue: #6894

1. Scenario: sharing indicator of items inside a re-shared subfolder 
  Scenario: sharing indicator of items inside a re-shared subfolder
    Given 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 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 accepted the share "Shares/simple-folder" offered by user "Alice" in the server
    And user "Brian" has shared folder "Shares/simple-folder/simple-empty-folder" with user "Carol" in the server
    And user "Brian" has logged in using the webUI
    When the user opens folder "Shares" using the webUI
    And the user opens the sharing sidebar for folder "simple-folder"
    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
    And the user opens the sharing sidebar for file "lorem.txt"
    Then the following resources should have share indicators on the webUI
      | fileName            | expectedIndicators |
      | simple-empty-folder | user-direct        |
      | lorem.txt           | user-indirect      |
2. Scenario: sharing indicator of items inside an incoming shared folder 
  Scenario: sharing indicator of items inside an incoming shared folder
    Given 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 accepted the share "Shares/simple-folder" offered by user "Alice" in the server
    When user "Brian" has logged in using the webUI
    And the user opens folder "Shares" using the webUI
    And the user opens the sharing sidebar for folder "simple-folder"
    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      |
3. Scenario: sharing indicator of items inside a re-shared folder 
  Scenario: sharing indicator of items inside a re-shared folder
    Given 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 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 accepted the share "Shares/simple-folder" offered by user "Alice" in the server
    And user "Brian" 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 folder "Shares" using the webUI
    And the user opens the sharing sidebar for folder "simple-folder"
    Then the following resources should have share indicators on the webUI
      | fileName      | expectedIndicators |
      | simple-folder | user-direct        |
    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      |
4. Scenario: sharing indicators public link from child of reshare 
  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             |
5. Scenario: sharing indicators public link from reshare 
  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 |
6. Scenario: no sharing indicator visible in file list from public link 
  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 |
7. Scenario: sharing indicator of items inside a re-shared subfolder 
  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 accepted the share "Shares/simple-folder" offered by user "Alice" 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        |
8. Scenario: sharing indicator of items inside an incoming shared folder 
  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
    And user "Brian" has accepted the share "Shares/simple-folder" offered by user "Alice" 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      |
9. Scenario: sharing indicator of items inside a re-shared folder 
  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 accepted the share "Shares/simple-folder" offered by user "Alice" 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 was referenced Oct 27, 2022
Closed
Closed
@SwikritiT SwikritiT mentioned this issue Nov 1, 2022
Closed
@amrita-shrestha
Copy link
Contributor

This scenario has been skipped due to Share spaces implementation.

1. Scenario: sharing indicator of items inside a re-shared subfolder 
  Scenario: sharee moves a file shared by sharer into another folder
    Given the setting "shareapi_auto_accept_share" of app "core" has been set to "no" in the server
    And 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 "Alice" has uploaded file with content "test content" to "simple-folder/testFile.txt" in the server
    And user "Alice" has shared folder "/simple-folder" with user "Brian" in the server
    And user "Brian" has accepted the share "Shares/simple-folder" offered by user "Alice" in the server
    And user "Brian" has logged in using the webUI
    And user "Brian" has created folder "/Shares/testFolder" in the server
    And the user has opened folder "Shares"
    And the user has opened folder "simple-folder"
    When the user batch moves these files into folder "/Shares/testFolder" using the webUI
      | file_name    |
      | testFile.txt |
    Then breadcrumb for folder "Shares" should be displayed on the webUI
    And as "Brian" file "/Shares/testFolder/testFile.txt" should exist in the server

@amrita-shrestha amrita-shrestha mentioned this issue Nov 1, 2022
Merged
10 tasks
@SwikritiT
Copy link
Contributor Author

Tests skipped in #8078 as tests try to copy into Shares/ which is not possible due to share jail

1. Scenario: copy a file into another folder with no change permission 
  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 accepted the share "Shares/simple-folder" offered by user "Brian" 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
2. Scenario: copy a folder into another folder with no change permission 
  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 accepted the share "Shares/simple-folder" offered by user "Brian" 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

@SwikritiT
Copy link
Contributor Author

Tests skipped in #8076 the tests try to click on copy private link URL button which is not available for ocis

1. Scenario Outline: Copy permalink to clipboard 
 Scenario Outline: Copy permalink to clipboard
    When the user copies the private link of the resource <resource_name> using the webUI
    Then as user "Alice" the clipboard content should match permalink of resource <resource_name>
    Examples:
      | resource_name   |
      | "lorem.txt"     |
      | "simple-folder" |
2. tests/acceptance/features/webUIPrivateLinks/accessingPrivateLinks.feature 
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

  @smokeTest @ocisSmokeTest
  Scenario: Copy and access private link
    Given user "Alice" has logged in using the webUI
    When the user copies the private link of the file "lorem.txt" using the webUI
    And the user navigates to the copied private link using the webUI
    Then file "lorem.txt" should be listed on the webUI

  @smokeTest @ocisSmokeTest
  Scenario: Access private link before authorisation
    When an anonymous user tries to navigate to the private link created by user "Alice" for file "lorem.txt"
    Then the user should be redirected to the IdP login page
    When user "Alice" fills in the login form using the webUI
    Then file "lorem.txt" should be listed on the webUI

  Scenario: Access private link as a collaborator
    Given user "Brian" has been created with default attributes and without skeleton files in the server
    And user "Alice" has shared file "lorem.txt" with user "Brian" with "read" permissions 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"
    And the private link resolved successfully
    Then file "lorem.txt" should be listed on the webUI

  @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
      """

@SwikritiT
Copy link
Contributor Author

Tests skipped in #8110 because they try to open the shares folder

1. Scenario: share a file with an internal group a member overwrites and unshares the file 
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 user "Alice" accepts the share "Shares/new-lorem.txt" offered by user "Carol" using the sharing API in the server
    And user "Brian" accepts the share "Shares/new-lorem.txt" offered by user "Carol" using the sharing API in the server
    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"
2.Scenario: share a file with another internal user who overwrites and unshares the file 
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
    And user "Alice" has accepted the share "Shares/new-lorem.txt" offered by user "Brian" 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"

@amrita-shrestha amrita-shrestha mentioned this issue Apr 9, 2024
Closed
18 tasks
@saw-jan
Copy link
Member

saw-jan commented Apr 10, 2024

#10259 (comment)

@saw-jan @Salipa-Gurung @PrajwolAmatya can we close this issue #7264 or we going to let it open?

Closing in favor of #10259

@saw-jan saw-jan closed this as completed Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
QA:team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@grgprarup @SwikritiT @SagarGi @saw-jan @amrita-shrestha