Removed core issue tag, refactored ocis-reva, ocis issue tag
This commit is contained in:
@@ -18,7 +18,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@smokeTest @issue-ocis-reva-196
|
||||
@smokeTest @issue-1291
|
||||
Scenario Outline: Uploading a file with checksum should return the checksum in the propfind
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
@@ -34,7 +34,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@smokeTest @issue-ocis-reva-98
|
||||
@smokeTest @issue-1316
|
||||
Scenario Outline: Uploading a file with checksum should return the checksum in the download header
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
@@ -51,7 +51,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-196
|
||||
@issue-1291
|
||||
Scenario Outline: Moving a file with checksum should return the checksum in the propfind
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
@@ -68,7 +68,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-98
|
||||
@issue-1316
|
||||
Scenario Outline: Downloading a file with checksum should return the checksum in the download header
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
@@ -86,7 +86,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-196
|
||||
@issue-1291
|
||||
Scenario Outline: Uploading a chunked file with checksum should return the checksum in the propfind
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded chunk file "1" of "3" with "AAAAA" to "/myChecksumFile.txt" with checksum "MD5:45a72715acdd5019c5be30bdbb75233e"
|
||||
@@ -104,7 +104,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-17
|
||||
@issue-1343
|
||||
Scenario Outline: Uploading a chunked file with checksum should return the checksum in the download header
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded chunk file "1" of "3" with "AAAAA" to "/myChecksumFile.txt" with checksum "MD5:45a72715acdd5019c5be30bdbb75233e"
|
||||
@@ -122,7 +122,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-14
|
||||
|
||||
Scenario Outline: Moving file with checksum should return the checksum in the download header
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
@@ -140,7 +140,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-196
|
||||
@issue-1291
|
||||
Scenario Outline: Copying a file with checksum should return the checksum in the propfind using new DAV path
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
@@ -156,7 +156,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-98
|
||||
@issue-1316
|
||||
Scenario Outline: Copying file with checksum should return the checksum in the download header using new DAV path
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
@@ -172,7 +172,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@files_sharing-app-required @issue-ocis-reva-196
|
||||
@files_sharing-app-required @issue-1291
|
||||
Scenario Outline: Sharing a file with checksum should return the checksum in the propfind using new DAV path
|
||||
Given auto-accept shares has been disabled
|
||||
And using <dav_version> DAV path
|
||||
@@ -187,7 +187,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| new |
|
||||
|
||||
@files_sharing-app-required @issue-ocis-reva-196 @skipOnOcV10
|
||||
@files_sharing-app-required @issue-1291 @skipOnOcV10
|
||||
Scenario Outline: Modifying a shared file should return correct checksum in the propfind using new DAV path
|
||||
Given auto-accept shares has been disabled
|
||||
And using <dav_version> DAV path
|
||||
@@ -202,7 +202,7 @@ Feature: checksums
|
||||
| dav_version | checksum |
|
||||
| new | SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a |
|
||||
|
||||
@issue-ocis-reva-99
|
||||
@issue-1315
|
||||
Scenario Outline: Upload a file where checksum does not match
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" uploads file with checksum "SHA1:f005ba11" and content "Some Text" to "/chksumtst.txt" using the WebDAV API
|
||||
@@ -234,7 +234,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-99
|
||||
@issue-1315
|
||||
Scenario Outline: Uploaded file should have the same checksum when downloaded
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/chksumtst.txt"
|
||||
@@ -254,7 +254,7 @@ Feature: checksums
|
||||
| spaces |
|
||||
|
||||
## Validation Plugin or Old Endpoint Specific
|
||||
@issue-ocis-reva-17
|
||||
@issue-1343
|
||||
Scenario Outline: Uploading an old method chunked file with checksum should fail using new DAV path
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" uploads chunk file "1" of "3" with "AAAAA" to "/myChecksumFile.txt" with checksum "MD5:45a72715acdd5019c5be30bdbb75233e" using the WebDAV API
|
||||
@@ -271,7 +271,7 @@ Feature: checksums
|
||||
| spaces |
|
||||
|
||||
## upload overwriting
|
||||
@issue-ocis-reva-196
|
||||
@issue-1291
|
||||
Scenario Outline: Uploading a file with MD5 checksum overwriting an existing file
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file with content "some data" to "textfile0.txt"
|
||||
@@ -294,7 +294,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-196
|
||||
@issue-1291
|
||||
Scenario Outline: Uploading a file with SHA1 checksum overwriting an existing file
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file with content "some data" to "textfile0.txt"
|
||||
@@ -317,7 +317,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @issue-ocis-reva-196
|
||||
@skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @issue-1291
|
||||
Scenario Outline: Uploading a file with invalid SHA1 checksum overwriting an existing file
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
|
||||
@@ -335,7 +335,7 @@ Feature: checksums
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-214
|
||||
@issue-1296
|
||||
Scenario Outline: Uploading a file with checksum should work for file with special characters
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to <renamed_file> with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" using the WebDAV API
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
@api
|
||||
Feature: Other tests related to api
|
||||
|
||||
@issue-ocis-reva-100
|
||||
@issue-1314
|
||||
Scenario: robots.txt file should be accessible
|
||||
When a user requests "/robots.txt" with "GET" and no authentication
|
||||
Then the HTTP status code should be "200"
|
||||
|
||||
Reference in New Issue
Block a user