@issue-1324
Feature: files and folders exist in the trashbin after being deleted
  As a user
  I want deleted files and folders to be available in the trashbin
  So that I can recover data easily

  Background:
    Given user "Alice" has been created with default attributes
    And user "Alice" has uploaded file with content "to delete" to "/textfile0.txt"

  @smokeTest
  Scenario Outline: deleting a file moves it to trashbin
    Given using <dav-path-version> DAV path
    When user "Alice" deletes file "/textfile0.txt" using the WebDAV API
    Then the HTTP status code should be "204"
    And as "Alice" file "/textfile0.txt" should exist in the trashbin
    But as "Alice" file "/textfile0.txt" should not exist
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @smokeTest
  Scenario Outline: deleting a folder moves it to trashbin
    Given using <dav-path-version> DAV path
    And user "Alice" has created folder "/tmp"
    When user "Alice" deletes folder "/tmp" using the WebDAV API
    Then the HTTP status code should be "204"
    And as "Alice" folder "/tmp" should exist in the trashbin
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |


  Scenario Outline: deleting a file in a folder moves it to the trashbin root
    Given using <dav-path-version> DAV path
    And user "Alice" has created folder "/new-folder"
    And user "Alice" has moved file "/textfile0.txt" to "/new-folder/new-file.txt"
    When user "Alice" deletes file "/new-folder/new-file.txt" using the WebDAV API
    Then the HTTP status code should be "204"
    And as "Alice" the file with original path "/new-folder/new-file.txt" should exist in the trashbin
    And as "Alice" file "/new-file.txt" should exist in the trashbin
    But as "Alice" file "/new-folder/new-file.txt" should not exist
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @skipOnReva
  Scenario Outline: deleting a file in a shared folder moves it to the trashbin root
    Given using <dav-path-version> DAV path
    And user "Brian" has been created with default attributes
    And user "Alice" has created folder "/shared"
    And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
    And user "Alice" has sent the following resource share invitation:
      | resource        | shared   |
      | space           | Personal |
      | sharee          | Brian    |
      | shareType       | user     |
      | permissionsRole | Editor   |
    And user "Brian" has a share "shared" synced
    When user "Alice" deletes file "/shared/shared_file.txt" using the WebDAV API
    Then the HTTP status code should be "204"
    And as "Alice" the file with original path "/shared/shared_file.txt" should exist in the trashbin
    And as "Alice" file "/shared_file.txt" should exist in the trashbin
    But as "Alice" file "/shared/shared_file.txt" should not exist
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @skipOnReva
  Scenario Outline: deleting a shared folder moves it to trashbin
    Given using <dav-path-version> DAV path
    And user "Brian" has been created with default attributes
    And user "Alice" has created folder "/shared"
    And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
    And user "Alice" has sent the following resource share invitation:
      | resource        | shared   |
      | space           | Personal |
      | sharee          | Brian    |
      | shareType       | user     |
      | permissionsRole | Editor   |
    And user "Brian" has a share "shared" synced
    When user "Alice" deletes folder "/shared" using the WebDAV API
    Then the HTTP status code should be "204"
    And as "Alice" the folder with original path "/shared" should exist in the trashbin
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  # This scenario deletes many files as close together in time as the test can run.
  # On a very slow system, the file deletes might all happen in different seconds.
  # But on "reasonable" systems, some of the files will be deleted in the same second,
  # thus testing the required behavior.
  Scenario Outline: trashbin can store two files with the same name but different origins when the files are deleted close together in time
    Given using <dav-path-version> DAV path
    And user "Alice" has created folder "/folderA"
    And user "Alice" has created folder "/folderB"
    And user "Alice" has created folder "/folderC"
    And user "Alice" has created folder "/folderD"
    And user "Alice" has copied file "/textfile0.txt" to "/folderA/textfile0.txt"
    And user "Alice" has copied file "/textfile0.txt" to "/folderB/textfile0.txt"
    And user "Alice" has copied file "/textfile0.txt" to "/folderC/textfile0.txt"
    And user "Alice" has copied file "/textfile0.txt" to "/folderD/textfile0.txt"
    When user "Alice" deletes these files without delays using the WebDAV API
      | /textfile0.txt         |
      | /folderA/textfile0.txt |
      | /folderB/textfile0.txt |
      | /folderC/textfile0.txt |
      | /folderD/textfile0.txt |
    Then the HTTP status code of responses on all endpoints should be "204"
    And as "Alice" the folder with original path "/folderA/textfile0.txt" should exist in the trashbin
    And as "Alice" the folder with original path "/folderB/textfile0.txt" should exist in the trashbin
    And as "Alice" the folder with original path "/folderC/textfile0.txt" should exist in the trashbin
    And as "Alice" the folder with original path "/folderD/textfile0.txt" should exist in the trashbin
    And as "Alice" the folder with original path "/textfile0.txt" should exist in the trashbin
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  # Note: the underlying acceptance test code ensures that each delete step is separated by a least 1 second
  Scenario Outline: trashbin can store two files with the same name but different origins when the deletes are separated by at least 1 second
    Given using <dav-path-version> DAV path
    And user "Alice" has created folder "/folderA"
    And user "Alice" has created folder "/folderB"
    And user "Alice" has copied file "/textfile0.txt" to "/folderA/textfile0.txt"
    And user "Alice" has copied file "/textfile0.txt" to "/folderB/textfile0.txt"
    When user "Alice" deletes file "/folderA/textfile0.txt" using the WebDAV API
    And user "Alice" deletes file "/folderB/textfile0.txt" using the WebDAV API
    And user "Alice" deletes file "/textfile0.txt" using the WebDAV API
    Then the HTTP status code of responses on all endpoints should be "204"
    And as "Alice" the folder with original path "/folderA/textfile0.txt" should exist in the trashbin
    And as "Alice" the folder with original path "/folderB/textfile0.txt" should exist in the trashbin
    And as "Alice" the folder with original path "/textfile0.txt" should exist in the trashbin
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @issue-3561
  Scenario Outline: listing other user's trashbin is prohibited
    Given using <dav-path-version> DAV path
    And user "testtrashbin100" has been created with default attributes
    And user "testtrashbin100" has uploaded file "filesForUpload/textfile.txt" to "/textfile1.txt"
    And user "Brian" has been created with default attributes
    And user "testtrashbin100" has deleted file "/textfile1.txt"
    When user "Brian" tries to list the trashbin content for user "testtrashbin100"
    Then the HTTP status code should be "404"
    And the last webdav response should not contain the following elements
      | path          | user            |
      | textfile1.txt | testtrashbin100 |
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @issue-3561 @smokeTest
  Scenario Outline: listing other user's trashbin is prohibited with multiple files on trashbin
    Given using <dav-path-version> DAV path
    And user "testtrashbin101" has been created with default attributes
    And user "testtrashbin101" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
    And user "testtrashbin101" has uploaded file "filesForUpload/textfile.txt" to "/textfile2.txt"
    And user "Brian" has been created with default attributes
    And user "testtrashbin101" has deleted file "/textfile0.txt"
    And user "testtrashbin101" has deleted file "/textfile2.txt"
    When user "Brian" tries to list the trashbin content for user "testtrashbin101"
    Then the HTTP status code should be "404"
    And the last webdav response should not contain the following elements
      | path          | user            |
      | textfile0.txt | testtrashbin101 |
      | textfile2.txt | testtrashbin101 |
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @issue-3561 @skipOnReva
  Scenario Outline: listing other user's trashbin is prohibited for newly recreated user with same name
    Given using <dav-path-version> DAV path
    And user "testtrashbin102" has been created with default attributes
    And user "testtrashbin102" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
    And user "testtrashbin102" has uploaded file "filesForUpload/textfile.txt" to "/textfile2.txt"
    And user "Brian" has been created with default attributes
    And user "testtrashbin102" has deleted file "/textfile0.txt"
    And user "testtrashbin102" has deleted file "/textfile2.txt"
    And user "testtrashbin102" has been deleted
    And user "testtrashbin102" has been created with default attributes
    And user "testtrashbin102" has uploaded file "filesForUpload/textfile.txt" to "/textfile3.txt"
    And user "testtrashbin102" has deleted file "/textfile3.txt"
    When user "Brian" tries to list the trashbin content for user "testtrashbin102"
    Then the HTTP status code should be "404"
    And the last webdav response should not contain the following elements
      | path          | user            |
      | textfile0.txt | testtrashbin102 |
      | textfile2.txt | testtrashbin102 |
      | textfile3.txt | testtrashbin102 |
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @issue-3561
  Scenario Outline: listing other user's empty unused trashbin is prohibited
    Given using <dav-path-version> DAV path
    And user "testtrashbinempty" has been created with default attributes
    And user "testtrashbinempty" has uploaded file "filesForUpload/textfile.txt" to "/textfile1.txt"
    When user "Alice" tries to list the trashbin content for user "testtrashbinempty"
    Then the HTTP status code should be "404"
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @issue-3561
  Scenario Outline: listing non-existent user's trashbin is prohibited
    Given using <dav-path-version> DAV path
    When user "Alice" tries to list the trashbin content for user "nonexistent"
    Then the HTTP status code should be "404"
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @smokeTest
  Scenario Outline: get trashbin content with wrong password
    Given using <dav-path-version> DAV path
    And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
    And user "Alice" has deleted file "/textfile0.txt"
    When user "Alice" tries to list the trashbin content for user "Alice" using password "invalid"
    Then the HTTP status code should be "401"
    And the last webdav response should not contain the following elements
      | path           | user  |
      | /textfile0.txt | Alice |
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @smokeTest
  Scenario Outline: get trashbin content without password
    Given using <dav-path-version> DAV path
    And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
    And user "Alice" has deleted file "/textfile0.txt"
    When user "Alice" tries to list the trashbin content for user "Alice" using password ""
    Then the HTTP status code should be "401"
    And the last webdav response should not contain the following elements
      | path           | user  |
      | /textfile0.txt | Alice |
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |


  Scenario Outline: user with unusual username deletes a file
    Given using <dav-path-version> DAV path
    And user "<user>" has been created with default attributes
    And user "<user>" has uploaded file with content "to delete" to "/textfile0.txt"
    When user "<user>" deletes file "/textfile0.txt" using the WebDAV API
    Then the HTTP status code should be "204"
    And as "<user>" file "/textfile0.txt" should exist in the trashbin
    But as "<user>" file "/textfile0.txt" should not exist
    Examples:
      | dav-path-version | user     |
      | new              | dash-123 |
      | new              | null     |
      | new              | nil      |
      | spaces           | dash-123 |
      | spaces           | null     |
      | spaces           | nil      |


  Scenario Outline: deleting a file with comma in the filename moves it to trashbin
    Given using <dav-path-version> DAV path
    And user "Alice" has uploaded file with content "file with comma in filename" to "sample,1.txt"
    When user "Alice" deletes file "sample,1.txt" using the WebDAV API
    Then the HTTP status code should be "204"
    And as "Alice" file "sample,1.txt" should exist in the trashbin
    But as "Alice" file "sample,1.txt" should not exist
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |


  Scenario Outline: deleting a folder moves all its content to the trashbin
    Given using <dav-path-version> DAV path
    And user "Alice" has created folder "/new-folder"
    And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/new-folder/new-file.txt"
    When user "Alice" deletes folder "/new-folder" using the WebDAV API
    Then the HTTP status code should be "204"
    And as "Alice" the file with original path "/new-folder/new-file.txt" should exist in the trashbin
    And as "Alice" the folder with original path "/new-folder" should exist in the trashbin
    And as "Alice" file "/new-folder/new-file.txt" should exist in the trashbin
    But as "Alice" file "/new-folder/new-file.txt" should not exist
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @issue-541
  Scenario Outline: deleted file has appropriate deletion time information
    Given using <dav-path-version> DAV path
    And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2018 04:18:13 GMT"
    And user "Alice" has deleted file "file.txt"
    When user "Alice" tries to list the trashbin content for user "Alice"
    Then the HTTP status code should be "207"
    And the deleted file "file.txt" should have the correct deletion mtime in the response
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @issue-1547
  Scenario Outline: deleting files with special characters moves it to trashbin
    Given using <dav-path-version> DAV path
    And user "Alice" has uploaded the following files with content "special character file"
      | path             |
      | qa&dev.txt       |
      | !@tester$^.txt   |
      | %file *?2.txt    |
      | # %ab ab?=ed.txt |
      | fo.              |
      | fo.1             |
      | fo...1..         |
      | ...              |
      | ..fo             |
      | fo.xyz           |
    When user "Alice" deletes the following files
      | path             |
      | qa&dev.txt       |
      | !@tester$^.txt   |
      | %file *?2.txt    |
      | # %ab ab?=ed.txt |
      | fo.              |
      | fo.1             |
      | fo...1..         |
      | ...              |
      | ..fo             |
      | fo.xyz           |
    Then the HTTP status code of responses on all endpoints should be "204"
    And as "Alice" the following files should not exist
      | path             |
      | qa&dev.txt       |
      | !@tester$^.txt   |
      | %file *?2.txt    |
      | # %ab ab?=ed.txt |
      | fo.              |
      | fo.1             |
      | fo...1..         |
      | ...              |
      | ..fo             |
      | fo.xyz           |
    But as "Alice" the files with following original paths should exist in the trashbin
      | path             |
      | qa&dev.txt       |
      | !@tester$^.txt   |
      | %file *?2.txt    |
      | # %ab ab?=ed.txt |
      | fo.              |
      | fo.1             |
      | fo...1..         |
      | ...              |
      | ..fo             |
      | fo.xyz           |
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |

  @issue-1547
  Scenario Outline: deleting folders with special characters moves it to trashbin
    Given using <dav-path-version> DAV path
    And user "Alice" has created the following folders
      | path         |
      | qa&dev       |
      | !@tester$^   |
      | %file *?2    |
      | # %ab ab?=ed |
      | fo.          |
      | fo.1         |
      | fo...1..     |
      | ...          |
      | ..fo         |
      | fo.xyz       |
    When user "Alice" deletes the following folders
      | path         |
      | qa&dev       |
      | !@tester$^   |
      | %file *?2    |
      | # %ab ab?=ed |
      | fo.          |
      | fo.1         |
      | fo...1..     |
      | ...          |
      | ..fo         |
      | fo.xyz       |
    Then the HTTP status code of responses on all endpoints should be "204"
    But as "Alice" the following folders should not exist
      | path         |
      | qa&dev       |
      | !@tester$^   |
      | %file *?2    |
      | # %ab ab?=ed |
      | fo.          |
      | fo.1         |
      | fo...1..     |
      | ...          |
      | ..fo         |
      | fo.xyz       |
    And as "Alice" the folders with following original paths should exist in the trashbin
      | path         |
      | qa&dev       |
      | !@tester$^   |
      | %file *?2    |
      | # %ab ab?=ed |
      | fo.          |
      | fo.1         |
      | fo...1..     |
      | ...          |
      | ..fo         |
      | fo.xyz       |
    Examples:
      | dav-path-version |
      | new              |
      | spaces           |