Remove bug demos apiWebdavProperties2-getFileProperties.feature

owncloud · Feb 3, 2021 · 1cf4d50 · 1cf4d50
1 parent ddd1daa
commit 1cf4d50
Show file tree

Hide file tree

Showing 2 changed files with 39 additions and 56 deletions.
diff --git a/tests/acceptance/features/apiBugDemonstration/apiTrashbin-trashbinDelete.feature b/tests/acceptance/features/apiBugDemonstration/apiTrashbin-trashbinDelete.feature
@@ -12,20 +12,3 @@ Feature: files and folders can be deleted from the trashbin
     And user "Alice" has created folder "PARENT/CHILD"
     And user "Alice" has uploaded file with content "to delete" to "/PARENT/parent.txt"
     And user "Alice" has uploaded file with content "to delete" to "/PARENT/CHILD/child.txt"
-
-  @smokeTest
-  @issue-ocis-reva-118
-  @issue-product-179
-  @skipOnOcis-OCIS-Storage
-  # after fixing all issues delete this Scenario and use the one from oC10 core
-  Scenario: delete a single file from the trashbin
-    Given user "Alice" has deleted file "/textfile0.txt"
-    And user "Alice" has deleted file "/textfile1.txt"
-    And user "Alice" has deleted file "/PARENT/parent.txt"
-    And user "Alice" has deleted file "/PARENT/CHILD/child.txt"
-    When user "Alice" deletes the file with original path "textfile1.txt" from the trashbin using the trashbin API
-    Then the HTTP status code should be "405"
-    And as "Alice" the file with original path "/textfile1.txt" should exist in the trashbin
-    But as "Alice" the file with original path "/textfile0.txt" should exist in the trashbin
-    And as "Alice" the file with original path "/PARENT/parent.txt" should exist in the trashbin
-    And as "Alice" the file with original path "/PARENT/CHILD/child.txt" should exist in the trashbin
diff --git a/tests/acceptance/features/apiBugDemonstration/apiWebdavProperties2-getFileProperties.feature b/tests/acceptance/features/apiBugDemonstration/apiWebdavProperties2-getFileProperties.feature
@@ -18,25 +18,25 @@ Feature: get file properties
     And the value of the item "//d:response/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>/"
     Examples:
       | dav_version | file_name     | expected_href                             |
-      | old         | /C++ file.cpp | webdav\/C\+\+%20file\.cpp                 |
+
       | old         | /file #2.txt  | webdav\/file%20%232\.txt                  |
-      | old         | /file &2.txt  | webdav\/file%20&2\.txt                    |
-      | new         | /C++ file.cpp | dav\/files\/%username%\/C\+\+%20file\.cpp |
+
+
       | new         | /file #2.txt  | dav\/files\/%username%\/file%20%232\.txt  |
-      | new         | /file &2.txt  | dav\/files\/%username%\/file%20&2\.txt    |
 
-  @issue-ocis-reva-214 @issue-ocis-reva-265 @skipOnOcis-EOS-Storage @skipOnOcis-OCIS-Storage
-  # after fixing all issues delete this Scenario and use the one from oC10 core
-  Scenario Outline: Do a PROPFIND of various file names
-    Given using <dav_version> DAV path
-    And user "Alice" has uploaded file with content "uploaded content" to "<file_name>"
-    When user "Alice" gets the properties of file "<file_name>" using the WebDAV API
-    Then the properties response should contain an etag
-    And the value of the item "//d:response/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>/"
-    Examples:
-      | dav_version | file_name    | expected_href                            |
-      | old         | /file ?2.txt | webdav\/file%20%3F2\.txt                 |
-      | new         | /file ?2.txt | dav\/files\/%username%\/file%20%3F2\.txt |
+
+#  @issue-ocis-reva-214 @issue-ocis-reva-265 @skipOnOcis-EOS-Storage @skipOnOcis-OCIS-Storage
+#  # after fixing all issues delete this Scenario and use the one from oC10 core
+#  Scenario Outline: Do a PROPFIND of various file names
+#    Given using <dav_version> DAV path
+#    And user "Alice" has uploaded file with content "uploaded content" to "<file_name>"
+#    When user "Alice" gets the properties of file "<file_name>" using the WebDAV API
+#    Then the properties response should contain an etag
+#    And the value of the item "//d:response/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>/"
+#    Examples:
+#      | dav_version | file_name    | expected_href                            |
+#      | old         | /file ?2.txt | webdav\/file%20%3F2\.txt                 |
+#      | new         | /file ?2.txt | dav\/files\/%username%\/file%20%3F2\.txt |
 
   @issue-ocis-reva-214 @skipOnOcis-OCIS-Storage
   # after fixing all issues delete this Scenario and use the one from oC10 core
@@ -52,33 +52,33 @@ Feature: get file properties
     Examples:
       | dav_version | folder_name     | expected_href                                                                  |
       | old         | /upload         | webdav\/upload                                                                 |
-      | old         | /strängé folder | webdav\/str%C3%A4ng%C3%A9%20folder                                             |
-      | old         | /C++ folder     | webdav\/C\+\+%20folder                                                         |
-      | old         | /नेपाली         | webdav\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80                 |
+#      | old         | /strängé folder | webdav\/str%C3%A4ng%C3%A9%20folder                                             |
+#      | old         | /C++ folder     | webdav\/C\+\+%20folder                                                         |
+#      | old         | /नेपाली         | webdav\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80                 |
       | old         | /folder #2.txt  | webdav\/folder%20%232\.txt                                                     |
-      | old         | /folder &2.txt  | webdav\/folder%20&2\.txt                                                       |
+#      | old         | /folder &2.txt  | webdav\/folder%20&2\.txt                                                       |
       | new         | /upload         | dav\/files\/%username%\/upload                                                 |
-      | new         | /strängé folder | dav\/files\/%username%\/str%C3%A4ng%C3%A9%20folder                             |
-      | new         | /C++ folder     | dav\/files\/%username%\/C\+\+%20folder                                         |
-      | new         | /नेपाली         | dav\/files\/%username%\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 |
+#      | new         | /strängé folder | dav\/files\/%username%\/str%C3%A4ng%C3%A9%20folder                             |
+#      | new         | /C++ folder     | dav\/files\/%username%\/C\+\+%20folder                                         |
+#      | new         | /नेपाली         | dav\/files\/%username%\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 |
       | new         | /folder #2.txt  | dav\/files\/%username%\/folder%20%232\.txt                                     |
-      | new         | /folder &2.txt  | dav\/files\/%username%\/folder%20&2\.txt                                       |
+#      | new         | /folder &2.txt  | dav\/files\/%username%\/folder%20&2\.txt                                       |
 
-  @issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage
-  # after fixing all issues delete this Scenario and use the one from oC10 core
-  Scenario Outline: Do a PROPFIND of various folder names
-    Given using <dav_version> DAV path
-    And user "Alice" has created folder "<folder_name>"
-    And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file1.txt"
-    And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file2.txt"
-    When user "Alice" gets the properties of folder "<folder_name>" with depth 1 using the WebDAV API
-    Then the value of the item "//d:response[1]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\//"
-    And the value of the item "//d:response[2]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file1.txt/"
-    And the value of the item "//d:response[3]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file2.txt/"
-    Examples:
-      | dav_version | folder_name    | expected_href                              |
-      | old         | /folder ?2.txt | webdav\/folder%20%3F2\.txt                 |
-      | new         | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt |
+#  @issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage
+#  # after fixing all issues delete this Scenario and use the one from oC10 core
+#  Scenario Outline: Do a PROPFIND of various folder names
+#    Given using <dav_version> DAV path
+#    And user "Alice" has created folder "<folder_name>"
+#    And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file1.txt"
+#    And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file2.txt"
+#    When user "Alice" gets the properties of folder "<folder_name>" with depth 1 using the WebDAV API
+#    Then the value of the item "//d:response[1]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\//"
+#    And the value of the item "//d:response[2]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file1.txt/"
+#    And the value of the item "//d:response[3]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file2.txt/"
+#    Examples:
+#      | dav_version | folder_name    | expected_href                              |
+#      | old         | /folder ?2.txt | webdav\/folder%20%3F2\.txt                 |
+#      | new         | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt |
 
   @skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage
   # after fixing all issues delete this Scenario and use the one from oC10 core