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

Refactored dav_version to new

Browse Source
This commit is contained in:
Prarup Gurung
2023-05-08 09:03:08 +05:45
parent e208b3018a
commit 62b91981ed
1 changed files with 5 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/coreApiMain/checksums.feature
+5 -11
View File
@@ -176,8 +176,8 @@ Feature: checksums
| spaces |
@issue-1291
Scenario Outline: sharing a file with checksum should return the checksum in the propfind using new DAV path
Given using <dav_version> DAV path
Scenario: sharing a file with checksum should return the checksum in the propfind using new DAV path
Given using new DAV path
And user "Brian" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
@@ -185,23 +185,17 @@ Feature: checksums
When user "Brian" requests the checksum of "/Shares/myChecksumFile.txt" via propfind
Then the HTTP status code should be "207"
And the webdav checksum should match "SHA1:3ee962b839762adb0ad8ba6023a4690be478de6f MD5:d70b40f177b14b470d1756a3c12b963a ADLER32:8ae90960"
Examples:
| dav_version |
| new |
@issue-1291
Scenario Outline: modifying a shared file should return correct checksum in the propfind using new DAV path
Given using <dav_version> DAV path
Scenario: modifying a shared file should return correct checksum in the propfind using new DAV path
Given using new DAV path
And user "Brian" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice"
When user "Brian" uploads file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/Shares/myChecksumFile.txt" using the WebDAV API
Then the HTTP status code should be "204"
And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "<checksum>"
Examples:
| dav_version | checksum |
| new | SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a |
And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a"
@issue-1315
Scenario Outline: upload a file where checksum does not match