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
This commit is contained in:
@@ -9,7 +9,7 @@ Feature: copying from public link share
|
||||
And user "Alice" has created folder "/PARENT"
|
||||
And the config "OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD" has been set to "false"
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario: copy file within a public link folder new public WebDAV API
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
|
||||
And using SharingNG
|
||||
@@ -24,7 +24,7 @@ Feature: copying from public link share
|
||||
And the content of file "/PARENT/testfile.txt" for user "Alice" should be "some data"
|
||||
And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data"
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario: copy folder within a public link folder new public WebDAV API
|
||||
Given user "Alice" has created folder "/PARENT/testFolder"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"
|
||||
@@ -40,7 +40,7 @@ Feature: copying from public link share
|
||||
And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data"
|
||||
And the content of file "/PARENT/testFolder-copy/testfile.txt" for user "Alice" should be "some data"
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario: copy file within a public link folder to a new folder
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
|
||||
And user "Alice" has created folder "/PARENT/testFolder"
|
||||
@@ -56,7 +56,7 @@ Feature: copying from public link share
|
||||
And the content of file "/PARENT/testfile.txt" for user "Alice" should be "some data"
|
||||
And the content of file "/PARENT/testFolder/copy1.txt" for user "Alice" should be "some data"
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario: copy file within a public link folder to existing file
|
||||
Given user "Alice" has uploaded file with content "some data 0" to "/PARENT/testfile.txt"
|
||||
And user "Alice" has uploaded file with content "some data 1" to "/PARENT/copy1.txt"
|
||||
@@ -71,7 +71,7 @@ Feature: copying from public link share
|
||||
And as "Alice" file "/PARENT/copy1.txt" should exist
|
||||
And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data 0"
|
||||
|
||||
@issue-1232
|
||||
@issue-1232 @issue-10331
|
||||
Scenario: copy folder within a public link folder to existing file
|
||||
Given user "Alice" has created folder "/PARENT/testFolder"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"
|
||||
@@ -88,7 +88,7 @@ Feature: copying from public link share
|
||||
But as "Alice" file "/PARENT/copy1.txt" should not exist
|
||||
And as "Alice" file "/copy1.txt" should exist in the trashbin
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario: copy file within a public link folder and delete file
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
|
||||
And using SharingNG
|
||||
@@ -101,7 +101,7 @@ Feature: copying from public link share
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" file "/PARENT/copy1.txt" should not exist
|
||||
|
||||
@issue-1232
|
||||
@issue-1232 @issue-10331
|
||||
Scenario: copy file within a public link folder to existing folder
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
|
||||
And user "Alice" has created folder "/PARENT/new-folder"
|
||||
@@ -118,7 +118,7 @@ Feature: copying from public link share
|
||||
And as "Alice" folder "/PARENT/new-folder" should not exist
|
||||
And as "Alice" folder "new-folder" should exist in the trashbin
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario Outline: copy file with special characters in it's name within a public link folder
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/<file-name>"
|
||||
And using SharingNG
|
||||
@@ -139,7 +139,7 @@ Feature: copying from public link share
|
||||
| C++ file.cpp |
|
||||
| sample,1.txt |
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario Outline: copy file within a public link folder to a file with special characters in it's name
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
|
||||
And using SharingNG
|
||||
@@ -160,7 +160,7 @@ Feature: copying from public link share
|
||||
| C++ file.cpp |
|
||||
| sample,1.txt |
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario Outline: copy file within a public link folder into a folder with special characters
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
|
||||
And user "Alice" has created folder "/PARENT/<destination-folder-name>"
|
||||
@@ -182,7 +182,7 @@ Feature: copying from public link share
|
||||
| C++ file.cpp |
|
||||
| sample,1.txt |
|
||||
|
||||
@issue-8711
|
||||
@issue-8711 @issue-10331
|
||||
Scenario: copy file within a public link folder to a same file
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
|
||||
And using SharingNG
|
||||
@@ -194,7 +194,7 @@ Feature: copying from public link share
|
||||
Then the HTTP status code should be "204"
|
||||
And the content of file "/PARENT/testfile.txt" for user "Alice" should be "some data"
|
||||
|
||||
@issue-8711
|
||||
@issue-8711 @issue-10331
|
||||
Scenario: copy folder within a public link folder to a same folder
|
||||
Given user "Alice" has created folder "/PARENT/testFolder"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"
|
||||
@@ -208,7 +208,7 @@ Feature: copying from public link share
|
||||
And as "Alice" folder "/PARENT/testFolder" should exist
|
||||
And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data"
|
||||
|
||||
@issue-1230
|
||||
@issue-1230 @issue-10331
|
||||
Scenario: copy file within a public link folder to a share item root
|
||||
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
|
||||
And using SharingNG
|
||||
@@ -221,7 +221,7 @@ Feature: copying from public link share
|
||||
And as "Alice" file "/PARENT/testfile.txt" should exist
|
||||
And the content of file "/PARENT/testfile.txt" for user "Alice" should be "some data"
|
||||
|
||||
@issue-1230
|
||||
@issue-1230 @issue-10331
|
||||
Scenario: copy folder within a public link folder to a share item root
|
||||
Given user "Alice" has created folder "/PARENT/testFolder"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"
|
||||
|
||||
@@ -91,7 +91,7 @@ Feature: update a public link share
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
|
||||
|
||||
@issue-9724 @issue-10331
|
||||
Scenario Outline: creating a new public link share with password and adding an expiration date using public API
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
|
||||
@@ -225,7 +225,7 @@ Feature: update a public link share
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
|
||||
@issue-1269
|
||||
@issue-1269 @issue-9724 @issue-10331
|
||||
Scenario Outline: updating share permissions from change to read restricts public from deleting files using the public API
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Alice" has created folder "PARENT"
|
||||
@@ -249,7 +249,7 @@ Feature: update a public link share
|
||||
| 1 |
|
||||
| 2 |
|
||||
|
||||
|
||||
@issue-9724 @issue-10331
|
||||
Scenario Outline: updating share permissions from read to change allows public to delete files using the public API
|
||||
Given using OCS API version "<ocs-api-version>"
|
||||
And user "Alice" has created folder "PARENT"
|
||||
|
||||
@@ -9,7 +9,7 @@ Feature: upload to a public link share
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario Outline: uploading file to a public upload-only share using public API that was deleted does not work
|
||||
Given using <dav-path-version> DAV path
|
||||
And using SharingNG
|
||||
@@ -29,7 +29,7 @@ Feature: upload to a public link share
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-1269
|
||||
@issue-1269 @issue-10331
|
||||
Scenario: uploading file to a public read-only share folder with public API does not work
|
||||
Given using SharingNG
|
||||
And user "Alice" has created the following resource link share:
|
||||
@@ -40,7 +40,7 @@ Feature: upload to a public link share
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test-file" using the new public WebDAV API
|
||||
And the HTTP status code should be "403"
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario: uploading to a public upload-only share with public API
|
||||
Given using SharingNG
|
||||
And user "Alice" has created the following resource link share:
|
||||
@@ -54,7 +54,7 @@ Feature: upload to a public link share
|
||||
And the following headers should match these regular expressions
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario: uploading to a public upload-only share with password with public API
|
||||
Given using SharingNG
|
||||
And user "Alice" has created the following resource link share:
|
||||
@@ -66,7 +66,7 @@ Feature: upload to a public link share
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
|
||||
|
||||
|
||||
@issue-10331
|
||||
Scenario: uploading to a public read/write share with password with public API
|
||||
Given using SharingNG
|
||||
And user "Alice" has created the following resource link share:
|
||||
@@ -78,7 +78,7 @@ Feature: upload to a public link share
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
|
||||
|
||||
@skipOnReva
|
||||
@skipOnReva @issue-10331
|
||||
Scenario: uploading file to a public shared folder with read/write permission when the sharer has insufficient quota does not work with public API
|
||||
Given using SharingNG
|
||||
And user "Alice" has created the following resource link share:
|
||||
@@ -90,7 +90,7 @@ Feature: upload to a public link share
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test2" using the new public WebDAV API
|
||||
Then the HTTP status code should be "507"
|
||||
|
||||
@skipOnReva
|
||||
@skipOnReva @issue-10331
|
||||
Scenario: uploading file to a public shared folder with upload-only permission when the sharer has insufficient quota does not work with public API
|
||||
Given using SharingNG
|
||||
And user "Alice" has created the following resource link share:
|
||||
@@ -102,7 +102,7 @@ Feature: upload to a public link share
|
||||
When the public uploads file "test.txt" with password "%public%" and content "test2" using the new public WebDAV API
|
||||
Then the HTTP status code should be "507"
|
||||
|
||||
@smokeTest
|
||||
@smokeTest @issue-10331
|
||||
Scenario: uploading to a public upload-write and no edit and no overwrite share with public API
|
||||
Given using SharingNG
|
||||
And user "Alice" has created the following resource link share:
|
||||
@@ -114,7 +114,7 @@ Feature: upload to a public link share
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test2"
|
||||
|
||||
@smokeTest @issue-1267
|
||||
@smokeTest @issue-1267 @issue-10331
|
||||
Scenario: uploading same file to a public upload-write and no edit and no overwrite share multiple times with new public API
|
||||
Given using SharingNG
|
||||
And user "Alice" has created the following resource link share:
|
||||
|
||||
Reference in New Issue
Block a user