test: make remote.php configurable

test: build dav paths

test: fix paths

test: merge method args

test: add issue tags

test: add new expected failure file

test: merge expected-failure files before running tests

tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature

@@ -25,7 +25,7 @@ Feature: A manager of the space can edit public link
     And user "Alice" has uploaded a file inside space "edit space" with content "some content" to "test.txt"
     And using SharingNG
 
-
+  @issue-9724 @issue-10331
   Scenario Outline: manager of the space can edit public link.
     Given using OCS API version "2"
     When user "Alice" updates the last public link share using the sharing API with

tests/acceptance/features/apiSpaces/publicLink.feature

@@ -14,29 +14,29 @@ Feature: public link for a space
       | permissionsRole | view         |
     And using SharingNG
 
-
+  @issue-10331
   Scenario: public tries to upload a file in the public space
     When the public uploads file "test.txt" with content "test" using the new public WebDAV API
     And the HTTP status code should be "403"
 
-
+  @issue-10331
   Scenario: public tries to create a folder in the public space
     When the public creates folder "created-by-public" using the new public WebDAV API
     And the HTTP status code should be "403"
 
-
+  @issue-10331
   Scenario: public tries to delete a file in the public space
     Given user "Alice" has uploaded a file inside space "public space" with content "some content" to "test.txt"
     When the public deletes file "test.txt" from the last public link share using the new public WebDAV API
     And the HTTP status code should be "403"
 
-
+  @issue-10331
   Scenario: public tries to delete a folder in the public space
     And user "Alice" has created a folder "/public-folder" in space "public space"
     When the public deletes folder "public-folder" from the last public link share using the new public WebDAV API
     And the HTTP status code should be "403"
 
-
+  @issue-10331
   Scenario: public tries to change content of a resources in the public space
     Given user "Alice" has uploaded a file inside space "public space" with content "some content" to "test.txt"
     When the public overwrites file "test.txt" with content "public content" using the new WebDAV API

tests/acceptance/features/apiSpaces/tusUpload.feature

@@ -40,7 +40,7 @@ Feature: upload resources using TUS protocol
       | test.txt   |
       | upload.txt |
 
-
+  @issue-10346
   Scenario Outline: upload a zero-byte file inside a shared folder
     Given using <dav-path-version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files
@@ -84,7 +84,7 @@ Feature: upload resources using TUS protocol
     When user "Alice" uploads a file from "filesForUpload/zerobyte.txt" to "textfile.txt" via TUS inside of the space "new-space" using the WebDAV API
     Then for user "Alice" the content of the file "textfile.txt" of the space "new-space" should be ""
 
-  @issue-8003
+  @issue-8003 @issue-10346
   Scenario Outline: replace a shared file with zero-byte file
     Given using <dav-path-version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files