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

Used kebab case for example table header name

Browse Source
This commit is contained in:
Prarup Gurung
2024-03-21 09:06:38 +05:45
parent 84a14c5953
commit ba7d91ebce
57 changed files with 900 additions and 898 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/coreApiWebdavProperties/createFileFolder.feature
+9 -9
View File
@@ -10,11 +10,11 @@ Feature: create files and folder
Scenario Outline: create a folder
Given using <dav-path-version> DAV path
When user "Alice" creates folder "<folder_name>" using the WebDAV API
When user "Alice" creates folder "<folder-name>" using the WebDAV API
Then the HTTP status code should be "201"
And as "Alice" folder "<folder_name>" should exist
And as "Alice" folder "<folder-name>" should exist
Examples:
| dav-path-version | folder_name |
| dav-path-version | folder-name |
| old | /upload |
| old | /strängé folder |
| old | /C++ folder.cpp |
@@ -34,7 +34,7 @@ Feature: create files and folder
@skipOnRevaMaster
Examples:
| dav-path-version | folder_name |
| dav-path-version | folder-name |
| spaces | /upload |
| spaces | /strängé folder |
| spaces | /C++ folder.cpp |
@@ -143,12 +143,12 @@ Feature: create files and folder
Scenario Outline: create a file
Given using <dav-path-version> DAV path
When user "Alice" uploads file with content "some text" to "<file_name>" using the WebDAV API
When user "Alice" uploads file with content "some text" to "<file-name>" using the WebDAV API
Then the HTTP status code should be "201"
And as "Alice" file "<file_name>" should exist
And the content of file "<file_name>" for user "Alice" should be "some text"
And as "Alice" file "<file-name>" should exist
And the content of file "<file-name>" for user "Alice" should be "some text"
Examples:
| dav-path-version | file_name |
| dav-path-version | file-name |
| old | /upload.txt |
| old | /strängéfile.txt |
| old | /C++ file.cpp |
@@ -168,7 +168,7 @@ Feature: create files and folder
@skipOnRevaMaster
Examples:
| dav-path-version | file_name |
| dav-path-version | file-name |
| spaces | /upload.txt |
| spaces | /strängéfile.txt |
| spaces | /C++ file.cpp |
tests/acceptance/features/coreApiWebdavProperties/createFileFolderWhenSharesExist.feature
+6 -6
View File
@@ -15,12 +15,12 @@ Feature: create file or folder named similar to Shares folder
Scenario Outline: create a folder with a name similar to Shares
Given using <dav-path-version> DAV path
When user "Brian" creates folder "<folder_name>" using the WebDAV API
When user "Brian" creates folder "<folder-name>" using the WebDAV API
Then the HTTP status code should be "201"
And as "Brian" folder "<folder_name>" should exist
And as "Brian" folder "<folder-name>" should exist
And as "Brian" folder "/Shares" should exist
Examples:
| dav-path-version | folder_name |
| dav-path-version | folder-name |
| old | /Share |
| old | /shares |
| old | /Shares1 |
@@ -31,12 +31,12 @@ Feature: create file or folder named similar to Shares folder
Scenario Outline: create a file with a name similar to Shares
Given using <dav-path-version> DAV path
When user "Brian" uploads file with content "some text" to "<file_name>" using the WebDAV API
When user "Brian" uploads file with content "some text" to "<file-name>" using the WebDAV API
Then the HTTP status code should be "201"
And the content of file "<file_name>" for user "Brian" should be "some text"
And the content of file "<file-name>" for user "Brian" should be "some text"
And as "Brian" folder "/Shares" should exist
Examples:
| dav-path-version | file_name |
| dav-path-version | file-name |
| old | /Share |
| old | /shares |
| old | /Shares1 |
tests/acceptance/features/coreApiWebdavProperties/getFileProperties.feature
+23 -23
View File
@@ -10,12 +10,12 @@ Feature: get file properties
@smokeTest
Scenario Outline: user sends a PROPFIND request on various file names
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
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 "207"
And the properties response should contain an etag
Examples:
| dav-path-version | file_name |
| dav-path-version | file-name |
| old | /upload.txt |
| old | /strängé file.txt |
| old | /नेपाली.txt |
@@ -27,7 +27,7 @@ Feature: get file properties
@skipOnRevaMaster
Examples:
| dav-path-version | file_name |
| dav-path-version | file-name |
| spaces | /upload.txt |
| spaces | /strängé file.txt |
| spaces | /नेपाली.txt |
@@ -36,13 +36,13 @@ Feature: get file properties
@issue-1296
Scenario Outline: user sends a PROPFIND request on various file with '?, #, &, +' in its name
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
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 "207"
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"
And there should be an entry with href containing "<expected-href>" in the response to user "Alice"
Examples:
| dav-path-version | file_name | expected_href |
| 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 |
@@ -54,7 +54,7 @@ Feature: get file properties
@skipOnRevaMaster
Examples:
| dav-path-version | file_name | expected_href |
| 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 |
@@ -63,16 +63,16 @@ Feature: get file properties
@issue-1296
Scenario Outline: user sends a PROPFIND request on various folder names
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"
When user "Alice" gets the properties of folder "<folder_name>" with depth 1 using the WebDAV API
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"
When user "Alice" gets the properties of folder "<folder-name>" with depth 1 using the WebDAV API
Then the HTTP status code should be "207"
And there should be an entry with href containing "<expected_href>/" in the response to user "Alice"
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"
And there should be an entry with href containing "<expected-href>/" in the response to user "Alice"
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-path-version | folder_name | expected_href |
| 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 |
@@ -90,7 +90,7 @@ Feature: get file properties
@skipOnRevaMaster
Examples:
| dav-path-version | folder_name | expected_href |
| 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 |
@@ -102,13 +102,13 @@ Feature: get file properties
Scenario Outline: user sends a PROPFIND request on various files inside various folders
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
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 "207"
And the properties response should contain an etag
Examples:
| dav-path-version | folder_name | file_name |
| 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 |
@@ -122,7 +122,7 @@ Feature: get file properties
@skipOnRevaMaster
Examples:
| dav-path-version | folder_name | file_name |
| 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 |
tests/acceptance/features/coreApiWebdavProperties/getQuota.feature
+2 -2
View File
@@ -45,13 +45,13 @@ Feature: get quota
| shareType | user |
| permissions | all |
| shareWith | Alice |
When user "Alice" gets the following properties of folder "<folder-path>" inside space "Shares" using the WebDAV API
When user "Alice" gets the following properties of folder "<folder-name>" inside space "Shares" using the WebDAV API
| propertyName |
| d:quota-available-bytes |
Then the HTTP status code should be "207"
And the single response should contain a property "d:quota-available-bytes" with value "9000"
Examples:
| dav-path-version | folder-path |
| dav-path-version | folder-name |
| old | /Shares/testquota |
| new | /Shares/testquota |
| spaces | /testquota |
tests/acceptance/features/coreApiWebdavProperties/setFileProperties.feature
+10 -10
View File
@@ -84,21 +84,21 @@ Feature: set file properties
@issue-1263
Scenario Outline: setting custom DAV property using one endpoint and reading it with other endpoint
Given using <action-dav-path-version> DAV path
Given using <dav-path-version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testnewold.txt"
And user "Alice" has set property "very-custom-prop" with namespace "x1='http://whatever.org/ns'" of file "/testnewold.txt" to "lucky"
And using <other-dav-path-version> DAV path
And using <dav-path-version-2> DAV path
When user "Alice" gets a custom property "very-custom-prop" with namespace "x1='http://whatever.org/ns'" of file "/testnewold.txt"
Then the response should contain a custom "very-custom-prop" property with namespace "x1='http://whatever.org/ns'" and value "lucky"
Examples:
| action-dav-path-version | other-dav-path-version |
| old | new |
| new | old |
| dav-path-version | dav-path-version-2 |
| old | new |
| new | old |
@skipOnRevaMaster
Examples:
| action-dav-path-version | other-dav-path-version |
| spaces | new |
| spaces | old |
| new | spaces |
| old | spaces |
| dav-path-version | dav-path-version-2 |
| spaces | new |
| spaces | old |
| new | spaces |
| old | spaces |