Merge pull request #32723 from owncloud/testNotExistingOfFileOnErrorC…

…hecksum

check file existence after upload with wrong checksums

tests/acceptance/features/apiMain/checksums.feature

@@ -141,12 +141,16 @@ Feature: checksums
     And user "user0" uploads new chunk file "3" with "CCCCC" to id "chunking-42" using the WebDAV API
     And user "user0" moves new chunk file with id "chunking-42" to "/myChunkedFile.txt" with checksum "SHA1:f005ba11" using the WebDAV API
     Then the HTTP status code should be "400"
+    And user "user0" should not see the following elements
+      | /myChunkedFile.txt |
 
   Scenario Outline: Upload a file where checksum does not match
     Given using <dav_version> DAV path
     And file "/chksumtst.txt" has been deleted for user "user0"
     When user "user0" uploads file with checksum "SHA1:f005ba11" and content "Some Text" to "/chksumtst.txt" using the WebDAV API
     Then the HTTP status code should be "400"
+    And user "user0" should not see the following elements
+      | /chksumtst.txt |
     Examples:
 			| dav_version   |
 			| old           |
@@ -194,3 +198,5 @@ Feature: checksums
     Given using new DAV path
     When user "user0" uploads chunk file "1" of "3" with "AAAAA" to "/myChecksumFile.txt" with checksum "MD5:45a72715acdd5019c5be30bdbb75233e" using the WebDAV API
     Then the HTTP status code should be "503"
+    And user "user0" should not see the following elements
+      | /myChecksumFile.txt |