mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-01-05 19:59:37 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5983 from owncloud/remove-core-issue-tag-and-refactor-ocis-issus-tag

Browse Source 
[full-ci] [tests-only] Removed core issue tag, refactored ocis-reva, ocis issue tag
This commit is contained in:
Prarup Gurung
2023-04-03 03:58:54 -07:00
committed by GitHub
parent b78bea77de f3bf0894fc
commit 1a31aba659
76 changed files with 295 additions and 295 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tests/acceptance/features/apiSpacesShares/checksum.feature
View File

@@ -7,7 +7,7 @@ Feature: checksums
And using spaces DAV path
And user "Brian" has been created with default attributes and without skeleton files
@files_sharing-app-required @issue-ocis-reva-196
@files_sharing-app-required @issue-1291
Scenario: Sharing a file with checksum should return the checksum in the propfind using new DAV path
Given 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"
@@ -16,7 +16,7 @@ Feature: checksums
Then the HTTP status code should be "207"
And the webdav checksum should match "SHA1:3ee962b839762adb0ad8ba6023a4690be478de6f MD5:d70b40f177b14b470d1756a3c12b963a ADLER32:8ae90960"
@files_sharing-app-required @issue-ocis-reva-196
@files_sharing-app-required @issue-1291
Scenario: Modifying a shared file should return correct checksum in the propfind using new DAV path
Given 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"

2
tests/acceptance/features/coreApiAuthOcs/ocsDELETEAuth.feature
View File

@@ -4,7 +4,7 @@ Feature: auth
Background:
Given user "another-admin" has been created with default attributes and without skeleton files
@smokeTest @issue-ocis-reva-30 @issue-ocis-reva-65 @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @issue-32068
@smokeTest @issue-1337 @issue-1319 @skipOnBruteForceProtection @issue-brute_force_protection-112
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
Given user "another-admin" has been added to group "admin"
When user "another-admin" requests these endpoints with "DELETE" using password "invalid" about user "Alice"

12
tests/acceptance/features/coreApiAuthOcs/ocsGETAuth.feature
View File

@@ -4,7 +4,7 @@ Feature: auth
Background:
Given user "Alice" has been created with default attributes and without skeleton files
@issue-32068 @skipOnOcV10 @issue-ocis-reva-30 @smokeTest
@issue-1337 @smokeTest
Scenario: using OCS anonymously
When a user requests these endpoints with "GET" and no authentication
| endpoint |
@@ -25,7 +25,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "401"
@issue-ocis-reva-29
@issue-1338
Scenario: ocs config end point accessible by unauthorized users
When a user requests these endpoints with "GET" and no authentication
| endpoint |
@@ -38,7 +38,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"
@issue-32068 @skipOnOcV10 @issue-ocis-reva-11 @issue-ocis-reva-30 @issue-ocis-reva-31 @issue-ocis-reva-32 @issue-ocis-reva-33 @issue-ocis-reva-34 @issue-ocis-reva-35
@issue-1337 @issue-1336 @issue-1335 @issue-1334 @issue-1333
Scenario: using OCS with non-admin basic auth
When the user "Alice" requests these endpoints with "GET" with basic auth
| endpoint |
@@ -69,7 +69,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "401"
@issue-32068 @skipOnOcV10 @issue-ocis-reva-29 @issue-ocis-reva-30 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@issue-1338 @issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
Scenario: using OCS as normal user with wrong password
When user "Alice" requests these endpoints with "GET" using password "invalid"
| endpoint |
@@ -100,7 +100,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"
@issue-ocis-reva-65
@issue-1319
Scenario:using OCS with admin basic auth
When the administrator requests these endpoint with "GET"
| endpoint |
@@ -117,7 +117,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"
@issue-ocis-reva-30 @issue-ocis-reva-65 @skipOnBruteForceProtection @issue-brute_force_protection-112
@issue-1337 @issue-1319 @skipOnBruteForceProtection @issue-brute_force_protection-112
Scenario: using OCS as admin user with wrong password
Given user "another-admin" has been created with default attributes and without skeleton files
And user "another-admin" has been added to group "admin"

2
tests/acceptance/features/coreApiAuthOcs/ocsPOSTAuth.feature
View File

@@ -4,7 +4,7 @@ Feature: auth
Background:
Given user "Alice" has been created with default attributes and without skeleton files
@issue-ocis-reva-30 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
Scenario: send POST requests to OCS endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |

4
tests/acceptance/features/coreApiAuthOcs/ocsPUTAuth.feature
View File

@@ -4,7 +4,7 @@ Feature: auth
Background:
Given user "another-admin" has been created with default attributes and without skeleton files
@issue-ocis-reva-30 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
Scenario: send PUT request to OCS endpoints as admin with wrong password
Given user "another-admin" has been added to group "admin"
When user "another-admin" requests these endpoints with "PUT" including body "doesnotmatter" using password "invalid" about user "Alice"
@@ -20,7 +20,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "997"
@issue-38423 @skipOnOcV10
Scenario: Request to edit nonexistent user by authorized admin gets unauthorized in http response
Given user "another-admin" has been added to group "admin"
When user "another-admin" requests these endpoints with "PUT" including body "doesnotmatter" about user "nonexistent"

4
tests/acceptance/features/coreApiAuthWebDav/webDavCOPYAuth.feature
View File

@@ -55,7 +55,7 @@ Feature: COPY file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@issue-ocis-reva-14
Scenario: send COPY requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "COPY" about user "Alice"
| endpoint |
@@ -64,7 +64,7 @@ Feature: COPY file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "403"
@skipOnOcV10 @personalSpace @issue-ocis-reva-14
@skipOnOcV10 @personalSpace
Scenario: send COPY requests to another user's webDav endpoints as normal user using the spaces WebDAV API
When user "Brian" requests these endpoints with "COPY" about user "Alice"
| endpoint |

4
tests/acceptance/features/coreApiAuthWebDav/webDavDELETEAuth.feature
View File

@@ -53,7 +53,7 @@ Feature: delete file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@issue-ocis-reva-13
Scenario: send DELETE requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "DELETE" about user "Alice"
| endpoint |
@@ -62,7 +62,7 @@ Feature: delete file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "404"
@issue-ocis-reva-13 @skipOnOcV10 @personalSpace
@skipOnOcV10 @personalSpace
Scenario: send DELETE requests to another user's webDav endpoints as normal user using the spaces WebDAV API
When user "Brian" requests these endpoints with "DELETE" about user "Alice"
| endpoint |

4
tests/acceptance/features/coreApiAuthWebDav/webDavLOCKAuth.feature
View File

@@ -52,7 +52,7 @@ Feature: LOCK file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@issue-ocis-reva-9
@issue-1347
Scenario: send LOCK requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "LOCK" to get property "d:shared" about user "Alice"
| endpoint |
@@ -64,7 +64,7 @@ Feature: LOCK file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "409"
@issue-ocis-reva-9 @skipOnOcV10 @personalSpace
@issue-1347 @personalSpace
Scenario: send LOCK requests to another user's webDav endpoints as normal user using the spaces WebDAV API
When user "Brian" requests these endpoints with "LOCK" to get property "d:shared" about user "Alice"
| endpoint |

8
tests/acceptance/features/coreApiAuthWebDav/webDavMKCOLAuth.feature
View File

@@ -48,7 +48,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@skipOnOcV10 @issue-ocis-5049 @issue-ocis-reva-9 @issue-ocis-reva-197
@skipOnOcV10 @issue-5049 @issue-1347 @issue-1292
Scenario: send MKCOL requests to another user's webDav endpoints as normal user
Given user "Brian" has been created with default attributes and without skeleton files
When user "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice"
@@ -59,7 +59,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "404"
@skipOnOcV10 @issue-ocis-5049 @issue-ocis-reva-9 @issue-ocis-reva-197
@skipOnOcV10 @issue-5049 @issue-1347 @issue-1292
Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal user
Given user "Brian" has been created with default attributes and without skeleton files
When user "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user"
@@ -70,7 +70,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/files/non-existent-user/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "404"
@skipOnOcV10 @personalSpace @issue-ocis-reva-9 @issue-ocis-reva-197
@personalSpace @issue-1347 @issue-1292
Scenario: send MKCOL requests to another user's webDav endpoints as normal user using the spaces WebDAV API
Given user "Brian" has been created with default attributes and without skeleton files
When user "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice"
@@ -81,7 +81,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "404"
@skipOnOcV10 @issue-ocis-5049 @personalSpace @issue-ocis-reva-9 @issue-ocis-reva-197
@skipOnOcV10 @issue-5049 @personalSpace @issue-1347 @issue-1292
Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal user using the spaces WebDAV API
Given user "Brian" has been created with default attributes and without skeleton files
When user "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user"

4
tests/acceptance/features/coreApiAuthWebDav/webDavMOVEAuth.feature
View File

@@ -51,7 +51,7 @@ Feature: MOVE file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@issue-ocis-reva-14
Scenario: send MOVE requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "MOVE" about user "Alice"
| endpoint |
@@ -60,7 +60,7 @@ Feature: MOVE file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "403"
@skipOnOcV10 @personalSpace @issue-ocis-reva-14
@skipOnOcV10 @personalSpace
Scenario: send MOVE requests to another user's webDav endpoints as normal user using the spaces WebDAV API
When user "Brian" requests these endpoints with "MOVE" about user "Alice"
| endpoint |

4
tests/acceptance/features/coreApiAuthWebDav/webDavPOSTAuth.feature
View File

@@ -52,7 +52,7 @@ Feature: get file info using POST
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@issue-ocis-reva-179
@issue-1287
Scenario: send POST requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "POST" including body "doesnotmatter" about user "Alice"
| endpoint |
@@ -61,7 +61,7 @@ Feature: get file info using POST
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "404"
@skipOnOcV10 @personalSpace @issue-ocis-reva-179
@skipOnOcV10 @personalSpace @issue-1287
Scenario: send POST requests to another user's webDav endpoints as normal user using the spaces WebDAV API
When user "Brian" requests these endpoints with "POST" including body "doesnotmatter" about user "Alice"
| endpoint |

4
tests/acceptance/features/coreApiAuthWebDav/webDavPROPFINDAuth.feature
View File

@@ -51,7 +51,7 @@ Feature: get file info using PROPFIND
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@issue-ocis-reva-9
@issue-1347
Scenario: send PROPFIND requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "PROPFIND" to get property "d:getetag" about user "Alice"
| endpoint |
@@ -60,7 +60,7 @@ Feature: get file info using PROPFIND
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "404"
@skipOnOcV10 @personalSpace @issue-ocis-reva-9
@skipOnOcV10 @personalSpace @issue-1347
Scenario: send PROPFIND requests to another user's webDav endpoints as normal user using the spaces WebDAV API
When user "Brian" requests these endpoints with "PROPFIND" to get property "d:getetag" about user "Alice"
| endpoint |

4
tests/acceptance/features/coreApiAuthWebDav/webDavPROPPATCHAuth.feature
View File

@@ -52,7 +52,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@issue-ocis-reva-9 @issue-ocis-reva-197
@issue-1347 @issue-1292
Scenario: send PROPPATCH requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "PROPPATCH" to set property "favorite" about user "Alice"
| endpoint |
@@ -61,7 +61,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "404"
@issue-ocis-reva-9 @issue-ocis-reva-197 @skipOnOcV10 @personalSpace
@issue-1347 @issue-1292 @skipOnOcV10 @personalSpace
Scenario: send PROPPATCH requests to another user's webDav endpoints as normal user using the spaces WebDAV API
When user "Brian" requests these endpoints with "PROPPATCH" to set property "favorite" about user "Alice"
| endpoint |

6
tests/acceptance/features/coreApiCapabilities/capabilities.feature
View File

@@ -4,7 +4,7 @@ Feature: capabilities
Background:
Given using OCS API version "1"
@smokeTest @issue-ocis-1285
@smokeTest @issue-1285
Scenario: getting default capabilities with admin user
When the administrator retrieves the capabilities using the capabilities API
Then the OCS status code should be "100"
@@ -129,7 +129,7 @@ Feature: capabilities
}
"""
@issue-ocis-1285
@issue-1285
Scenario: getting default_permissions capability with admin user
When the administrator retrieves the capabilities using the capabilities API
Then the OCS status code should be "100"
@@ -168,7 +168,7 @@ Feature: capabilities
}
"""
@issue-ocis-1285
@issue-1285
Scenario: .htaccess is reported as a blacklisted file by default
When the administrator retrieves the capabilities using the capabilities API
Then the OCS status code should be "100"

2
tests/acceptance/features/coreApiCapabilities/capabilitiesWithNormalUser.feature
View File

@@ -7,7 +7,7 @@ Feature: default capabilities for normal user
# adjust this scenario after fixing tagged issues as its just created to show difference
# in the response items in different environment (core & ocis-reva)
@issue-ocis-reva-175 @issue-ocis-reva-176
@issue-1285 @issue-1286
Scenario: getting default capabilities with normal user
When user "Alice" retrieves the capabilities using the capabilities API
Then the OCS status code should be "100"

12
tests/acceptance/features/coreApiFavorites/favorites.feature
View File

@@ -13,7 +13,7 @@ Feature: favorite
And user "Alice" has created folder "/PARENT"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@issue-ocis-reva-276
@issue-1263
Scenario Outline: Favorite a folder
Given using <dav_version> DAV path
When user "Alice" favorites element "/FOLDER" using the WebDAV API
@@ -34,7 +34,7 @@ Feature: favorite
| dav_version |
| spaces |
@issue-ocis-reva-276
@issue-1263
Scenario Outline: Unfavorite a folder
Given using <dav_version> DAV path
And user "Alice" has favorited element "/FOLDER"
@@ -56,7 +56,7 @@ Feature: favorite
| dav_version |
| spaces |
@smokeTest @issue-ocis-reva-276
@smokeTest @issue-1263
Scenario Outline: Favorite a file
Given using <dav_version> DAV path
When user "Alice" favorites element "/textfile0.txt" using the WebDAV API
@@ -77,7 +77,7 @@ Feature: favorite
| dav_version |
| spaces |
@smokeTest @issue-ocis-reva-276
@smokeTest @issue-1263
Scenario Outline: Unfavorite a file
Given using <dav_version> DAV path
And user "Alice" has favorited element "/textfile0.txt"
@@ -147,7 +147,7 @@ Feature: favorite
| dav_version |
| spaces |
@issue-33840 @skipOnOcV10
Scenario Outline: Get favorited elements and limit count of entries
Given using <dav_version> DAV path
And user "Alice" has favorited element "/textfile0.txt"
@@ -172,7 +172,7 @@ Feature: favorite
| dav_version |
| spaces |
@issue-33840 @skipOnOcV10
Scenario Outline: Get favorited elements paginated in subfolder
Given using <dav_version> DAV path
And user "Alice" has created folder "/subfolder"

36
tests/acceptance/features/coreApiMain/checksums.feature
View File

@@ -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

2
tests/acceptance/features/coreApiMain/main.feature
View File

@@ -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"

2
tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature
View File

@@ -10,7 +10,7 @@ Feature: resources shared with the same name are received with unique names
| Brian |
| Carol |
@smokeTest @issue-ocis-2131
@smokeTest @issue-2131
Scenario: unique target names for incoming shares
Given user "Alice" has created folder "/foo"
And user "Brian" has created folder "/foo"

2
tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1327
@api @files_sharing-app-required @issue-1327
Feature: shares are received in the default folder for received shares
Background:

14
tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature
View File

@@ -37,7 +37,7 @@ Feature: share resources where the sharee receives the share in multiple ways
| 1 | 100 | /textfile0 (2).txt |
| 2 | 200 | /textfile0 (2).txt |
@issue-ocis-1289
@issue-1289
Scenario Outline: Share of folder and sub-folder to same user
Given using OCS API version "<ocs_api_version>"
And group "grp4" has been created
@@ -62,7 +62,7 @@ Feature: share resources where the sharee receives the share in multiple ways
| 1 | 100 | /CHILD |
| 2 | 200 | /CHILD |
@issue-ocis-2021
@issue-2021
Scenario Outline: sharing subfolder when parent already shared
Given using OCS API version "<ocs_api_version>"
And group "grp1" has been created
@@ -79,7 +79,7 @@ Feature: share resources where the sharee receives the share in multiple ways
| 1 | 100 | /sub |
| 2 | 200 | /sub |
@issue-ocis-2021
@issue-2021
Scenario Outline: sharing subfolder when parent already shared with group of sharer
Given using OCS API version "<ocs_api_version>"
And group "grp0" has been created
@@ -122,7 +122,7 @@ Feature: share resources where the sharee receives the share in multiple ways
And the content of file "/Shares/randomfile.txt" for user "Alice" should be "First data"
And the content of file "/Shares/randomfile (2).txt" for user "Alice" should be "Second data"
@issue-ocis-2131
@issue-2131
Examples:
| ocs_api_version | file_target_1 | file_target_2 |
| 1 | /randomfile.txt | /randomfile (2).txt |
@@ -157,7 +157,7 @@ Feature: share resources where the sharee receives the share in multiple ways
And as "Alice" folder "/Shares/zzzfolder/Brian" should exist
And as "Alice" folder "/Shares/zzzfolder (2)/Carol" should exist
@issue-ocis-2131
@issue-2131
Examples:
| ocs_api_version | file_target_1 | file_target_2 | ocs_status_code |
| 1 | /zzzfolder | /zzzfolder (2) | 100 |
@@ -398,7 +398,7 @@ Feature: share resources where the sharee receives the share in multiple ways
And user "Brian" should be able to rename file "/Shares/child1/child2/textfile-2.txt" to "/Shares/child1/child2/rename.txt"
And user "Brian" should not be able to rename file "/Shares/parent/child1/child2/rename.txt" to "/Shares/parent/child1/child2/rename2.txt"
And user "Alice" should not be able to rename file "/Shares/parent/child1/child2/rename.txt" to "/Shares/parent/child1/child2/rename2.txt"
@issue-ocis-2440
@issue-2440
Examples:
| path |
| /child1 |
@@ -433,7 +433,7 @@ Feature: share resources where the sharee receives the share in multiple ways
And user "Brian" should be able to delete file "/Shares/child1/child2/textfile-2.txt"
And user "Brian" should not be able to delete folder "/Shares/parent/child1"
And user "Alice" should not be able to delete folder "/Shares/parent/child1"
@issue-ocis-2440
@issue-2440
Examples:
| path |
| /child1 |

6
tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWithDisabledUser.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1328
@api @files_sharing-app-required @issue-1328
Feature: share resources with a disabled user
Background:
@@ -6,7 +6,7 @@ Feature: share resources with a disabled user
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
@issue-ocis-2212
@issue-2212
Scenario Outline: Creating a new share with a disabled user
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -18,7 +18,7 @@ Feature: share resources with a disabled user
| ocs_api_version | ocs_status_code |
| 1 | 997 |
@issue-32068
Scenario: Creating a new share with a disabled user
Given using OCS API version "2"
And user "Brian" has been created with default attributes and without skeleton files

4
tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature
View File

@@ -72,7 +72,7 @@ Feature: cannot share resources with invalid permissions
| 1 | 200 | create,delete |
| 2 | 400 | create,delete |
@issue-ocis-reva-34
Scenario Outline: Cannot create a share of a file with a group with only create permission
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -93,7 +93,7 @@ Feature: cannot share resources with invalid permissions
| 1 | 200 |
| 2 | 400 |
@issue-ocis-reva-34
Scenario Outline: Cannot create a share of a file with a group with only (create,delete) permission
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files

40
tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature
View File

@@ -5,7 +5,7 @@ Feature: sharing
Given auto-accept shares has been disabled
And user "Alice" has been created with default attributes and without skeleton files
@smokeTest @skipOnEncryptionType:user-keys @issue-32322
@smokeTest @skipOnEncryptionType:user-keys
Scenario Outline: Creating a share of a file with a user, the default permissions are read(1)+update(2)+can-share(16)
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -35,7 +35,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@smokeTest @skipOnEncryptionType:user-keys @issue-32322 @issue-ocis-2133
@smokeTest @skipOnEncryptionType:user-keys @issue-2133
Scenario Outline: Creating a share of a file containing commas in the filename, with a user, the default permissions are read(1)+update(2)+can-share(16)
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -64,7 +64,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-2133 @issue-ocis-reva-301 @issue-ocis-reva-302
@issue-2133 @issue-1270 @issue-1271
Scenario Outline: Creating a share of a file with a user and asking for various permission combinations
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -131,7 +131,7 @@ Feature: sharing
| 1 | 200 |
| 2 | 400 |
@issue-ocis-2133
@issue-2133
Scenario Outline: Creating a share of a folder with a user, the default permissions are all permissions(31)
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -156,7 +156,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-34
Scenario Outline: Creating a share of a file with a group, the default permissions are read(1)+update(2)+can-share(16)
Given using OCS API version "<ocs_api_version>"
And group "grp1" has been created
@@ -181,7 +181,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-34
Scenario Outline: Creating a share of a folder with a group, the default permissions are all permissions(31)
Given using OCS API version "<ocs_api_version>"
And group "grp1" has been created
@@ -293,7 +293,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-2201
@issue-2201
Scenario Outline: sharing subfolder of already shared folder, GET result is correct
Given using OCS API version "<ocs_api_version>"
And these users have been created with default attributes and without skeleton files:
@@ -395,7 +395,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-11
Scenario: share with user when username contains capital letters
Given these users have been created without skeleton files:
| username |
@@ -433,7 +433,7 @@ Feature: sharing
| /Shares/randomfile.txt |
And the content of file "/Shares/randomfile.txt" for user "Brian" should be "Random data"
@issue-ocis-reva-34
Scenario Outline: Share of folder to a group with emoji in the name
Given using OCS API version "<ocs_api_version>"
And these users have been created with default attributes and without skeleton files:
@@ -522,13 +522,13 @@ Feature: sharing
And file "/textfile0.txt" should not be included as path in the response
And as "Brian" file "/Shares/textfile0.txt" should not exist
And as "Carol" file "/Shares/textfile0.txt" should not exist
@skipOnOcV10 @issue-ocis-2441
@skipOnOcV10 @issue-2441
Examples:
| ocs_api_version | ocs_status_code | path |
| 1 | 100 | /textfile0.txt |
| 2 | 200 | /textfile0.txt |
@skipOnFilesClassifier @issue-files-classifier-291 @issue-ocis-2146
@skipOnFilesClassifier @issue-files-classifier-291 @issue-2146
Scenario: Share a file by multiple channels and download from sub-folder and direct file share
Given these users have been created with default attributes and without skeleton files:
| username |
@@ -557,7 +557,7 @@ Feature: sharing
And the content of file "/Shares/common/sub/textfile0.txt" for user "Brian" should be "BLABLABLA" plus end-of-line
And the content of file "/common/sub/textfile0.txt" for user "Alice" should be "BLABLABLA" plus end-of-line
@issue-enterprise-3896 @issue-ocis-2201
@issue-enterprise-3896 @issue-2201
Scenario Outline: sharing back to resharer is allowed
Given these users have been created with default attributes and without skeleton files:
| username |
@@ -578,7 +578,7 @@ Feature: sharing
| pending_share_path |
| /userOneFolder |
@issue-enterprise-3896 @issue-ocis-2201
@issue-enterprise-3896 @issue-2201
Scenario Outline: sharing back to original sharer is allowed
Given these users have been created with default attributes and without skeleton files:
| username |
@@ -599,7 +599,7 @@ Feature: sharing
| pending_share_path |
| /userOneFolder |
@issue-enterprise-3896 @issue-ocis-2201
@issue-enterprise-3896 @issue-2201
Scenario Outline: sharing a subfolder to a user that already received parent folder share
Given these users have been created with default attributes and without skeleton files:
| username |
@@ -653,7 +653,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-903
@issue-903
Scenario Outline: shares to a deleted user should not be listed as shares for the sharer
Given using OCS API version "<ocs_api_version>"
And these users have been created with default attributes and without skeleton files:
@@ -676,7 +676,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-719
@issue-719
Scenario Outline: Creating a share of a renamed file when another share exists
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -709,7 +709,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-1710
@issue-1710
Scenario Outline: Sharing a same file twice to the same group is not possible
Given using OCS API version "<ocs-api-version>"
And group "grp1" has been created
@@ -724,7 +724,7 @@ Feature: sharing
| 1 | 200 |
| 2 | 403 |
@issue-ocis-2215
@issue-2215
Scenario Outline: Sharing the shares folder to users is not possible
Given using OCS API version "<ocs-api-version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -741,7 +741,7 @@ Feature: sharing
| 1 | 200 |
| 2 | 403 |
@issue-ocis-2215
@issue-2215
Scenario Outline: Sharing the shares folder to groups is not possible
Given using OCS API version "<ocs-api-version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -760,7 +760,7 @@ Feature: sharing
| 1 | 200 |
| 2 | 403 |
@issue-ocis-2215
@issue-2215
Scenario Outline: Sharing the shares folder as public link is not possible
Given using OCS API version "<ocs-api-version>"
And user "Brian" has been created with default attributes and without skeleton files

6
tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1328 @issue-ocis-1289
@api @files_sharing-app-required @issue-1328 @issue-1289
Feature: sharing
Background:
@@ -197,7 +197,7 @@ Feature: sharing
| /shared | 1 | 200 | /Shares/shared | /Shares/shared |
| /shared | 2 | 404 | /Shares/shared | /Shares/shared |
@issue-ocis-720
@issue-720
Scenario Outline: request PROPFIND after sharer deletes the collaborator
Given using OCS API version "<ocs_api_version>"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
@@ -212,7 +212,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-1229
@issue-1229
Scenario Outline: delete a share with wrong authentication
Given using OCS API version "<ocs_api_version>"
And user "Alice" has shared file "textfile0.txt" with user "Brian"

30
tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-1328
@api @files_sharing-app-required @issue-1289 @issue-1328
Feature: accept/decline shares coming from internal users
As a user
I want to have control of which received shares I accept
@@ -58,7 +58,7 @@ Feature: accept/decline shares coming from internal users
| path |
| <pending_share_path_1> |
| <pending_share_path_2> |
@issue-ocis-2540
@issue-2540
Examples:
| pending_share_path_1 | pending_share_path_2 |
| /Shares/PARENT/ | /Shares/textfile0.txt |
@@ -81,12 +81,12 @@ Feature: accept/decline shares coming from internal users
| path |
| <pending_share_path_1> |
| <pending_share_path_2> |
@issue-ocis-2540
@issue-2540
Examples:
| pending_share_path_1 | pending_share_path_2 |
| /Shares/PARENT/ | /Shares/textfile0.txt |
@smokeTest @issue-ocis-2131
@smokeTest @issue-2131
Scenario: accept a pending share
Given user "Alice" has shared folder "/PARENT" with user "Brian"
And user "Alice" has shared file "/textfile0.txt" with user "Brian"
@@ -159,12 +159,12 @@ Feature: accept/decline shares coming from internal users
| path |
| <declined_share_path_1> |
| <declined_share_path_2> |
@issue-ocis-2540
@issue-2540
Examples:
| declined_share_path_1 | declined_share_path_2 |
| /Shares/PARENT/ | /Shares/textfile0.txt |
@smokeTest @issue-ocis-2128
@smokeTest @issue-2128
Scenario Outline: decline an accepted share
Given user "Alice" has shared folder "/PARENT" with user "Brian"
And user "Alice" has shared file "/textfile0.txt" with user "Brian"
@@ -182,7 +182,7 @@ Feature: accept/decline shares coming from internal users
| path |
| <declined_share_path_1> |
| <declined_share_path_2> |
@issue-ocis-2540
@issue-2540
Examples:
| declined_share_path_1 | declined_share_path_2 |
| /Shares/PARENT/ | /Shares/textfile0.txt |
@@ -220,12 +220,12 @@ Feature: accept/decline shares coming from internal users
| path |
| /Shares/PARENT/ |
| /Shares/textfile0.txt |
@issue-ocis-2540
@issue-2540
Examples:
| pending_share_path_1 | pending_share_path_2 |
| /Shares/PARENT/ | /Shares/textfile0.txt |
@issue-ocis-2131
@issue-2131
Scenario: receive two shares with identical names from different users, accept one by one
Given user "Alice" has created folder "/shared"
And user "Alice" has created folder "/shared/Alice"
@@ -254,7 +254,7 @@ Feature: accept/decline shares coming from internal users
| path |
| <pending_share_path> |
And the sharing API should report that no shares are shared with user "Alice"
@issue-ocis-2540
@issue-2540
Examples:
| pending_share_path |
| /Shares/PARENT/ |
@@ -465,7 +465,7 @@ Feature: accept/decline shares coming from internal users
| /PARENT (2)/ |
And the content of file "/Shares/PARENT/abc.txt" for user "David" should be "uploaded content"
@issue-ocis-1123
@issue-1123
Scenario Outline: deleting a share accepted file and folder
Given user "Alice" has shared folder "/PARENT" with user "Brian"
And user "Brian" has accepted share "/PARENT" offered by user "Alice"
@@ -474,12 +474,12 @@ Feature: accept/decline shares coming from internal users
And the sharing API should report to user "Brian" that these shares are in the declined state
| path |
| <declined_share_path> |
@issue-ocis-2540
@issue-2540
Examples:
| declined_share_path |
| /Shares/PARENT |
@issue-ocis-765 @issue-ocis-2131
@issue-765 @issue-2131
Scenario: shares exist after restoring already shared file to a previous version
And user "Alice" has uploaded file with content "Test Content." to "/toShareFile.txt"
And user "Alice" has uploaded file with content "Content Test Updated." to "/toShareFile.txt"
@@ -490,7 +490,7 @@ Feature: accept/decline shares coming from internal users
And the content of file "/toShareFile.txt" for user "Alice" should be "Test Content."
And the content of file "/Shares/toShareFile.txt" for user "Brian" should be "Test Content."
@issue-ocis-2131
@issue-2131
Scenario: a user receives multiple group shares for matching file and folder name
Given group "grp2" has been created
And user "Alice" has been added to group "grp2"
@@ -555,7 +555,7 @@ Feature: accept/decline shares coming from internal users
And the content of file "/Shares/PARENT (2).txt" for user "Brian" should be "from carol to grp1"
And the content of file "/Shares/parent.txt" for user "Brian" should be "from carol to grp1"
@issue-ocis-2131
@issue-2131
Scenario: a group receives multiple shares from non-member for matching file and folder name
Given user "Brian" has been removed from group "grp1"
And user "Alice" has created folder "/PaRent"

2
tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-reva-1328 @issues-ocis-1289
@api @files_sharing-app-required @issue-1328 @issues-1289
Feature: sharing
Background:

6
tests/acceptance/features/coreApiShareManagementToShares/moveReceivedShare.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-1328
@api @files_sharing-app-required @issue-1289 @issue-1328
Feature: sharing
Background:
@@ -162,7 +162,7 @@ Feature: sharing
And as "Brian" folder "/Shares/myFolder" should exist
But as "Alice" folder "/Shares/myFolder" should not exist
@issue-ocis-2141
@issue-2141
Scenario Outline: receiver renames a received folder share to name with special characters in group sharing
Given group "grp1" has been created
And user "Carol" has been added to group "grp1"
@@ -185,7 +185,7 @@ Feature: sharing
| ?abc=oc # | ?abc=oc g%rp# | # oc?test=oc&a |
| @a#8a=b?c=d | @a#8a=b?c=d grp | ?a#8 a=b?c=d |
@issue-ocis-2141
@issue-2141
Scenario Outline: receiver renames a received file share to name with special characters with share, read, change permissions in group sharing
Given group "grp1" has been created
And user "Carol" has been added to group "grp1"

4
tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature
View File

@@ -40,7 +40,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-ocis-reva-260
@smokeTest @issue-1257
Scenario Outline: Sharee can't see the share that is filtered out
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "some data" to "/textfile1.txt"
@@ -57,7 +57,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-ocis-reva-34 @issue-ocis-reva-194
@smokeTest @issue-1289
Scenario Outline: Sharee can see the group share
Given using OCS API version "<ocs_api_version>"
And group "grp1" has been created

2
tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-1328
@api @files_sharing-app-required @issue-1289 @issue-1328
Feature: sharing
Background:

12
tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature
View File

@@ -8,7 +8,7 @@ Feature: sharing
| Alice |
| Brian |
@smokeTest @issue-ocis-reva-262
@smokeTest @issue-1258
Scenario Outline: getting all shares of a user using that user
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt"
@@ -23,7 +23,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-65
@issue-1319
Scenario Outline: getting all shares of a user using another user
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
@@ -105,7 +105,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-ocis-reva-357 @issue-ocis-reva-301 @issue-ocis-reva-302
@smokeTest @issue-1226 @issue-1270 @issue-1271
Scenario Outline: getting share info of a share
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt"
@@ -136,7 +136,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-374
@issue-1233
Scenario Outline: Get a share with a user that didn't receive the share
Given using OCS API version "<ocs_api_version>"
And user "Carol" has been created with default attributes and without skeleton files
@@ -150,7 +150,7 @@ Feature: sharing
| 1 | 200 |
| 2 | 404 |
@skipOnLDAP @issue-ocis-reva-194 @skipOnGraph
@skipOnLDAP @issue-1289 @skipOnGraph
Scenario: Share of folder to a group, remove user from that group
Given using OCS API version "1"
And user "Carol" has been created with default attributes and without skeleton files
@@ -171,7 +171,7 @@ Feature: sharing
| /Shares/PARENT/ |
| /Shares/PARENT/parent.txt |
@issue-ocis-reva-372
@issue-1231
Scenario Outline: getting all the shares inside the folder
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/PARENT"

8
tests/acceptance/features/coreApiShareOperationsToShares2/getWebDAVSharePermissions.feature
View File

@@ -66,7 +66,7 @@ Feature: sharing
| old |
| new |
@issue-ocis-2213
@issue-2213
Scenario Outline: Correct webdav share-permissions for received file with edit permissions but no reshare permissions
Given using <dav-path> DAV path
And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
@@ -81,7 +81,7 @@ Feature: sharing
| old |
| new |
@issue-ocis-2213
@issue-2213
Scenario Outline: Correct webdav share-permissions for received group shared file with edit permissions but no reshare permissions
Given using <dav-path> DAV path
And group "grp1" has been created
@@ -103,7 +103,7 @@ Feature: sharing
| old |
| new |
@issue-ocis-2213
@issue-2213
Scenario Outline: Correct webdav share-permissions for received file with reshare permissions but no edit permissions
Given using <dav-path> DAV path
And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
@@ -196,7 +196,7 @@ Feature: sharing
| old |
| new |
@issue-ocis-2213
@issue-2213
Scenario Outline: Correct webdav share-permissions for received folder with all permissions but edit
Given using <dav-path> DAV path
And user "Alice" has created folder "/tmp"

2
tests/acceptance/features/coreApiSharePublicLink1/accessToPublicLinkShare.feature
View File

@@ -1,4 +1,4 @@
@api @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-282
@api @public_link_share-feature-required @files_sharing-app-required
Feature: accessing a public link share
Background:

2
tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-315 @issue-ocis-reva-316 @issue-ocis-2079 @issue-ocis-reva-292
@api @files_sharing-app-required @public_link_share-feature-required @issue-1276 @issue-1277 @issue-2079 @issue-1269
Feature: changing a public link share

30
tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-315 @issue-ocis-reva-316
@api @files_sharing-app-required @public_link_share-feature-required @issue-1276 @issue-1277
Feature: create a public link share
@@ -30,13 +30,13 @@ Feature: create a public link share
And the public upload to the last publicly shared file using the old public WebDAV API should fail with HTTP status code "403"
And the public upload to the last publicly shared file using the new public WebDAV API should fail with HTTP status code "403"
@issue-ocis-reva-12 @issue-ocis-2079
@issue-1346 @issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-ocis-reva-199
@smokeTest @issue-1293
Scenario Outline: Creating a new public link share of a file with password using the new public WebDAV API
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
@@ -94,7 +94,7 @@ Feature: create a public link share
And uploading content to a public link shared file should work using the old public WebDAV API
And uploading content to a public link shared file should work using the new public WebDAV API
@issue-ocis-2079 @issue-ocis-reva-292
@issue-2079 @issue-1269
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
@@ -126,7 +126,7 @@ Feature: create a public link share
And the public upload to the last publicly shared folder using the old public WebDAV API should fail with HTTP status code "403"
And the public upload to the last publicly shared folder using the new public WebDAV API should fail with HTTP status code "403"
@issue-ocis-reva-12 @issue-ocis-2079
@issue-1346 @issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
@@ -161,13 +161,13 @@ Feature: create a public link share
And the public should not be able to download file "/randomfile.txt" from inside the last public link shared folder using the old public WebDAV API with password "%regular%"
And the public should not be able to download file "/randomfile.txt" from inside the last public link shared folder using the new public WebDAV API without a password
And the public should not be able to download file "/randomfile.txt" from inside the last public link shared folder using the new public WebDAV API with password "%regular%"
@issue-ocis-2079 @issue-ocis-reva-292
@issue-2079 @issue-1269
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-ocis-reva-294
@smokeTest
Scenario Outline: Getting the share information of public link share from the OCS API does not expose sensitive information
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
@@ -229,7 +229,7 @@ Feature: create a public link share
And the public upload to the last publicly shared folder using the old public WebDAV API should fail with HTTP status code "403"
And the public upload to the last publicly shared folder using the new public WebDAV API should fail with HTTP status code "403"
@issue-ocis-reva-41 @issue-ocis-2079
@issue-1328 @issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
@@ -251,7 +251,7 @@ Feature: create a public link share
And uploading a file should work using the old public WebDAV API
And uploading a file should work using the new public WebDAV API
@issue-ocis-2079
@issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
@@ -273,13 +273,13 @@ Feature: create a public link share
And uploading a file should work using the old public WebDAV API
And uploading a file should work using the new public WebDAV API
@issue-ocis-2079
@issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-283 @issue-ocis-2079
@issue-1265 @issue-2079
Scenario Outline: Allow public sharing of the root on OCIS when the default permission is read and access using the public WebDAV API
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
@@ -306,7 +306,7 @@ Feature: create a public link share
| 1 | 100 |
| 2 | 200 |
@issue-ocis-2079
@issue-2079
Scenario Outline: user creates a public link share of a file with file name longer than 64 chars using the public WebDAV API
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "long file" to "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt"
@@ -322,7 +322,7 @@ Feature: create a public link share
| 1 | 100 |
| 2 | 200 |
@issue-ocis-2079
@issue-2079
Scenario Outline: user creates a public link share of a folder with folder name longer than 64 chars and access using the public WebDAV API
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog"
@@ -339,7 +339,7 @@ Feature: create a public link share
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-199
@issue-1293
Scenario: Delete a folder that has been publicly shared and try to access using the public WebDAV API
Given user "Alice" has created folder "PARENT"
And user "Alice" has uploaded file with content "Random data" to "/PARENT/parent.txt"
@@ -349,7 +349,7 @@ Feature: create a public link share
When user "Alice" deletes folder "/PARENT" using the WebDAV API
Then the public download of file "/parent.txt" from inside the last public link shared folder using the new public WebDAV API should fail with HTTP status code "404"
@issue-ocis-reva-292 @issue-ocis-reva-199
@issue-1269 @issue-1293
Scenario: try to download from a public share that has upload only permissions using the public webdav api
Given user "Alice" has created folder "PARENT"
And user "Alice" has uploaded file with content "Random data" to "/PARENT/parent.txt"

2
tests/acceptance/features/coreApiSharePublicLink1/deletePublicLinkShare.feature
View File

@@ -20,7 +20,7 @@ Feature: delete a public link share
| 1 | 100 |
| 2 | 200 |
@issue-product-60 @issue-ocis-reva-311
@issue-product-60 @issue-1275
Scenario Outline: Deleting a public link after renaming a file
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "This is a test file" to "test-file.txt"

10
tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-310
@api @files_sharing-app-required @public_link_share-feature-required
Feature: copying from public link share
Background:
@@ -59,7 +59,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-ocis-reva-373
@issue-1232
Scenario: Copy folder within a public link folder to the same folder name as an already 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"
@@ -85,7 +85,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-ocis-reva-373
@issue-1232
Scenario: Copy file within a public link folder to a file with name same as an 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"
@@ -158,7 +158,7 @@ Feature: copying from public link share
| C++ file.cpp |
| sample,1.txt |
@issue-ocis-reva-368
@issue-1230
Scenario Outline: Copy file within a public link folder to a file with unusual destination names
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
And user "Alice" has created a public link share with settings
@@ -173,7 +173,7 @@ Feature: copying from public link share
| testfile.txt |
| |
@issue-ocis-reva-368
@issue-1230
Scenario Outline: Copy folder within a public link folder to a folder with unusual destination names
Given user "Alice" has created folder "/PARENT/testFolder"
And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"

4
tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature
View File

@@ -1,4 +1,4 @@
@api @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-288 @issue-ocis-reva-252
@api @public_link_share-feature-required @files_sharing-app-required
Feature: multilinksharing
Background:
@@ -209,7 +209,7 @@ Feature: multilinksharing
| dav-path |
| spaces |
@issue-ocis-reva-335
@issue-1251
Scenario Outline: Renaming a folder doesn't remove its public shares
Given using OCS API version "1"
And using <dav-path> DAV path

26
tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-252
@api @files_sharing-app-required @public_link_share-feature-required
Feature: update a public link share
Background:
@@ -45,7 +45,7 @@ Feature: update a public link share
| 1 | 100 |
| 2 | 200 |
@smokeTest @issue-ocis-reva-336
@smokeTest
Scenario Outline: Creating a new public link share, updating its expiration date and getting its info
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "FOLDER"
@@ -92,7 +92,7 @@ Feature: update a public link share
And the public should be able to download the last publicly shared file using the old public WebDAV API with password "%public%" and the content should be "Random data"
And the public should be able to download the last publicly shared file using the new public WebDAV API with password "%public%" and the content should be "Random data"
@issue-ocis-2079
@issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
@@ -113,13 +113,13 @@ Feature: update a public link share
And the public should be able to download the last publicly shared file using the old public WebDAV API without a password and the content should be "Random data"
And the public should be able to download the last publicly shared file using the new public WebDAV API without a password and the content should be "Random data"
@issue-ocis-2079
@issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-336
Scenario Outline: Creating a new public link share, updating its password and getting its info
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "FOLDER"
@@ -151,7 +151,7 @@ Feature: update a public link share
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-336
Scenario Outline: Creating a new public link share, updating its permissions and getting its info
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "FOLDER"
@@ -183,7 +183,7 @@ Feature: update a public link share
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-336
Scenario Outline: Creating a new public link share, updating its permissions to view download and upload and getting its info
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "FOLDER"
@@ -215,7 +215,7 @@ Feature: update a public link share
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-336
Scenario Outline: Creating a new public link share, updating publicUpload option and getting its info
Given using OCS API version "<ocs_api_version>"
And user "Alice" has created folder "FOLDER"
@@ -265,7 +265,7 @@ Feature: update a public link share
And uploading a file should not work using the old public WebDAV API
And uploading a file should not work using the new public WebDAV API
@issue-ocis-2079
@issue-2079
Examples:
| ocs_api_version | http_status_code |
| 1 | 200 |
@@ -289,7 +289,7 @@ Feature: update a public link share
And uploading a file should work using the old public WebDAV API
And uploading a file should work using the new public WebDAV API
@issue-ocis-2079
@issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
@@ -313,7 +313,7 @@ Feature: update a public link share
And uploading a file should not work using the old public WebDAV API
And uploading a file should not work using the new public WebDAV API
@issue-ocis-2079
@issue-2079
Examples:
| ocs_api_version | http_status_code |
| 1 | 200 |
@@ -337,7 +337,7 @@ Feature: update a public link share
And uploading a file should work using the old public WebDAV API
And uploading a file should work using the new public WebDAV API
@issue-ocis-2079
@issue-2079
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
@@ -359,7 +359,7 @@ Feature: update a public link share
And the HTTP status code of responses on all endpoints should be "403"
And as "Alice" file "PARENT/CHILD/child.txt" should exist
@issue-ocis-2079 @issue-ocis-reva-292
@issue-2079 @issue-1269
Examples:
| ocs_api_version |
| 1 |

16
tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-315 @issue-ocis-reva-316 @issue-ocis-2079
@api @files_sharing-app-required @public_link_share-feature-required @issue-1276 @issue-1277 @issue-2079
Feature: upload to a public link share
@@ -6,7 +6,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"
@smokeTest @issue-ocis-reva-286
@smokeTest @issue-1267
Scenario: Uploading same file to a public upload-only share multiple times via new API
# The new API does the autorename automatically in upload-only folders
Given user "Alice" has created a public link share with settings
@@ -30,7 +30,7 @@ Feature: upload to a public link share
When the public uploads file "test.txt" with content "test" using the new public WebDAV API
And the HTTP status code should be "404"
@issue-ocis-reva-290
@issue-1268
Examples:
| dav-path |
| old |
@@ -41,7 +41,7 @@ Feature: upload to a public link share
| dav-path |
| spaces |
@issue-reva-292
@issue-1269
Scenario: Uploading file to a public read-only share folder with public API does not work
Given user "Alice" has created a public link share with settings
| path | FOLDER |
@@ -89,7 +89,7 @@ Feature: upload to a public link share
When the public uploads file "test.txt" with content "test-file" using the new public WebDAV API
Then the HTTP status code should be "507"
@issue-reva-195
@issue-1290
Scenario: Uploading file to a public shared folder with upload-only permission when the sharer has insufficient quota does not work with public API
When user "Alice" creates a public link share using the sharing API with settings
| path | FOLDER |
@@ -98,7 +98,7 @@ Feature: upload to a public link share
When the public uploads file "test.txt" with content "test-file" using the new public WebDAV API
Then the HTTP status code should be "507"
@issue-reva-41
@issue-1328
Scenario: Uploading file to a public shared folder does not work when allow public uploads has been disabled before sharing and again enabled after sharing the folder with public API
Given parameter "shareapi_allow_public_upload" of app "core" has been set to "no"
And user "Alice" has created a public link share with settings
@@ -107,7 +107,7 @@ Feature: upload to a public link share
When the public uploads file "test.txt" with content "test-file" using the new public WebDAV API
And the HTTP status code should be "403"
@issue-reva-41
@issue-1328
Scenario: Uploading file to a public shared folder works when allow public uploads has been disabled and again enabled after sharing the folder with public API
Given user "Alice" has created a public link share with settings
| path | FOLDER |
@@ -127,7 +127,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"
@smokeTest @issue-reva-286
@smokeTest @issue-1267
Scenario: Uploading same file to a public upload-write and no edit and no overwrite share multiple times with new public API
Given user "Alice" has created a public link share with settings
| path | FOLDER |

2
tests/acceptance/features/coreApiShareReshareToShares1/reShare.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1328
@api @files_sharing-app-required @issue-1328
Feature: sharing
Background:

2
tests/acceptance/features/coreApiShareReshareToShares2/reShareChain.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-2141
@api @files_sharing-app-required @issue-2141
Feature: resharing can be done on a reshared resource
Background:

2
tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1328
@api @files_sharing-app-required @issue-1328
Feature: resharing can be disabled
Background:

10
tests/acceptance/features/coreApiShareReshareToShares2/reShareSubfolder.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1328
@api @files_sharing-app-required @issue-1328
Feature: a subfolder of a received share can be reshared
Background:
@@ -8,7 +8,7 @@ Feature: a subfolder of a received share can be reshared
| Alice |
| Brian |
@smokeTest @issue-ocis-2214
@smokeTest @issue-2214
Scenario Outline: User is allowed to reshare a sub-folder with the same permissions
Given using OCS API version "<ocs_api_version>"
And user "Carol" has been created with default attributes and without skeleton files
@@ -84,7 +84,7 @@ Feature: a subfolder of a received share can be reshared
| 1 | 200 | 23 | 15 |
| 2 | 404 | 23 | 15 |
@issue-ocis-2214
@issue-2214
Scenario Outline: User is allowed to update reshare of a sub-folder with less permissions
Given using OCS API version "<ocs_api_version>"
And user "Carol" has been created with default attributes and without skeleton files
@@ -107,7 +107,7 @@ Feature: a subfolder of a received share can be reshared
| 1 | 100 | /SUB |
| 2 | 200 | /SUB |
@issue-ocis-2214
@issue-2214
Scenario Outline: User is allowed to update reshare of a sub-folder to the maximum allowed permissions
Given using OCS API version "<ocs_api_version>"
And user "Carol" has been created with default attributes and without skeleton files
@@ -130,7 +130,7 @@ Feature: a subfolder of a received share can be reshared
| 1 | 100 | /SUB |
| 2 | 200 | /SUB |
@issue-ocis-2214
@issue-2214
Scenario Outline: User is not allowed to update reshare of a sub-folder with more permissions
Given using OCS API version "<ocs_api_version>"
And user "Carol" has been created with default attributes and without skeleton files

2
tests/acceptance/features/coreApiShareReshareToShares3/reShareUpdate.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1328
@api @files_sharing-app-required @issue-1328
Feature: sharing
Background:

14
tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1328
@api @files_sharing-app-required @issue-1328
Feature: resharing a resource with an expiration date
Background:
@@ -33,7 +33,7 @@ Feature: resharing a resource with an expiration date
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-194
@issue-1289
Scenario Outline: User should be able to set expiration while resharing a file with group
Given using OCS API version "<ocs_api_version>"
And user "Carol" has been created with default attributes and without skeleton files
@@ -87,7 +87,7 @@ Feature: resharing a resource with an expiration date
| 1 | no | | 100 |
| 2 | no | | 200 |
@issue-ocis-reva-194
@issue-1289
Scenario Outline: resharing with group using the sharing API with expire days set and combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "<default-expire-date>"
@@ -144,7 +144,7 @@ Feature: resharing a resource with an expiration date
| 1 | no | | 100 |
| 2 | no | | 200 |
@issue-ocis-reva-194
@issue-1289
Scenario Outline: resharing with group using the sharing API without expire days set and with combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "<default-expire-date>"
@@ -202,7 +202,7 @@ Feature: resharing a resource with an expiration date
| 1 | no | 100 |
| 2 | no | 200 |
@issue-ocis-reva-194
@issue-1289
Scenario Outline: resharing with group using the sharing API with expire days set and with combinations of default/enforce expire date enabled and specify expire date in share
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "<default-expire-date>"
@@ -258,7 +258,7 @@ Feature: resharing a resource with an expiration date
| 1 | no | 100 |
| 2 | no | 200 |
@issue-ocis-reva-194
@issue-1289
Scenario Outline: resharing group share with user using the sharing API with default expire date set and with combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
@@ -288,7 +288,7 @@ Feature: resharing a resource with an expiration date
| 1 | no | | 100 |
| 2 | no | | 200 |
@issue-ocis-reva-194
@issue-1289
Scenario Outline: resharing group share with user using the sharing API with default expire date set and specifying expiration on share and with combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"

10
tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature
View File

@@ -29,7 +29,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-1289
@issue-1289
Scenario Outline: keep group permissions in sync when the share is renamed by the receiver and then the permissions are updated by sharer
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -77,7 +77,7 @@ Feature: sharing
| 1 | 200 |
| 2 | 400 |
@issue-ocis-2173
@issue-2173
Scenario Outline: Cannot update a share of a file with a user to have only create and/or delete permission
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -99,7 +99,7 @@ Feature: sharing
| 1 | 200 | create,delete |
| 2 | 400 | create,delete |
@issue-ocis-2173
@issue-2173
Scenario Outline: Cannot update a share of a file with a group to have only create and/or delete permission
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
@@ -123,7 +123,7 @@ Feature: sharing
| 1 | 200 | create,delete |
| 2 | 400 | create,delete |
@skipOnFilesClassifier @issue-files-classifier-291 @toFixOnOCIS @issue-ocis-2201
@skipOnFilesClassifier @issue-files-classifier-291 @toFixOnOCIS @issue-2201
Scenario Outline: Share ownership change after moving a shared file outside of an outer share
Given these users have been created with default attributes and without skeleton files:
| username |
@@ -194,7 +194,7 @@ Feature: sharing
| path |
| /Carol-folder |
@toFixOnOCIS @toFixOnOcV10 @issue-ocis-reva-349 @issue-ocis-reva-350 @issue-ocis-reva-352 @issue-37653
@toFixOnOCIS @toFixOnOcV10 @issue-1253 @issue-1224 @issue-1225
#after fixing all the issues merge this scenario with the one below
Scenario Outline: API responds with a full set of parameters when owner changes the permission of a share
Given using OCS API version "<ocs_api_version>"

2
tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-1328
@api @files_sharing-app-required @issue-1289 @issue-1328
Feature: updating shares to users and groups that have the same name
Background:

2
tests/acceptance/features/coreApiSharees/sharees.feature
View File

@@ -1,4 +1,4 @@
@api @files_sharing-app-required @issue-ocis-reva-34
@api @files_sharing-app-required
Feature: sharees
Background:

2
tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature
View File

@@ -1,4 +1,4 @@
@api @files_trashbin-app-required @issue-ocis-reva-52
@api @files_trashbin-app-required @issue-1324
Feature: files and folders can be deleted from the trashbin
As a user
I want to delete files and folders from the trashbin

18
tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature
View File

@@ -1,4 +1,4 @@
@api @files_trashbin-app-required @issue-ocis-reva-52
@api @files_trashbin-app-required @issue-1324
Feature: files and folders exist in the trashbin after being deleted
As a user
I want deleted files and folders to be available in the trashbin
@@ -175,7 +175,7 @@ Feature: files and folders exist in the trashbin after being deleted
| dav-path |
| spaces |
@issue-ocis-3561 @skipOnLDAP @skip_on_objectstore
@issue-3561 @skipOnLDAP @skip_on_objectstore
Scenario Outline: Listing other user's trashbin is prohibited
Given using <dav-path> DAV path
And user "testtrashbin100" has been created with default attributes and without skeleton files
@@ -193,7 +193,7 @@ Feature: files and folders exist in the trashbin after being deleted
| new | 404 |
| spaces | 404 |
@issue-ocis-3561 @smokeTest @skipOnLDAP @skip_on_objectstore
@issue-3561 @smokeTest @skipOnLDAP @skip_on_objectstore
Scenario Outline: Listing other user's trashbin is prohibited with multiple files on trashbin
Given using <dav-path> DAV path
And user "testtrashbin101" has been created with default attributes and without skeleton files
@@ -214,7 +214,7 @@ Feature: files and folders exist in the trashbin after being deleted
| new | 404 |
| spaces | 404 |
@issue-ocis-3561 @skipOnLDAP @skip_on_objectstore @provisioning_api-app-required
@issue-3561 @skipOnLDAP @skip_on_objectstore @provisioning_api-app-required
Scenario Outline: Listing other user's trashbin is prohibited for newly recreated user with same name
Given using <dav-path> DAV path
And user "testtrashbin102" has been created with default attributes and without skeleton files
@@ -240,7 +240,7 @@ Feature: files and folders exist in the trashbin after being deleted
| new | 404 |
| spaces | 404 |
@issue-ocis-3561 @skipOnLDAP @skip_on_objectstore
@issue-3561 @skipOnLDAP @skip_on_objectstore
Scenario Outline: Listing other user's empty unused trashbin is prohibited
Given using <dav-path> DAV path
And user "testtrashbinempty" has been created with default attributes and without skeleton files
@@ -253,7 +253,7 @@ Feature: files and folders exist in the trashbin after being deleted
| new | 404 |
| spaces | 404 |
@issue-ocis-3561 @skipOnLDAP @skip_on_objectstore
@issue-3561 @skipOnLDAP @skip_on_objectstore
Scenario Outline: Listing non-existent user's trashbin is prohibited
Given using <dav-path> DAV path
When user "Alice" tries to list the trashbin content for user "testtrashbinnotauser"
@@ -370,7 +370,7 @@ Feature: files and folders exist in the trashbin after being deleted
| dav-path |
| spaces |
@issue-ocis-541
@issue-541
Scenario Outline: deleted file has appropriate deletion time information
Given using <dav-path> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2018 04:18:13 GMT" using the WebDAV API
@@ -387,7 +387,7 @@ Feature: files and folders exist in the trashbin after being deleted
| dav-path |
| spaces |
@issue-ocis-1547
@issue-1547
Scenario Outline: deleting files with special characters moves it to trashbin
Given using <dav-path> DAV path
And user "Alice" has uploaded the following files with content "special character file"
@@ -424,7 +424,7 @@ Feature: files and folders exist in the trashbin after being deleted
| dav-path |
| spaces |
@issue-ocis-1547
@issue-1547
Scenario Outline: deleting folders with special characters moves it to trashbin
Given using <dav-path> DAV path
And user "Alice" has created the following folders

2
tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature
View File

@@ -1,4 +1,4 @@
@api @files_trashbin-app-required @issue-ocis-reva-52
@api @files_trashbin-app-required @issue-1324
Feature: Restore deleted files/folders
As a user
I would like to restore files/folders

20
tests/acceptance/features/coreApiVersions/fileVersions.feature
View File

@@ -1,4 +1,4 @@
@api @files_versions-app-required @issue-ocis-reva-275
@api @files_versions-app-required @issue-1262
Feature: dav-versions
@@ -13,7 +13,7 @@ Feature: dav-versions
Then the HTTP status code should be "201"
And the version folder of file "/davtest.txt" for user "Alice" should contain "0" elements
@issue-ocis-reva-17 @issue-ocis-reva-56
@issue-1343 @issue-1321
Scenario: Upload file and no version is available using various chunking methods (except new chunking)
When user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms except new chunking using the WebDAV API
Then the HTTP status code should be "200"
@@ -29,7 +29,7 @@ Feature: dav-versions
And the version folder of file "/davtest.txt" for user "Alice" should contain "1" element
And the content length of file "/davtest.txt" with version index "1" for user "Alice" in versions folder should be "8"
@issue-ocis-reva-17 @issue-ocis-reva-56
@issue-1343 @issue-1321
Scenario: Upload a file twice and versions are available using various chunking methods (except new chunking)
When user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms except new chunking using the WebDAV API
And user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms except new chunking using the WebDAV API
@@ -66,7 +66,7 @@ Feature: dav-versions
Then the HTTP status code should be "204"
And the content of file "/davtest.txt" for user "Alice" should be "Back To The Future."
@smokeTest @skipOnStorage:ceph @files_primary_s3-issue-161 @issue-ocis-reva-17 @issue-ocis-reva-56
@smokeTest @skipOnStorage:ceph @files_primary_s3-issue-161 @issue-1343 @issue-1321
Scenario Outline: Uploading a chunked file does create the correct version that can be restored
Given using <dav-path> DAV path
And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt"
@@ -127,7 +127,7 @@ Feature: dav-versions
Then the HTTP status code should be "204"
And the content of file "/renamedfile.txt" for user "Alice" should be "old content"
@issue-ocis-1238
@issue-1238
Scenario: User can access version number after moving a file
Given user "Alice" has created folder "testFolder"
And user "Alice" has uploaded file with content "uploaded content" to "textfile0.txt"
@@ -146,7 +146,7 @@ Feature: dav-versions
Then the HTTP status code should be "207"
And the number of versions should be "0"
@issue-ocis-1234
@issue-1234
Scenario: the number of etag elements in response changes according to version of the file
Given user "Alice" has uploaded file with content "uploaded content" to "textfile0.txt"
And user "Alice" has uploaded file with content "version 1" to "textfile0.txt"
@@ -388,7 +388,7 @@ Feature: dav-versions
And the content of file "/sharingfolder/sharefile.txt" for user "Alice" should be "old content"
And the content of file "/Shares/sharingfolder/sharefile.txt" for user "Brian" should be "old content"
@files_sharing-app-required @issue-ocis-reva-34
@files_sharing-app-required
Scenario: sharer can restore a file inside a group shared folder modified by sharee
Given user "Brian" has been created with default attributes and without skeleton files
And user "Carol" has been created with default attributes and without skeleton files
@@ -408,7 +408,7 @@ Feature: dav-versions
And the content of file "/Shares/sharingfolder/sharefile.txt" for user "Brian" should be "First content"
And the content of file "/Shares/sharingfolder/sharefile.txt" for user "Carol" should be "First content"
@files_sharing-app-required @issue-ocis-reva-386
@files_sharing-app-required @issue-1238
Scenario Outline: Moving a file (with versions) into a shared folder as the sharee and as the sharer
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -434,7 +434,7 @@ Feature: dav-versions
| old | Brian | /testshare |
| new | Brian | /testshare |
@files_sharing-app-required @issue-ocis-reva-386
@files_sharing-app-required @issue-1238
Scenario Outline: Moving a file (with versions) out of a shared folder as the sharee and as the sharer
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -525,4 +525,4 @@ Feature: dav-versions
And the following headers should be set
| header | value |
| Content-Disposition | attachment; filename*=UTF-8''textfile0.txt; filename="textfile0.txt" |
And the downloaded content should be "uploaded content"
And the downloaded content should be "uploaded content"

4
tests/acceptance/features/coreApiWebdavDelete/deleteFolder.feature
View File

@@ -24,7 +24,7 @@ Feature: delete folder
| dav_version |
| spaces |
@issue-ocis-reva-269
Scenario Outline: delete a folder when 2 folder exist with different case
Given using <dav_version> DAV path
And user "Alice" has created folder "/parent"
@@ -42,7 +42,7 @@ Feature: delete folder
| dav_version |
| spaces |
@issue-ocis-reva-269
Scenario Outline: delete a sub-folder
Given using <dav_version> DAV path
And user "Alice" has created folder "/PARENT/CHILD"

4
tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature
View File

@@ -107,7 +107,7 @@ Feature: propagation of etags when copying files or folders
And these etags should not have changed:
| user | path |
| Alice | /upload/file.txt |
@issue-ocis-4091
@issue-4091
Examples:
| dav_version |
| old |
@@ -140,7 +140,7 @@ Feature: propagation of etags when copying files or folders
And these etags should not have changed:
| user | path |
| Alice | /upload/file.txt |
@issue-ocis-4091
@issue-4091
Examples:
| dav_version |
| old |

2
tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-172
@api @issue-1284
Feature: there can be only one exclusive lock on a resource
Background:

2
tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-172
@api @issue-1284
Feature: actions on a locked item are possible if the token is sent with the request
Background:

2
tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-172
@api @issue-1284
Feature: independent locks
Make sure all locks are independent and don't interact with other items that have the same name

2
tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-172
@api @issue-1284
Feature: independent locks
Make sure all locks are independent and don't interact with other items that have the same name

2
tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-172
@api @issue-1284
Feature: UNLOCK locked items
Background:

2
tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-172 @files_sharing-app-required
@api @issue-1284 @files_sharing-app-required
Feature: UNLOCK locked items (sharing)
Background:

4
tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-14
@api
Feature: move (rename) folder
As a user
I want to be able to move and rename folders
@@ -131,7 +131,7 @@ Feature: move (rename) folder
| spaces | /... |
| spaces | /..upload |
@issue-ocis-3023
@issue-3023
Scenario Outline: Moving a folder into a sub-folder of itself
Given using <dav_version> DAV path
And user "Alice" has created folder "PARENT"

2
tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-14
@api
Feature: users cannot move (rename) a folder to a blacklisted name
As an administrator
I want to be able to prevent users from moving (renaming) folders to specified names

6
tests/acceptance/features/coreApiWebdavMove2/moveFile.feature
View File

@@ -121,7 +121,7 @@ Feature: move (rename) file
| dav_version |
| spaces |
@issue-ocis-reva-211
@issue-1295
Scenario Outline: rename a file into an invalid filename
Given using <dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToRename.txt"
@@ -158,7 +158,7 @@ Feature: move (rename) file
| dav_version |
| spaces |
@issue-ocis-reva-211
@issue-1295
Scenario Outline: Renaming a file to a path with extension .part should not be possible
Given using <dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToRename.txt"
@@ -209,7 +209,7 @@ Feature: move (rename) file
| dav_version |
| spaces |
@issue-ocis-reva-265
@issue-1259
#after fixing the issues merge this Scenario into the one above
Scenario Outline: renaming to a file with question mark in its name
Given using <dav_version> DAV path

2
tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature
View File

@@ -9,7 +9,7 @@ Feature: users cannot move (rename) a file to a blacklisted name
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
@issue-ocis-reva-211
@issue-1295
Scenario Outline: rename a file to a filename that is banned by default
Given using <dav_version> DAV path
When user "Alice" moves file "/textfile0.txt" to "/.htaccess" using the WebDAV API

6
tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature
View File

@@ -25,7 +25,7 @@ Feature: download file
| dav_version |
| spaces |
@issue-ocis-reva-12
@issue-1346
Scenario Outline: download a file with range
Given using <dav_version> DAV path
When user "Alice" downloads file "/welcome.txt" with range "bytes=24-50" using the WebDAV API
@@ -77,7 +77,7 @@ Feature: download file
| dav_version |
| spaces |
@issue-ocis-reva-98
@issue-1316
Scenario Outline: Get the content-length response header of a pdf file
Given using <dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/simple.pdf" to "/simple.pdf"
@@ -96,7 +96,7 @@ Feature: download file
| dav_version |
| spaces |
@issue-ocis-reva-98
@issue-1316
Scenario Outline: Get the content-length response header of an image file
Given using <dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/testavatar.png" to "/testavatar.png"

2
tests/acceptance/features/coreApiWebdavOperations/propfind.feature
View File

@@ -1,7 +1,7 @@
@api
Feature: PROPFIND
@issue-ocis-751
@issue-751
Scenario Outline: PROPFIND to "/remote.php/dav/(files|spaces)"
Given user "Alice" has been created with default attributes and without skeleton files
When user "Alice" requests "<dav_path>" with "PROPFIND" using basic auth

6
tests/acceptance/features/coreApiWebdavOperations/search.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-39
@api @issue-1330
Feature: Search
As a user
I would like to be able to search for files
@@ -180,7 +180,7 @@ Feature: Search
| dav_version |
| spaces |
@issue-ocis-4712
@issue-4712
Scenario Outline: report extra properties in search entries for a file
Given using <dav_version> DAV path
When user "Alice" searches for "upload" using the WebDAV API requesting these properties:
@@ -213,7 +213,7 @@ Feature: Search
| dav_version |
| spaces |
@issue-ocis-4712
@issue-4712
Scenario Outline: report extra properties in search entries for a folder
Given using <dav_version> DAV path
When user "Alice" searches for "upload" using the WebDAV API requesting these properties:

2
tests/acceptance/features/coreApiWebdavPreviews/previews.feature
View File

@@ -120,7 +120,7 @@ Feature: previews of files downloaded through the webdav API
Then the HTTP status code should be "204"
And as user "Alice" the preview of "/parent.txt" with width "32" and height "32" should have been changed
@issue-ocis-2538
@issue-2538
Scenario: when owner updates a shared file, previews for sharee are also updated (to shared folder)
Given auto-accept shares has been disabled
And user "Brian" has been created with default attributes and without skeleton files

44
tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature
View File

@@ -62,7 +62,7 @@ Feature: copy file
| dav_version |
| spaces |
@files_sharing-app-required @issue-ocis-reva-11
@files_sharing-app-required
Scenario Outline: Copying a file to a folder with no permissions
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -81,7 +81,7 @@ Feature: copy file
| old |
| new |
@files_sharing-app-required @issue-ocis-reva-11
@files_sharing-app-required
Scenario Outline: Copying a file to overwrite a file into a folder with no permissions
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -102,7 +102,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-reva-15
@issue-1345
Scenario Outline: Copying file to a path with extension .part should not be possible
Given using <dav_version> DAV path
When user "Alice" copies file "/textfile1.txt" to "/textfile1.part" using the WebDAV API
@@ -124,7 +124,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-reva-387
@issue-1239
Scenario Outline: copy a file over the top of an existing folder
Given using <dav_version> DAV path
And user "Alice" has created folder "FOLDER/sample-folder"
@@ -143,7 +143,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-reva-387
@issue-1239
Scenario Outline: copy a folder over the top of an existing file
Given using <dav_version> DAV path
And user "Alice" has created folder "FOLDER/sample-folder"
@@ -161,7 +161,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-reva-387
@issue-1239
Scenario Outline: copy a folder into another folder at different level
Given using <dav_version> DAV path
And user "Alice" has created folder "FOLDER/second-level-folder"
@@ -183,7 +183,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-reva-387
@issue-1239
Scenario Outline: copy a file into a folder at different level
Given using <dav_version> DAV path
And user "Alice" has created folder "FOLDER/second-level-folder"
@@ -207,7 +207,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-reva-387
@issue-1239
Scenario Outline: copy a file into a file at different level
Given using <dav_version> DAV path
And user "Alice" has uploaded file with content "file at second level" to "FOLDER/second-level-file.txt"
@@ -230,7 +230,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-reva-387
@issue-1239
Scenario Outline: copy a folder into a file at different level
Given using <dav_version> DAV path
And user "Alice" has created folder "FOLDER/second-level-folder"
@@ -254,7 +254,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a file over the top of an existing folder received as a user share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -273,7 +273,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a folder over the top of an existing file received as a user share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -291,7 +291,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a folder into another folder at different level which is received as a user share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -314,7 +314,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a file into a folder at different level received as a user share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -339,7 +339,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a file into a file at different level received as a user share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -363,7 +363,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a folder into a file at different level received as a user share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -387,7 +387,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a file over the top of an existing folder received as a group share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -414,7 +414,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a folder over the top of an existing file received as a group share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -440,7 +440,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a folder into another folder at different level which is received as a group share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -466,7 +466,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a file into a folder at different level received as a group share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -494,7 +494,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a file into a file at different level received as a group share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -521,7 +521,7 @@ Feature: copy file
| old |
| new |
@issue-ocis-1239
@issue-1239
Scenario Outline: copy a folder into a file at different level received as a group share
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -843,7 +843,7 @@ Feature: copy file
| dav_version |
| spaces |
@issue-ocis-3023
@issue-3023
Scenario Outline: Copying a folder into a sub-folder of itself
Given using <dav_version> DAV path
And user "Alice" has created folder "/PARENT"

10
tests/acceptance/features/coreApiWebdavProperties1/createFileFolder.feature
View File

@@ -8,7 +8,7 @@ Feature: create files and folder
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@issue-ocis-reva-269
Scenario Outline: create a folder
Given using <dav_version> DAV path
When user "Alice" creates folder "<folder_name>" using the WebDAV API
@@ -83,7 +83,7 @@ Feature: create files and folder
| dav_version |
| spaces |
@issue-ocis-reva-15
@issue-1345
Scenario Outline: Creating a directory which contains .part should not be possible
Given using <dav_version> DAV path
When user "Alice" creates folder "/folder.with.ext.part" using the WebDAV API
@@ -103,7 +103,7 @@ Feature: create files and folder
| dav_version |
| spaces |
@issue-ocis-reva-168
@issue-1283
Scenario Outline: try to create a folder that already exists
Given using <dav_version> DAV path
And user "Alice" has created folder "my-data"
@@ -122,7 +122,7 @@ Feature: create files and folder
| dav_version |
| spaces |
@issue-ocis-reva-168
@issue-1283
Scenario Outline: try to create a folder with a name of an existing file
Given using <dav_version> DAV path
And user "Alice" has uploaded file with content "uploaded data" to "/my-data.txt"
@@ -177,4 +177,4 @@ Feature: create files and folder
| spaces | /file #2.txt |
| spaces | /file ?2.pdf |
| spaces | /😀 🤖.txt |
| spaces | /new&file.txt |
| spaces | /new&file.txt |

2
tests/acceptance/features/coreApiWebdavProperties1/getQuota.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-101 @skipOnGraph
@api @issue-1313 @skipOnGraph
Feature: get quota
As a user
I want to be able to find out my available storage quota

10
tests/acceptance/features/coreApiWebdavProperties1/setFileProperties.feature
View File

@@ -8,7 +8,7 @@ Feature: set file properties
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@smokeTest @issue-ocis-reva-276
@smokeTest @issue-1263
Scenario Outline: Setting custom DAV property and reading it
Given using <dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustomprop.txt"
@@ -25,7 +25,7 @@ Feature: set file properties
| dav_version |
| spaces |
@issue-ocis-reva-217
@issue-1297
Scenario Outline: Setting custom complex DAV property and reading it
Given using <dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustomprop.txt"
@@ -42,7 +42,7 @@ Feature: set file properties
| dav_version |
| spaces |
@issue-ocis-reva-276
@issue-1263
Scenario Outline: Setting custom DAV property and reading it after the file is renamed
Given using <dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustompropwithmove.txt"
@@ -60,7 +60,7 @@ Feature: set file properties
| dav_version |
| spaces |
@files_sharing-app-required @issue-ocis-reva-217
@files_sharing-app-required @issue-1297
Scenario Outline: Setting custom DAV property on a shared file as an owner and reading as a recipient
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -83,7 +83,7 @@ Feature: set file properties
| dav_version |
| spaces |
@issue-ocis-reva-276
@issue-1263
Scenario Outline: Setting custom DAV property using one endpoint and reading it with other endpoint
Given using <action_dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testnewold.txt"

20
tests/acceptance/features/coreApiWebdavProperties2/getFileProperties.feature
View File

@@ -34,7 +34,7 @@ Feature: get file properties
| spaces | /नेपाली.txt |
| spaces | s,a,m,p,l,e.txt |
@issue-ocis-reva-214
@issue-1296
Scenario Outline: Do a PROPFIND of various file names
Given using <dav_version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "<file_name>"
@@ -61,7 +61,7 @@ Feature: get file properties
| spaces | /file ?2.txt | dav/spaces/%spaceid%/file ?2.txt |
| spaces | /file &2.txt | dav/spaces/%spaceid%/file &2.txt |
@issue-ocis-reva-214
@issue-1296
Scenario Outline: Do a PROPFIND of various folder names
Given using <dav_version> DAV path
And user "Alice" has created folder "<folder_name>"
@@ -130,7 +130,7 @@ Feature: get file properties
| spaces | /नेपाली | नेपाली |
| spaces | /folder #2.txt | file #2.txt |
@issue-ocis-reva-265
@issue-1259
#after fixing all issues delete this Scenario and merge with the one above
Scenario Outline: Do a PROPFIND of various files inside various folders
Given using <dav_version> DAV path
@@ -168,7 +168,7 @@ Feature: get file properties
| dav_version |
| spaces |
@files_sharing-app-required @issue-ocis-reva-11
@files_sharing-app-required
Scenario Outline: A file that is shared to a user has a share-types property
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -194,7 +194,7 @@ Feature: get file properties
| dav_version |
| spaces |
@files_sharing-app-required @issue-ocis-reva-11
@files_sharing-app-required
Scenario Outline: A file that is shared to a group has a share-types property
Given using <dav_version> DAV path
And group "grp1" has been created
@@ -220,7 +220,7 @@ Feature: get file properties
| dav_version |
| spaces |
@public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-11
@public_link_share-feature-required @files_sharing-app-required
Scenario Outline: A file that is shared by link has a share-types property
Given using <dav_version> DAV path
And user "Alice" has created folder "/test"
@@ -243,7 +243,7 @@ Feature: get file properties
| dav_version |
| spaces |
@skipOnLDAP @user_ldap-issue-268 @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-11
@skipOnLDAP @user_ldap-issue-268 @public_link_share-feature-required @files_sharing-app-required
Scenario Outline: A file that is shared by user,group and link has a share-types property
Given using <dav_version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -280,7 +280,7 @@ Feature: get file properties
| dav_version |
| spaces |
@smokeTest @issue-ocis-reva-216
@smokeTest @issue-2809
Scenario Outline: Retrieving private link
Given using <dav_version> DAV path
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/somefile.txt"
@@ -317,7 +317,7 @@ Feature: get file properties
| /remote.php/dav/spaces/%spaceid%/does-not-exist | Resource not found | |
| /remote.php/dav/spaces/%spaceid%/file1.txt | Resource not found | |
@issue-ocis-reva-217
@issue-1297
Scenario Outline: add, receive multiple custom meta properties to a file
Given using <dav_version> DAV path
And user "Alice" has created folder "/TestFolder"
@@ -350,7 +350,7 @@ Feature: get file properties
| dav_version |
| spaces |
@issue-36920 @issue-ocis-reva-217
@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
And user "Alice" has created folder "/TestFolder"

16
tests/acceptance/features/coreApiWebdavUpload1/uploadFile.feature
View File

@@ -54,7 +54,7 @@ Feature: upload file
| spaces | "C++ file.cpp" |
| spaces | "file #2.txt" |
@issue-ocis-reva-265
@issue-1259
#after fixing all issues delete this Scenario and merge with the one above
Scenario Outline: upload a file and check download content
Given using <dav_version> DAV path
@@ -128,7 +128,7 @@ Feature: upload file
| spaces | /नेपाली | नेपाली |
| spaces | /folder #2.txt | file #2.txt |
@issue-ocis-reva-265
@issue-1259
#after fixing all issues delete this Scenario and merge with the one above
Scenario Outline: upload a file into a folder and check download content
Given using <dav_version> DAV path
@@ -166,7 +166,7 @@ Feature: upload file
| dav_version |
| spaces |
@issue-ocis-reva-15
@issue-1345
Scenario Outline: Uploading file to path with extension .part should not be possible
Given using <dav_version> DAV path
When user "Alice" uploads file "filesForUpload/textfile.txt" to "/textfile.part" using the WebDAV API
@@ -217,7 +217,7 @@ Feature: upload file
| spaces | /upload...1.. | abc...txt.. |
| spaces | /... | ... |
@issue-ocis-reva-174
Scenario Outline: upload file with mtime
Given using <dav_version> DAV path
When user "Alice" uploads file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API
@@ -234,7 +234,7 @@ Feature: upload file
| dav_version |
| spaces |
@issue-ocis-reva-174
Scenario Outline: upload a file with mtime in a folder
Given using <dav_version> DAV path
And user "Alice" has created folder "testFolder"
@@ -252,7 +252,7 @@ Feature: upload file
| dav_version |
| spaces |
@issue-ocis-reva-174
Scenario Outline: moving a file does not change its mtime
Given using <dav_version> DAV path
And user "Alice" has created folder "testFolder"
@@ -271,7 +271,7 @@ Feature: upload file
| dav_version |
| spaces |
@issue-ocis-reva-174
Scenario Outline: overwriting a file changes its mtime
Given using <dav_version> DAV path
And user "Alice" has uploaded file with content "first time upload content" to "file.txt"
@@ -331,4 +331,4 @@ Feature: upload file
@skipOnOcV10 @personalSpace
Examples:
| dav_version |
| spaces |
| spaces |

2
tests/acceptance/features/coreApiWebdavUpload2/uploadFileUsingOldChunking.feature
View File

@@ -1,4 +1,4 @@
@api @issue-ocis-reva-17
@api @issue-1343
Feature: upload file using old chunking
As a user
I want to be able to upload "large" files in chunks