sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refactoring example table scenerio (#6697)

Browse Source
This commit is contained in:
Sabin Panta
2023-07-12 12:42:32 +05:45
committed by GitHub
parent 51bc49d5b5
commit f2498e1fdf
62 changed files with 2869 additions and 2868 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/coreApiWebdavProperties2/getFileProperties.feature
+210 -210
View File
@@ -10,60 +10,60 @@ Feature: get file properties
@smokeTest
Scenario Outline: user sends a PROPFIND request on various file names
Given using <dav_version> DAV path
Given using <dav-path-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 HTTP status code should be "201"
And the properties response should contain an etag
Examples:
| dav_version | file_name |
| old | /upload.txt |
| old | /strängé file.txt |
| old | /नेपाली.txt |
| old | s,a,m,p,l,e.txt |
| new | /upload.txt |
| new | /strängé file.txt |
| new | /नेपाली.txt |
| new | s,a,m,p,l,e.txt |
| dav-path-version | file_name |
| old | /upload.txt |
| old | /strängé file.txt |
| old | /नेपाली.txt |
| old | s,a,m,p,l,e.txt |
| new | /upload.txt |
| new | /strängé file.txt |
| new | /नेपाली.txt |
| new | s,a,m,p,l,e.txt |
@skipOnRevaMaster
Examples:
| dav_version | file_name |
| spaces | /upload.txt |
| spaces | /strängé file.txt |
| spaces | /नेपाली.txt |
| spaces | s,a,m,p,l,e.txt |
| dav-path-version | file_name |
| spaces | /upload.txt |
| spaces | /strängé file.txt |
| spaces | /नेपाली.txt |
| spaces | s,a,m,p,l,e.txt |
@issue-1296
Scenario Outline: user sends a PROPFIND request on various file with '?, #, &, +' in its name
Given using <dav_version> DAV path
Given using <dav-path-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 HTTP status code should be "201"
And the properties response should contain an etag
And there should be an entry with href containing "<expected_href>" in the response to user "Alice"
Examples:
| dav_version | file_name | expected_href |
| old | /C++ file.cpp | remote.php/webdav/C++ file.cpp |
| old | /file #2.txt | remote.php/webdav/file #2.txt |
| old | /file ?2.txt | remote.php/webdav/file ?2.txt |
| old | /file &2.txt | remote.php/webdav/file &2.txt |
| new | /C++ file.cpp | remote.php/dav/files/%username%/C++ file.cpp |
| new | /file #2.txt | remote.php/dav/files/%username%/file #2.txt |
| new | /file ?2.txt | remote.php/dav/files/%username%/file ?2.txt |
| new | /file &2.txt | remote.php/dav/files/%username%/file &2.txt |
| dav-path-version | file_name | expected_href |
| old | /C++ file.cpp | remote.php/webdav/C++ file.cpp |
| old | /file #2.txt | remote.php/webdav/file #2.txt |
| old | /file ?2.txt | remote.php/webdav/file ?2.txt |
| old | /file &2.txt | remote.php/webdav/file &2.txt |
| new | /C++ file.cpp | remote.php/dav/files/%username%/C++ file.cpp |
| new | /file #2.txt | remote.php/dav/files/%username%/file #2.txt |
| new | /file ?2.txt | remote.php/dav/files/%username%/file ?2.txt |
| new | /file &2.txt | remote.php/dav/files/%username%/file &2.txt |
@skipOnRevaMaster
Examples:
| dav_version | file_name | expected_href |
| spaces | /C++ file.cpp | dav/spaces/%spaceid%/C++ file.cpp |
| spaces | /file #2.txt | dav/spaces/%spaceid%/file #2.txt |
| spaces | /file ?2.txt | dav/spaces/%spaceid%/file ?2.txt |
| spaces | /file &2.txt | dav/spaces/%spaceid%/file &2.txt |
| dav-path-version | file_name | expected_href |
| spaces | /C++ file.cpp | dav/spaces/%spaceid%/C++ file.cpp |
| spaces | /file #2.txt | dav/spaces/%spaceid%/file #2.txt |
| spaces | /file ?2.txt | dav/spaces/%spaceid%/file ?2.txt |
| spaces | /file &2.txt | dav/spaces/%spaceid%/file &2.txt |
@issue-1296
Scenario Outline: user sends a PROPFIND request on various folder names
Given using <dav_version> DAV path
Given using <dav-path-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"
@@ -73,85 +73,85 @@ Feature: get file properties
And there should be an entry with href containing "<expected_href>/file1.txt" in the response to user "Alice"
And there should be an entry with href containing "<expected_href>/file2.txt" in the response to user "Alice"
Examples:
| dav_version | folder_name | expected_href |
| old | /upload | remote.php/webdav/upload |
| old | /strängé folder | remote.php/webdav/strängé folder |
| old | /C++ folder | remote.php/webdav/C++ folder |
| old | /नेपाली | remote.php/webdav/नेपाली |
| old | /folder #2.txt | remote.php/webdav/folder #2.txt |
| old | /folder ?2.txt | remote.php/webdav/folder ?2.txt |
| old | /folder &2.txt | remote.php/webdav/folder &2.txt |
| new | /upload | remote.php/dav/files/%username%/upload |
| new | /strängé folder | remote.php/dav/files/%username%/strängé folder |
| new | /C++ folder | remote.php/dav/files/%username%/C++ folder |
| new | /नेपाली | remote.php/dav/files/%username%/नेपाली |
| new | /folder #2.txt | remote.php/dav/files/%username%/folder #2.txt |
| new | /folder ?2.txt | remote.php/dav/files/%username%/folder ?2.txt |
| new | /folder &2.txt | remote.php/dav/files/%username%/folder &2.txt |
| dav-path-version | folder_name | expected_href |
| old | /upload | remote.php/webdav/upload |
| old | /strängé folder | remote.php/webdav/strängé folder |
| old | /C++ folder | remote.php/webdav/C++ folder |
| old | /नेपाली | remote.php/webdav/नेपाली |
| old | /folder #2.txt | remote.php/webdav/folder #2.txt |
| old | /folder ?2.txt | remote.php/webdav/folder ?2.txt |
| old | /folder &2.txt | remote.php/webdav/folder &2.txt |
| new | /upload | remote.php/dav/files/%username%/upload |
| new | /strängé folder | remote.php/dav/files/%username%/strängé folder |
| new | /C++ folder | remote.php/dav/files/%username%/C++ folder |
| new | /नेपाली | remote.php/dav/files/%username%/नेपाली |
| new | /folder #2.txt | remote.php/dav/files/%username%/folder #2.txt |
| new | /folder ?2.txt | remote.php/dav/files/%username%/folder ?2.txt |
| new | /folder &2.txt | remote.php/dav/files/%username%/folder &2.txt |
@skipOnRevaMaster
Examples:
| dav_version | folder_name | expected_href |
| spaces | /upload | dav/spaces/%spaceid%/upload |
| spaces | /strängé folder | dav/spaces/%spaceid%/strängé folder |
| spaces | /C++ folder | dav/spaces/%spaceid%/C++ folder |
| spaces | /नेपाली | dav/spaces/%spaceid%/नेपाली |
| spaces | /folder #2.txt | dav/spaces/%spaceid%/folder #2.txt |
| spaces | /folder ?2.txt | dav/spaces/%spaceid%/folder ?2.txt |
| spaces | /folder &2.txt | dav/spaces/%spaceid%/folder &2.txt |
| dav-path-version | folder_name | expected_href |
| spaces | /upload | dav/spaces/%spaceid%/upload |
| spaces | /strängé folder | dav/spaces/%spaceid%/strängé folder |
| spaces | /C++ folder | dav/spaces/%spaceid%/C++ folder |
| spaces | /नेपाली | dav/spaces/%spaceid%/नेपाली |
| spaces | /folder #2.txt | dav/spaces/%spaceid%/folder #2.txt |
| spaces | /folder ?2.txt | dav/spaces/%spaceid%/folder ?2.txt |
| spaces | /folder &2.txt | dav/spaces/%spaceid%/folder &2.txt |
Scenario Outline: user sends a PROPFIND request on various files inside various folders
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "<folder_name>"
And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/<file_name>"
When user "Alice" gets the properties of file "<folder_name>/<file_name>" using the WebDAV API
Then the HTTP status code should be "201"
And the properties response should contain an etag
Examples:
| dav_version | folder_name | file_name |
| old | /upload | abc.txt |
| old | /strängé folder | strängé file.txt |
| old | /C++ folder | C++ file.cpp |
| old | /नेपाली | नेपाली |
| old | /folder #2.txt | file #2.txt |
| new | /upload | abc.txt |
| new | /strängé folder (duplicate #2 &) | strängé file (duplicate #2 &) |
| new | /C++ folder | C++ file.cpp |
| new | /नेपाली | नेपाली |
| new | /folder #2.txt | file #2.txt |
| dav-path-version | folder_name | file_name |
| old | /upload | abc.txt |
| old | /strängé folder | strängé file.txt |
| old | /C++ folder | C++ file.cpp |
| old | /नेपाली | नेपाली |
| old | /folder #2.txt | file #2.txt |
| new | /upload | abc.txt |
| new | /strängé folder (duplicate #2 &) | strängé file (duplicate #2 &) |
| new | /C++ folder | C++ file.cpp |
| new | /नेपाली | नेपाली |
| new | /folder #2.txt | file #2.txt |
@skipOnRevaMaster
Examples:
| dav_version | folder_name | file_name |
| spaces | /upload | abc.txt |
| spaces | /strängé folder | strängé file.txt |
| spaces | /C++ folder | C++ file.cpp |
| spaces | /नेपाली | नेपाली |
| spaces | /folder #2.txt | file #2.txt |
| dav-path-version | folder_name | file_name |
| spaces | /upload | abc.txt |
| spaces | /strängé folder | strängé file.txt |
| spaces | /C++ folder | C++ file.cpp |
| spaces | /नेपाली | नेपाली |
| spaces | /folder #2.txt | file #2.txt |
@issue-1259
#after fixing all issues delete this Scenario and merge with the one above
Scenario Outline: user sends a PROPFIND request on various files inside various folders with '?' character in its name
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/folder ?2.txt"
And user "Alice" has uploaded file with content "uploaded content" to "/folder ?2.txt/file ?2.txt"
When user "Alice" gets the properties of file "/folder ?2.txt/file ?2.txt" using the WebDAV API
Then the HTTP status code should be "201"
And the properties response should contain an etag
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: file that is not shared does not have a share-types property
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
When user "Alice" gets the following properties of folder "/test" using the WebDAV API
| propertyName |
@@ -159,18 +159,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the response should contain an empty property "oc:share-types"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: file that is shared to a user has a share-types property
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
And user "Alice" has created folder "/test"
And user "Alice" has created a share with settings
@@ -185,18 +185,18 @@ Feature: get file properties
And the response should contain a share-types property with
| 0 |
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: file that is shared to a group has a share-types property
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And group "grp1" has been created
And user "Alice" has created folder "/test"
And user "Alice" has created a share with settings
@@ -211,18 +211,18 @@ Feature: get file properties
And the response should contain a share-types property with
| 1 |
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: file that is shared by link has a share-types property
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
And user "Alice" has created a public link share with settings
| path | test |
@@ -234,18 +234,18 @@ Feature: get file properties
And the response should contain a share-types property with
| 3 |
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: file that is shared by user,group and link has a share-types property
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
And group "grp1" has been created
And user "Alice" has created folder "/test"
@@ -271,18 +271,18 @@ Feature: get file properties
| 1 |
| 3 |
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
@smokeTest @issue-2809
Scenario Outline: retrieving a private link
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/somefile.txt"
When user "Alice" gets the following properties of file "/somefile.txt" using the WebDAV API
| propertyName |
@@ -290,14 +290,14 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "oc:privatelink" with value like "%(/(index.php/)?f/[0-9]*)%"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user sends a PROPFIND request on a nonexistent URL
@@ -319,7 +319,7 @@ Feature: get file properties
@issue-1297
Scenario Outline: add, receive multiple custom meta properties to a file
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/TestFolder"
And user "Alice" has uploaded file with content "test data one" to "/TestFolder/test1.txt"
And user "Alice" has set the following properties of file "/TestFolder/test1.txt" using the WebDav API
@@ -337,18 +337,18 @@ Feature: get file properties
| /TestFolder/test1.txt | testprop2 | BBBBB |
| /TestFolder/test1.txt | status | HTTP/1.1 200 OK |
Examples:
| dav_version |
| new |
| old |
| dav-path-version |
| new |
| old |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
@issue-1297
Scenario Outline: add multiple properties to files inside a folder and do a propfind of the parent folder
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/TestFolder"
And user "Alice" has uploaded file with content "test data one" to "/TestFolder/test1.txt"
And user "Alice" has uploaded file with content "test data two" to "/TestFolder/test2.txt"
@@ -373,18 +373,18 @@ Feature: get file properties
| /TestFolder/test2.txt | testprop2 | DDDDD |
| /TestFolder/ | status | HTTP/1.1 404 Not Found |
Examples:
| dav_version |
| new |
| old |
| dav-path-version |
| new |
| old |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the last modified date of a folder using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
When user "Alice" gets the following properties of folder "/test" using the WebDAV API
| propertyName |
@@ -392,18 +392,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "d:getlastmodified" with value like "/^[MTWFS][uedhfriatno]{2},\s(\d){2}\s[JFMAJSOND][anebrpyulgctov]{2}\s\d{4}\s\d{2}:\d{2}:\d{2} GMT$/"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the content type of a folder using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
When user "Alice" gets the following properties of folder "/test" using the WebDAV API
| propertyName |
@@ -411,18 +411,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "d:getcontenttype" with value ""
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the content type of a file using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "file.txt"
When user "Alice" gets the following properties of folder "file.txt" using the WebDAV API
| propertyName |
@@ -430,18 +430,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "d:getcontenttype" with value "text/plain.*"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the etag of a file using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "file.txt"
When user "Alice" gets the following properties of folder "file.txt" using the WebDAV API
| propertyName |
@@ -449,18 +449,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "d:getetag" with value like '%\"[a-z0-9:]{1,32}\"%'
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the resource type of a file using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "file.txt"
When user "Alice" gets the following properties of folder "file.txt" using the WebDAV API
| propertyName |
@@ -468,18 +468,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "d:resourcetype" with value ""
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the size of a file using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "file.txt"
When user "Alice" gets the following properties of folder "file.txt" using the WebDAV API
| propertyName |
@@ -487,18 +487,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "oc:size" with value "16"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the size of a folder using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
When user "Alice" gets the following properties of folder "/test" using the WebDAV API
| propertyName |
@@ -506,18 +506,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "oc:size" with value "0"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the file id of a file using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "file.txt"
When user "Alice" gets the following properties of folder "file.txt" using the WebDAV API
| propertyName |
@@ -525,18 +525,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "oc:fileid" with value like '/[a-zA-Z0-9]+/'
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the file id of a folder using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
When user "Alice" gets the following properties of folder "/test" using the WebDAV API
| propertyName |
@@ -544,18 +544,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "oc:fileid" with value like '/[a-zA-Z0-9]+/'
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the owner display name of a file using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "file.txt"
When user "Alice" gets the following properties of file "file.txt" using the WebDAV API
| propertyName |
@@ -563,18 +563,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response about the file owned by "Alice" should contain a property "oc:owner-display-name" with value "%displayname%"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the owner display name of a folder using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
When user "Alice" gets the following properties of folder "/test" using the WebDAV API
| propertyName |
@@ -582,18 +582,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response about the file owned by "Alice" should contain a property "oc:owner-display-name" with value "%displayname%"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the permissions on a file using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "file.txt"
When user "Alice" gets the following properties of folder "file.txt" using the WebDAV API
| propertyName |
@@ -601,18 +601,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "oc:permissions" with value like '/RM{0,1}DNVW/'
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the permissions on a folder using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
When user "Alice" gets the following properties of folder "/test" using the WebDAV API
| propertyName |
@@ -620,18 +620,18 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "oc:permissions" with value like '/RM{0,1}DNVCK/'
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |
Scenario Outline: user tries to get the size of a folder with files using webdav api
Given using <dav_version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has created folder "/test"
And user "Alice" has uploaded file with content "a" to "/test/file.txt"
And user "Alice" has uploaded file with content "b" to "/test/file1.txt"
@@ -644,11 +644,11 @@ Feature: get file properties
Then the HTTP status code should be "201"
And the single response should contain a property "oc:size" with value "5"
Examples:
| dav_version |
| old |
| new |
| dav-path-version |
| old |
| new |
@skipOnRevaMaster
Examples:
| dav_version |
| spaces |
| dav-path-version |
| spaces |