Merge pull request #38914 from owncloud/skip-async-tests

[Tests-Only] skip tests for async file operations in ocis

tests/acceptance/features/apiMain/checksums.feature

@@ -160,7 +160,7 @@ Feature: checksums
     And user "Alice" should not see the following elements
       | /myChunkedFile.txt |
 
-  @issue-ocis-reva-56
+  @issue-ocis-reva-56 @notToImplementOnOCIS
   Scenario: Upload new dav chunked file using async MOVE where checksum matches
     Given using new DAV path
     And the administrator has enabled async operations
@@ -176,7 +176,7 @@ Feature: checksums
       | fileId | /^[0-9a-z]{20,}$/ |
     And the content of file "/myChunkedFile.txt" for user "Alice" should be "BBBBBCCCCC"
 
-  @issue-ocis-reva-56
+  @issue-ocis-reva-56 @notToImplementOnOCIS
   Scenario: Upload new dav chunked file using async MOVE where checksum does not match
     Given using new DAV path
     And the administrator has enabled async operations
@@ -194,7 +194,7 @@ Feature: checksums
     And user "Alice" should not see the following elements
       | /myChunkedFile.txt |
 
-  @issue-ocis-reva-56
+  @issue-ocis-reva-56 @notToImplementOnOCIS
   Scenario: Upload new dav chunked file using async MOVE where checksum does not match - retry with correct checksum
     Given using new DAV path
     And the administrator has enabled async operations

tests/acceptance/features/apiWebdavMove1/moveFileAsync.feature

@@ -1,4 +1,4 @@
-@api @issue-ocis-reva-14
+@api @issue-ocis-reva-14 @notToImplementOnOCIS
 Feature: move (rename) file
   As a user
   I want to be able to move and rename files asynchronously

tests/acceptance/features/apiWebdavMove1/moveFileToBlacklistedNameAsync.feature

@@ -1,4 +1,4 @@
-@api @issue-ocis-reva-14
+@api @issue-ocis-reva-14 @notToImplementOnOCIS
 Feature: users cannot move (rename) a file to a blacklisted name
   As an administrator
   I want to be able to prevent users from moving (renaming) files to specified file names

tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature

@@ -1,4 +1,4 @@
-@api @issue-ocis-reva-56
+@api @issue-ocis-reva-56 @notToImplementOnOCIS
 Feature: upload file using new chunking
   As a user
   I want to be able to upload "large" files in chunks asynchronously

tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedName.feature

@@ -8,7 +8,7 @@ Feature: users cannot upload a file to a blacklisted name
     Given using OCS API version "1"
     And user "Alice" has been created with default attributes and without skeleton files
 
-  @issue-ocis-reva-15
+  @issue-ocis-reva-15 @notToImplementOnOCIS
   Scenario Outline: upload a file to a filename that is banned by default
     Given using <dav_version> DAV path
     When user "Alice" uploads file with content "uploaded content" to ".htaccess" using the WebDAV API

tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature

@@ -1,4 +1,4 @@
-@api @issue-ocis-reva-56
+@api @issue-ocis-reva-56 @notToImplementOnOCIS
 Feature: users cannot upload a file to a blacklisted name using new chunking
   As an administrator
   I want to be able to prevent users from uploading files to specified file names

tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature

@@ -1,4 +1,4 @@
-@api @issue-ocis-reva-56
+@api @issue-ocis-reva-56 @notToImplementOnOCIS
 Feature: users cannot upload a file to or into an excluded directory using new chunking
   As an administrator
   I want to be able to exclude directories (folders) from being processed. Any attempt to upload a file to one of those names should be refused.

tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature

@@ -9,6 +9,7 @@ Feature: users cannot upload a file to a blacklisted name using new chunking
     And using new DAV path
     And user "Alice" has been created with default attributes and without skeleton files
 
+  @notToImplementOnOCIS
   Scenario: Upload a file to a filename that is banned by default using new chunking
     When user "Alice" creates a new chunking upload with id "chunking-42" using the WebDAV API
     And user "Alice" uploads new chunk file "1" with "AAAAA" to id "chunking-42" using the WebDAV API

tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature

@@ -9,7 +9,7 @@ Feature: users cannot upload a file to a blacklisted name using old chunking
     And using old DAV path
     And user "Alice" has been created with default attributes and without skeleton files
 
-  @skipOnOcV10 @issue-36645
+  @skipOnOcV10 @issue-36645 @notToImplementOnOCIS
   Scenario: Upload a file to a filename that is banned by default using old chunking
     When user "Alice" uploads file "filesForUpload/textfile.txt" to "/.htaccess" in 3 chunks using the WebDAV API
     Then the HTTP status code should be "403"