From 9741999d269e856d0754500290b70685b8b19b4b Mon Sep 17 00:00:00 2001 From: Roshan Lamichhane Date: Mon, 6 Feb 2023 12:06:23 +0545 Subject: [PATCH 1/2] Removed some ocis/reva related issue tags --- .../acceptance/features/apiAuth/cors.feature | 2 +- .../features/apiAuth/filesAppAuth.feature | 2 +- .../features/apiAuth/tokenAuth.feature | 2 +- .../features/apiAuth/webDavAuth.feature | 2 +- .../features/apiAuthOcs/ocsDELETEAuth.feature | 2 +- .../ocsDELETEAuthOc10Issue32068.feature | 2 +- .../features/apiAuthOcs/ocsGETAuth.feature | 14 ++++---- .../ocsGETAuthOc10Issue32068.feature | 6 ++-- .../features/apiAuthOcs/ocsPOSTAuth.feature | 2 +- .../features/apiAuthOcs/ocsPUTAuth.feature | 2 +- .../apiAuthWebDav/webDavCOPYAuth.feature | 6 ++-- .../apiAuthWebDav/webDavDELETEAuth.feature | 6 ++-- .../apiAuthWebDav/webDavLOCKAuth.feature | 6 ++-- .../apiAuthWebDav/webDavMKCOLAuth.feature | 8 ++--- .../apiAuthWebDav/webDavMOVEAuth.feature | 6 ++-- .../apiAuthWebDav/webDavPOSTAuth.feature | 4 +-- .../apiAuthWebDav/webDavPROPFINDAuth.feature | 6 ++-- .../apiAuthWebDav/webDavPROPPATCHAuth.feature | 6 ++-- .../apiAuthWebDav/webDavPUTAuth.feature | 4 +-- .../apiCapabilities/capabilities.feature | 2 +- .../features/apiComments/comments.feature | 2 +- .../apiComments/createComments.feature | 2 +- .../apiComments/deleteComments.feature | 2 +- .../features/apiComments/editComments.feature | 2 +- .../favoritesOc10Issue33840.feature | 4 +-- .../features/apiMain/checksums.feature | 36 +++++++++---------- .../createShareWithInvalidPermissions.feature | 4 +-- ...createShareWhenExcludedFromSharing.feature | 2 +- .../createShareWithInvalidPermissions.feature | 4 +-- .../createShareToSharesFolder.feature | 8 ++--- .../accessToShare.feature | 2 +- .../gettingShares.feature | 2 +- .../createPublicLinkShare.feature | 14 ++++---- .../uploadToPublicLinkShare.feature | 2 -- .../features/apiSharees/sharees.feature | 2 +- .../features/apiTags/assignTags.feature | 2 +- .../features/apiTags/assignTagsGroup.feature | 2 +- .../features/apiTags/createTags.feature | 2 +- .../features/apiTags/deleteTags.feature | 2 +- .../features/apiTags/editTags.feature | 2 +- .../features/apiTags/retreiveTags.feature | 2 +- .../features/apiTags/unassignTags.feature | 2 +- .../apiTrashbin/trashbinDelete.feature | 2 +- .../apiTrashbin/trashbinFilesFolders.feature | 2 +- ...trashbinFilesFoldersOc10Issue23151.feature | 2 +- .../trashbinRestore.feature | 2 +- .../trashbinRestoreOc10Issue35974.feature | 2 +- .../features/apiVersions/fileVersions.feature | 16 ++++----- .../fileVersionsSharingToShares.feature | 2 +- .../resharedSharesToRoot.feature | 2 +- .../resharedSharesToShares.feature | 2 +- .../apiWebdavMove1/moveFileAsync.feature | 2 +- .../moveFileToBlacklistedNameAsync.feature | 2 +- .../moveFileToExcludedDirectoryAsync.feature | 2 +- .../apiWebdavMove1/moveFolder.feature | 2 +- .../moveFolderToBlacklistedName.feature | 2 +- .../moveFolderToExcludedDirectory.feature | 2 +- .../moveFileToExcludedDirectory.feature | 2 +- .../apiWebdavOperations/downloadFile.feature | 6 ++-- .../apiWebdavOperations/search.feature | 2 +- .../apiWebdavProperties1/copyFile.feature | 6 ++-- .../createFileFolder.feature | 2 +- .../getFileProperties.feature | 8 ++--- .../apiWebdavUpload1/uploadFile.feature | 2 +- .../uploadFileAsyncUsingNewChunking.feature | 2 +- .../uploadFileToBlacklistedName.feature | 6 ++-- ...acklistedNameAsyncUsingNewChunking.feature | 2 +- .../uploadFileToExcludedDirectory.feature | 6 ++-- ...udedDirectoryAsyncUsingNewChunking.feature | 2 +- ...eToBlacklistedNameUsingNewChunking.feature | 2 +- ...eToBlacklistedNameUsingOldChunking.feature | 2 +- ...NameUsingOldChunkingOc10Issue36645.feature | 2 +- ...oExcludedDirectoryUsingNewChunking.feature | 2 +- ...oExcludedDirectoryUsingOldChunking.feature | 2 +- ...toryUsingOldChunkingOc10Issue36645.feature | 2 +- .../uploadFileUsingNewChunking.feature | 2 +- .../uploadFileUsingOldChunking.feature | 2 +- ...FileUsingOldChunkingOc10Issue36115.feature | 2 +- 78 files changed, 148 insertions(+), 152 deletions(-) diff --git a/tests/acceptance/features/apiAuth/cors.feature b/tests/acceptance/features/apiAuth/cors.feature index c5dc5c3dfbfb..1f0931d32350 100644 --- a/tests/acceptance/features/apiAuth/cors.feature +++ b/tests/acceptance/features/apiAuth/cors.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-26 @issue-ocis-reva-27 +@api Feature: CORS headers Background: diff --git a/tests/acceptance/features/apiAuth/filesAppAuth.feature b/tests/acceptance/features/apiAuth/filesAppAuth.feature index 9910b031f43a..6af0f33bbb72 100644 --- a/tests/acceptance/features/apiAuth/filesAppAuth.feature +++ b/tests/acceptance/features/apiAuth/filesAppAuth.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-28 +@api Feature: auth Background: diff --git a/tests/acceptance/features/apiAuth/tokenAuth.feature b/tests/acceptance/features/apiAuth/tokenAuth.feature index 91b98fea400e..585f4b031caf 100644 --- a/tests/acceptance/features/apiAuth/tokenAuth.feature +++ b/tests/acceptance/features/apiAuth/tokenAuth.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-28 @issue-ocis-reva-37 +@api Feature: tokenAuth Background: diff --git a/tests/acceptance/features/apiAuth/webDavAuth.feature b/tests/acceptance/features/apiAuth/webDavAuth.feature index 5e2dabdf7c80..4a28b15886df 100644 --- a/tests/acceptance/features/apiAuth/webDavAuth.feature +++ b/tests/acceptance/features/apiAuth/webDavAuth.feature @@ -17,7 +17,7 @@ Feature: auth | dav_path | | /remote.php/webdav | - @smokeTest @issue-ocis-reva-28 + @smokeTest Scenario: using WebDAV with token auth Given a new client token for "Alice" has been generated When user "Alice" requests "/remote.php/webdav" with "PROPFIND" using basic token auth diff --git a/tests/acceptance/features/apiAuthOcs/ocsDELETEAuth.feature b/tests/acceptance/features/apiAuthOcs/ocsDELETEAuth.feature index 676cf84b26c1..4788a6a6001c 100644 --- a/tests/acceptance/features/apiAuthOcs/ocsDELETEAuth.feature +++ b/tests/acceptance/features/apiAuthOcs/ocsDELETEAuth.feature @@ -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 @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @issue-32068 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" diff --git a/tests/acceptance/features/apiAuthOcs/ocsDELETEAuthOc10Issue32068.feature b/tests/acceptance/features/apiAuthOcs/ocsDELETEAuthOc10Issue32068.feature index 8a8aef6f40aa..98ff743648d2 100644 --- a/tests/acceptance/features/apiAuthOcs/ocsDELETEAuthOc10Issue32068.feature +++ b/tests/acceptance/features/apiAuthOcs/ocsDELETEAuthOc10Issue32068.feature @@ -1,7 +1,7 @@ @api @files_sharing-app-required Feature: current oC10 behavior for issue-32068 - @smokeTest @issue-32068 @issue-ocis-reva-30 @issue-ocis-reva-65 @skipOnBruteForceProtection @issue-brute_force_protection-112 + @smokeTest @issue-32068 @skipOnBruteForceProtection @issue-brute_force_protection-112 Scenario: send DELETE requests to OCS endpoints as admin 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" diff --git a/tests/acceptance/features/apiAuthOcs/ocsGETAuth.feature b/tests/acceptance/features/apiAuthOcs/ocsGETAuth.feature index 04f13b6b20ae..2765de435392 100644 --- a/tests/acceptance/features/apiAuthOcs/ocsGETAuth.feature +++ b/tests/acceptance/features/apiAuthOcs/ocsGETAuth.feature @@ -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-32068 @skipOnOcV10 @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 + 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-32068 @skipOnOcV10 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-32068 @skipOnOcV10 @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 + 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 + @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" @@ -150,7 +150,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-28 + Scenario: using OCS with token auth of a normal user Given a new client token for "Alice" has been generated When user "Alice" requests these endpoints with "GET" using basic token auth diff --git a/tests/acceptance/features/apiAuthOcs/ocsGETAuthOc10Issue32068.feature b/tests/acceptance/features/apiAuthOcs/ocsGETAuthOc10Issue32068.feature index f46752bccf23..b43336c01be3 100644 --- a/tests/acceptance/features/apiAuthOcs/ocsGETAuthOc10Issue32068.feature +++ b/tests/acceptance/features/apiAuthOcs/ocsGETAuthOc10Issue32068.feature @@ -4,7 +4,7 @@ Feature: current oC10 behavior for issue-32068 Background: Given user "Alice" has been created with default attributes and without skeleton files - @issue-32068 @issue-ocis-reva-30 @smokeTest + @issue-32068 @smokeTest Scenario: using OCS anonymously When a user requests these endpoints with "GET" and no authentication | endpoint | @@ -26,7 +26,7 @@ Feature: current oC10 behavior for issue-32068 And the OCS status code of responses on all endpoints should be "997" #And the OCS status code of responses on all endpoints should be "401" - @issue-32068 @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-32068 Scenario: using OCS with non-admin basic auth When the user "Alice" requests these endpoints with "GET" with basic auth | endpoint | @@ -58,7 +58,7 @@ Feature: current oC10 behavior for issue-32068 And the OCS status code of responses on all endpoints should be "997" #And the OCS status code of responses on all endpoints should be "401" - @issue-32068 @issue-ocis-reva-29 @issue-ocis-reva-30 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 + @issue-32068 @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 | diff --git a/tests/acceptance/features/apiAuthOcs/ocsPOSTAuth.feature b/tests/acceptance/features/apiAuthOcs/ocsPOSTAuth.feature index 9b10a64ee6ff..ed547a484933 100644 --- a/tests/acceptance/features/apiAuthOcs/ocsPOSTAuth.feature +++ b/tests/acceptance/features/apiAuthOcs/ocsPOSTAuth.feature @@ -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 + @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 | diff --git a/tests/acceptance/features/apiAuthOcs/ocsPUTAuth.feature b/tests/acceptance/features/apiAuthOcs/ocsPUTAuth.feature index c6101795534b..a551906084fc 100644 --- a/tests/acceptance/features/apiAuthOcs/ocsPUTAuth.feature +++ b/tests/acceptance/features/apiAuthOcs/ocsPUTAuth.feature @@ -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 + @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" diff --git a/tests/acceptance/features/apiAuthWebDav/webDavCOPYAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavCOPYAuth.feature index de75e3cee705..954cf4cf3afe 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavCOPYAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavCOPYAuth.feature @@ -37,7 +37,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 "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 | @@ -79,7 +79,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 "401" - @issue-ocis-reva-37 + Scenario: send COPY requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -93,7 +93,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 "401" - @issue-ocis-reva-37 + Scenario: send COPY requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiAuthWebDav/webDavDELETEAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavDELETEAuth.feature index 0e4c28e28fdf..c4ccb1179b08 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavDELETEAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavDELETEAuth.feature @@ -36,7 +36,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 "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 | @@ -78,7 +78,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 "401" - @issue-ocis-reva-60 + Scenario: send DELETE requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -92,7 +92,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 "401" - @issue-ocis-reva-60 + Scenario: send DELETE requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiAuthWebDav/webDavLOCKAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavLOCKAuth.feature index 93ae796ccb67..78247b05e2ea 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavLOCKAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavLOCKAuth.feature @@ -34,7 +34,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 "401" - @issue-ocis-reva-9 + 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 | @@ -78,7 +78,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 "401" - @issue-ocis-reva-37 + Scenario: send LOCK requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -92,7 +92,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 "401" - @issue-ocis-reva-37 + Scenario: send LOCK requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiAuthWebDav/webDavMKCOLAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavMKCOLAuth.feature index 9fb6c060dcad..26491febba60 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavMKCOLAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavMKCOLAuth.feature @@ -30,7 +30,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 "401" - @skipOnOcV10 @issue-ocis-5049 @issue-ocis-reva-9 @issue-ocis-reva-197 + @skipOnOcV10 @issue-ocis-reva-197 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" @@ -41,7 +41,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-ocis-reva-197 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" @@ -86,7 +86,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 "401" - @issue-ocis-reva-37 + Scenario: send MKCOL requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -100,7 +100,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 "401" - @issue-ocis-reva-37 + Scenario: send MKCOL requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiAuthWebDav/webDavMOVEAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavMOVEAuth.feature index b3faa5d3a9a7..606a64f320e1 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavMOVEAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavMOVEAuth.feature @@ -33,7 +33,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 "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 | @@ -75,7 +75,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 "401" - @issue-ocis-reva-37 + Scenario: send MOVE requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -89,7 +89,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 "401" - @issue-ocis-reva-37 + Scenario: send MOVE requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature index 4bbeb28af619..9b8410db962e 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature @@ -76,7 +76,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 "401" - @issue-ocis-reva-37 + Scenario: send POST requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -90,7 +90,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 "401" - @issue-ocis-reva-37 + Scenario: send POST requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiAuthWebDav/webDavPROPFINDAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavPROPFINDAuth.feature index b264bf20e26a..9aa0394de4de 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavPROPFINDAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavPROPFINDAuth.feature @@ -33,7 +33,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 "401" - @issue-ocis-reva-9 + 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 | @@ -75,7 +75,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 "401" - @issue-ocis-reva-37 + Scenario: send PROPFIND requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -89,7 +89,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 "401" - @issue-ocis-reva-37 + Scenario: send PROPFIND requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiAuthWebDav/webDavPROPPATCHAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavPROPPATCHAuth.feature index a0a7a978391c..02f7d4a781aa 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavPROPPATCHAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavPROPPATCHAuth.feature @@ -34,7 +34,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 "401" - @issue-ocis-reva-9 @issue-ocis-reva-197 + @issue-ocis-reva-197 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 | @@ -76,7 +76,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 "401" - @issue-ocis-reva-37 + Scenario: send PROPPATCH requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -90,7 +90,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 "401" - @issue-ocis-reva-37 + Scenario: send PROPPATCH requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiAuthWebDav/webDavPUTAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavPUTAuth.feature index aea5d85496b9..25e62ff92882 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavPUTAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavPUTAuth.feature @@ -79,7 +79,7 @@ Feature: get file info using PUT | /remote.php/dav/files/%username%/PARENT/parent.txt | Then the HTTP status code of responses on all endpoints should be "401" - @issue-ocis-reva-37 + Scenario: send PUT requests to webDav endpoints using token authentication should not work Given token auth has been enforced And a new browser session for "Alice" has been started @@ -93,7 +93,7 @@ Feature: get file info using PUT | /remote.php/dav/files/%username%/PARENT/parent.txt | Then the HTTP status code of responses on all endpoints should be "401" - @issue-ocis-reva-37 + Scenario: send PUT requests to webDav endpoints using app password token as password Given token auth has been enforced And a new browser session for "Alice" has been started diff --git a/tests/acceptance/features/apiCapabilities/capabilities.feature b/tests/acceptance/features/apiCapabilities/capabilities.feature index 59de0f0d1d2e..68928c51978d 100644 --- a/tests/acceptance/features/apiCapabilities/capabilities.feature +++ b/tests/acceptance/features/apiCapabilities/capabilities.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-reva-41 +@api @files_sharing-app-required Feature: capabilities Background: diff --git a/tests/acceptance/features/apiComments/comments.feature b/tests/acceptance/features/apiComments/comments.feature index 20641d996a31..058b2c099a4b 100644 --- a/tests/acceptance/features/apiComments/comments.feature +++ b/tests/acceptance/features/apiComments/comments.feature @@ -1,4 +1,4 @@ -@api @comments-app-required @issue-ocis-reva-38 +@api @comments-app-required Feature: Comments Background: diff --git a/tests/acceptance/features/apiComments/createComments.feature b/tests/acceptance/features/apiComments/createComments.feature index c22b7a108df6..8d6988626b9e 100644 --- a/tests/acceptance/features/apiComments/createComments.feature +++ b/tests/acceptance/features/apiComments/createComments.feature @@ -1,4 +1,4 @@ -@api @comments-app-required @files_sharing-app-required @issue-ocis-reva-38 +@api @comments-app-required @files_sharing-app-required Feature: Comments Background: diff --git a/tests/acceptance/features/apiComments/deleteComments.feature b/tests/acceptance/features/apiComments/deleteComments.feature index 70094c7299f4..0144487956d5 100644 --- a/tests/acceptance/features/apiComments/deleteComments.feature +++ b/tests/acceptance/features/apiComments/deleteComments.feature @@ -1,4 +1,4 @@ -@api @comments-app-required @issue-ocis-reva-38 +@api @comments-app-required Feature: Comments Background: diff --git a/tests/acceptance/features/apiComments/editComments.feature b/tests/acceptance/features/apiComments/editComments.feature index 49eed785a182..3afee9cf8579 100644 --- a/tests/acceptance/features/apiComments/editComments.feature +++ b/tests/acceptance/features/apiComments/editComments.feature @@ -1,4 +1,4 @@ -@api @comments-app-required @issue-ocis-reva-38 +@api @comments-app-required Feature: Comments Background: diff --git a/tests/acceptance/features/apiFavorites/favoritesOc10Issue33840.feature b/tests/acceptance/features/apiFavorites/favoritesOc10Issue33840.feature index 1efacf2cfbef..83cca2dcb964 100644 --- a/tests/acceptance/features/apiFavorites/favoritesOc10Issue33840.feature +++ b/tests/acceptance/features/apiFavorites/favoritesOc10Issue33840.feature @@ -13,7 +13,7 @@ Feature: current oC10 behavior for issue-33840 And user "Alice" has created folder "/PARENT" And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt" - @issue-33840 @issue-ocis-reva-39 + @issue-33840 Scenario Outline: Get favorited elements and limit count of entries Given using DAV path And user "Alice" has favorited element "/textfile0.txt" @@ -35,7 +35,7 @@ Feature: current oC10 behavior for issue-33840 | old | | new | - @issue-33840 @issue-ocis-reva-39 + @issue-33840 Scenario Outline: Get favorited elements paginated in subfolder Given using DAV path And user "Alice" has created folder "/subfolder" diff --git a/tests/acceptance/features/apiMain/checksums.feature b/tests/acceptance/features/apiMain/checksums.feature index 3e303e429176..de68fc4c2968 100644 --- a/tests/acceptance/features/apiMain/checksums.feature +++ b/tests/acceptance/features/apiMain/checksums.feature @@ -24,7 +24,7 @@ Feature: checksums | old | | new | - @smokeTest @issue-ocis-reva-98 + @smokeTest Scenario Outline: Uploading a file with checksum should return the checksum in the download header Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" @@ -48,7 +48,7 @@ Feature: checksums | old | | new | - @issue-ocis-reva-98 + Scenario Outline: Downloading a file with checksum should return the checksum in the download header Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" @@ -74,7 +74,7 @@ Feature: checksums | dav_version | | old | - @issue-ocis-reva-17 + Scenario Outline: Uploading a chunked file with checksum should return the checksum in the download header Given using DAV path And user "Alice" has uploaded chunk file "1" of "3" with "AAAAA" to "/myChecksumFile.txt" with checksum "MD5:45a72715acdd5019c5be30bdbb75233e" @@ -103,7 +103,7 @@ Feature: checksums | old | | new | - @issue-ocis-reva-14 + Scenario Outline: Moving file with checksum should return the checksum in the download header Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" @@ -127,7 +127,7 @@ Feature: checksums | dav_version | | new | - @issue-ocis-reva-98 + Scenario Outline: Copying file with checksum should return the checksum in the download header using new DAV path Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" @@ -170,7 +170,7 @@ Feature: checksums | dav_version | checksum | | new | SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a | - @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload new DAV chunked file where checksum matches Given using new DAV path And user "Alice" has created a new chunking upload with id "chunking-42" @@ -179,7 +179,7 @@ Feature: checksums And user "Alice" moves new chunk file with id "chunking-42" to "/myChunkedFile.txt" with checksum "SHA1:5d84d61b03fdacf813640f5242d309721e0629b1" using the WebDAV API Then the HTTP status code of responses on all endpoints should be "201" - @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload new DAV chunked file where checksum does not match Given using new DAV path And user "Alice" has created a new chunking upload with id "chunking-42" @@ -190,7 +190,7 @@ Feature: checksums And user "Alice" should not see the following elements | /myChunkedFile.txt | - @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload new DAV chunked file using async MOVE where checksum matches Given using new DAV path And the administrator has enabled async operations @@ -206,7 +206,7 @@ Feature: checksums | fileId | /^[0-9a-z]{20,}$/ | And the content of file "/myChunkedFile.txt" for user "Alice" should be "BBBBBCCCCC" - @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload new DAV chunked file using async MOVE where checksum does not match Given using new DAV path And the administrator has enabled async operations @@ -224,7 +224,7 @@ Feature: checksums And user "Alice" should not see the following elements | /myChunkedFile.txt | - @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload new DAV chunked file using async MOVE where checksum does not match - retry with correct checksum Given using new DAV path And the administrator has enabled async operations @@ -241,7 +241,7 @@ Feature: checksums | fileId | /^[0-9a-z]{20,}$/ | And the content of file "/myChunkedFile.txt" for user "Alice" should be "BBBBBCCCCC" - @issue-ocis-reva-99 + Scenario Outline: Upload a file where checksum does not match Given using DAV path When user "Alice" uploads file with checksum "SHA1:f005ba11" and content "Some Text" to "/chksumtst.txt" using the WebDAV API @@ -263,7 +263,7 @@ Feature: checksums | old | | new | - @issue-ocis-reva-99 + Scenario Outline: Uploaded file should have the same checksum when downloaded Given using DAV path And user "Alice" has uploaded file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/chksumtst.txt" @@ -291,8 +291,8 @@ Feature: checksums | old | | new | + ## Validation Plugin or Old Endpoint Specific - @issue-ocis-reva-17 Scenario Outline: Uploading an old method chunked file with checksum should fail using new DAV path Given using DAV path When user "Alice" uploads chunk file "1" of "3" with "AAAAA" to "/myChecksumFile.txt" with checksum "MD5:45a72715acdd5019c5be30bdbb75233e" using the WebDAV API @@ -303,8 +303,8 @@ Feature: checksums | dav_version | | new | + ## upload overwriting - @issue-ocis-reva-196 Scenario Outline: Uploading a file with MD5 checksum overwriting an existing file Given using DAV path And user "Alice" has uploaded file with content "some data" to "textfile0.txt" @@ -322,7 +322,7 @@ Feature: checksums | old | | new | - @issue-ocis-reva-196 + Scenario Outline: Uploading a file with SHA1 checksum overwriting an existing file Given using DAV path And user "Alice" has uploaded file with content "some data" to "textfile0.txt" @@ -353,7 +353,7 @@ Feature: checksums | old | | new | - @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload overwriting a file with new chunking and correct checksum Given using new DAV path And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" @@ -364,7 +364,7 @@ Feature: checksums Then the HTTP status code of responses on each endpoint should be "201, 201, 204" respectively And the content of file "/textfile0.txt" for user "Alice" should be "BBBBBCCCCC" - @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @newChunking @issue-ocis-1321 Scenario: Upload overwriting a file with new chunking and invalid checksum Given using new DAV path And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" @@ -375,7 +375,7 @@ Feature: checksums Then the HTTP status code of responses on each endpoint should be "201, 201, 400" respectively And the content of file "/textfile0.txt" for user "Alice" should be "ownCloud test text file 0" - @issue-ocis-reva-214 + Scenario Outline: Uploading a file with checksum should work for file with special characters Given using DAV path When user "Alice" uploads file "filesForUpload/textfile.txt" to with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" using the WebDAV API diff --git a/tests/acceptance/features/apiShareCreateSpecialToRoot2/createShareWithInvalidPermissions.feature b/tests/acceptance/features/apiShareCreateSpecialToRoot2/createShareWithInvalidPermissions.feature index 4e467a59919d..2b573ec1619b 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToRoot2/createShareWithInvalidPermissions.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToRoot2/createShareWithInvalidPermissions.feature @@ -81,7 +81,7 @@ Feature: cannot share resources with invalid permissions | 1 | 400 | 200 | create,delete | | 2 | 400 | 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 "" And group "grp1" has been created @@ -100,7 +100,7 @@ Feature: cannot share resources with invalid permissions | 1 | 400 | 200 | | 2 | 400 | 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 "" And group "grp1" has been created diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature b/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature index 4507849b9950..9aeec236c612 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-reva-41 +@api @files_sharing-app-required Feature: cannot share resources when in a group that is excluded from sharing Background: diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature index 3f654ac014f1..34dc9fc0f1fc 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature @@ -73,7 +73,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 "" And user "Brian" has been created with default attributes and without skeleton files @@ -94,7 +94,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 "" And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature index 896849200902..0c22d511df73 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature @@ -157,7 +157,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 "" And group "grp1" has been created @@ -182,7 +182,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 "" And group "grp1" has been created @@ -396,7 +396,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 | @@ -434,7 +434,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 "" And these users have been created with default attributes and without skeleton files: diff --git a/tests/acceptance/features/apiShareOperationsToShares1/accessToShare.feature b/tests/acceptance/features/apiShareOperationsToShares1/accessToShare.feature index 9c3c3163c356..3b17801f163f 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/accessToShare.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/accessToShare.feature @@ -58,7 +58,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @issue-ocis-reva-34 @issue-ocis-reva-194 + @smokeTest @issue-ocis-reva-194 Scenario Outline: Sharee can see the group share Given using OCS API version "" And group "grp1" has been created diff --git a/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature b/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature index 0018e5b2776a..674202777800 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature @@ -24,7 +24,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-65 + Scenario Outline: getting all shares of a user using another user Given using OCS API version "" And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" diff --git a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature index 2303b9de0577..a501eccd881e 100644 --- a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature @@ -30,7 +30,7 @@ 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-ocis-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -158,7 +158,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-ocis-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -261,7 +261,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-ocis-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -293,7 +293,6 @@ Feature: create a public link share | permissions | create | Then the OCS status code should be "" - @issue-ocis-2079 @issue-ocis-reva-41 Examples: | ocs_api_version | ocs_status_code | | 1 | 403 | @@ -311,13 +310,12 @@ Feature: create a public link share | permissions | read,create | Then the OCS status code should be "" - @issue-ocis-2079 @issue-ocis-reva-41 Examples: | ocs_api_version | ocs_status_code | | 1 | 403 | | 2 | 403 | - @issue-ocis-reva-41 + Scenario Outline: Creating a link share with read+update+create permissions is forbidden when public upload is disabled globally Given using OCS API version "" And parameter "shareapi_allow_public_upload" of app "core" has been set to "no" @@ -333,7 +331,7 @@ Feature: create a public link share | 1 | 403 | | 2 | 403 | - @issue-ocis-reva-41 + Scenario Outline: Creating a link share with update permissions defaults to read permissions when public upload disabled globally Given using OCS API version "" And parameter "shareapi_allow_public_upload" of app "core" has been set to "no" @@ -442,7 +440,7 @@ Feature: create a public link share | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-41 + Scenario Outline: Create a public link with default expiration date set and max expiration date enforced and access using the public WebDAV API Given using OCS API version "" And parameter "shareapi_default_expire_date" of app "core" has been set to "yes" diff --git a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature index 5da1b5756c85..436d326c09ac 100644 --- a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature @@ -190,7 +190,6 @@ Feature: upload to a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-41 Examples: | public-webdav-api-version | | new | @@ -211,7 +210,6 @@ Feature: upload to a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-41 Examples: | public-webdav-api-version | | new | diff --git a/tests/acceptance/features/apiSharees/sharees.feature b/tests/acceptance/features/apiSharees/sharees.feature index d98e277d81d3..fde752d8a6e2 100644 --- a/tests/acceptance/features/apiSharees/sharees.feature +++ b/tests/acceptance/features/apiSharees/sharees.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-reva-34 +@api @files_sharing-app-required Feature: sharees Background: diff --git a/tests/acceptance/features/apiTags/assignTags.feature b/tests/acceptance/features/apiTags/assignTags.feature index 3391b7271ca2..32431a589042 100644 --- a/tests/acceptance/features/apiTags/assignTags.feature +++ b/tests/acceptance/features/apiTags/assignTags.feature @@ -1,4 +1,4 @@ -@api @systemtags-app-required @files_sharing-app-required @issue-ocis-reva-51 +@api @systemtags-app-required @files_sharing-app-required Feature: Assign tags to file/folder As a user I want to assign tags to the file/folder diff --git a/tests/acceptance/features/apiTags/assignTagsGroup.feature b/tests/acceptance/features/apiTags/assignTagsGroup.feature index c441aeac6cd5..d55fb51becb3 100644 --- a/tests/acceptance/features/apiTags/assignTagsGroup.feature +++ b/tests/acceptance/features/apiTags/assignTagsGroup.feature @@ -1,4 +1,4 @@ -@api @systemtags-app-required @issue-ocis-reva-51 +@api @systemtags-app-required Feature: Assign tag to groups As a user I should be able to assign tag to groups diff --git a/tests/acceptance/features/apiTags/createTags.feature b/tests/acceptance/features/apiTags/createTags.feature index d80bb1f1a87b..fdf3a2ea5d0a 100644 --- a/tests/acceptance/features/apiTags/createTags.feature +++ b/tests/acceptance/features/apiTags/createTags.feature @@ -1,4 +1,4 @@ -@api @systemtags-app-required @issue-ocis-reva-51 +@api @systemtags-app-required Feature: Creation of tags As a user I should be able to create tags diff --git a/tests/acceptance/features/apiTags/deleteTags.feature b/tests/acceptance/features/apiTags/deleteTags.feature index ef128574526f..27fc28f60897 100644 --- a/tests/acceptance/features/apiTags/deleteTags.feature +++ b/tests/acceptance/features/apiTags/deleteTags.feature @@ -1,4 +1,4 @@ -@api @systemtags-app-required @issue-ocis-reva-51 +@api @systemtags-app-required Feature: Deletion of tags As a user I want to delete the tags that are already created diff --git a/tests/acceptance/features/apiTags/editTags.feature b/tests/acceptance/features/apiTags/editTags.feature index f548976145b2..8afde7daa1c7 100644 --- a/tests/acceptance/features/apiTags/editTags.feature +++ b/tests/acceptance/features/apiTags/editTags.feature @@ -1,4 +1,4 @@ -@api @systemtags-app-required @issue-ocis-reva-51 +@api @systemtags-app-required Feature: Editing the tags As a user I want to be able to change the tags I have created diff --git a/tests/acceptance/features/apiTags/retreiveTags.feature b/tests/acceptance/features/apiTags/retreiveTags.feature index 857d0f82a624..59f5fdd09cc9 100644 --- a/tests/acceptance/features/apiTags/retreiveTags.feature +++ b/tests/acceptance/features/apiTags/retreiveTags.feature @@ -1,4 +1,4 @@ -@api @systemtags-app-required @issue-ocis-reva-51 +@api @systemtags-app-required Feature: tags Background: diff --git a/tests/acceptance/features/apiTags/unassignTags.feature b/tests/acceptance/features/apiTags/unassignTags.feature index b22093677984..47f2d6893a10 100644 --- a/tests/acceptance/features/apiTags/unassignTags.feature +++ b/tests/acceptance/features/apiTags/unassignTags.feature @@ -1,4 +1,4 @@ -@api @systemtags-app-required @files_sharing-app-required @issue-ocis-reva-51 +@api @systemtags-app-required @files_sharing-app-required Feature: Unassigning tags from file/folder As a user I want to be able to remove tags from file/folder diff --git a/tests/acceptance/features/apiTrashbin/trashbinDelete.feature b/tests/acceptance/features/apiTrashbin/trashbinDelete.feature index c47a5371521a..0cd49861f028 100644 --- a/tests/acceptance/features/apiTrashbin/trashbinDelete.feature +++ b/tests/acceptance/features/apiTrashbin/trashbinDelete.feature @@ -1,4 +1,4 @@ -@api @files_trashbin-app-required @issue-ocis-reva-52 +@api @files_trashbin-app-required Feature: files and folders can be deleted from the trashbin As a user I want to delete files and folders from the trashbin diff --git a/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature b/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature index 3af770053709..581871c3ef06 100644 --- a/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature +++ b/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature @@ -1,4 +1,4 @@ -@api @files_trashbin-app-required @issue-ocis-reva-52 +@api @files_trashbin-app-required 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 diff --git a/tests/acceptance/features/apiTrashbin/trashbinFilesFoldersOc10Issue23151.feature b/tests/acceptance/features/apiTrashbin/trashbinFilesFoldersOc10Issue23151.feature index 4f9b687ec95d..0ba2d30869a6 100644 --- a/tests/acceptance/features/apiTrashbin/trashbinFilesFoldersOc10Issue23151.feature +++ b/tests/acceptance/features/apiTrashbin/trashbinFilesFoldersOc10Issue23151.feature @@ -1,4 +1,4 @@ -@api @files_trashbin-app-required @issue-ocis-reva-52 +@api @files_trashbin-app-required 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 diff --git a/tests/acceptance/features/apiTrashbinRestore/trashbinRestore.feature b/tests/acceptance/features/apiTrashbinRestore/trashbinRestore.feature index 22911346194f..c0739b0c2971 100644 --- a/tests/acceptance/features/apiTrashbinRestore/trashbinRestore.feature +++ b/tests/acceptance/features/apiTrashbinRestore/trashbinRestore.feature @@ -1,4 +1,4 @@ -@api @files_trashbin-app-required @issue-ocis-reva-52 +@api @files_trashbin-app-required Feature: Restore deleted files/folders As a user I would like to restore files/folders diff --git a/tests/acceptance/features/apiTrashbinRestore/trashbinRestoreOc10Issue35974.feature b/tests/acceptance/features/apiTrashbinRestore/trashbinRestoreOc10Issue35974.feature index be6b87fc3ca1..aeb2b988dc7c 100644 --- a/tests/acceptance/features/apiTrashbinRestore/trashbinRestoreOc10Issue35974.feature +++ b/tests/acceptance/features/apiTrashbinRestore/trashbinRestoreOc10Issue35974.feature @@ -1,4 +1,4 @@ -@api @files_trashbin-app-required @issue-ocis-reva-52 +@api @files_trashbin-app-required Feature: Restore deleted files/folders As a user I would like to restore files/folders diff --git a/tests/acceptance/features/apiVersions/fileVersions.feature b/tests/acceptance/features/apiVersions/fileVersions.feature index b0b0e268864e..3fee5ce58127 100644 --- a/tests/acceptance/features/apiVersions/fileVersions.feature +++ b/tests/acceptance/features/apiVersions/fileVersions.feature @@ -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 + 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" @@ -21,13 +21,13 @@ Feature: dav-versions And the version folder of file "/davtest.txt-newdav-regular" for user "Alice" should contain "0" elements And the version folder of file "/davtest.txt-olddav-oldchunking" for user "Alice" should contain "0" elements - @issue-ocis-reva-17 @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload file and no version is available using new chunking When user "Alice" uploads file "filesForUpload/davtest.txt" to "/davtest.txt" in 2 chunks with new chunking and using the WebDAV API 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-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload file and no version is available using async upload Given the administrator has enabled async operations When user "Alice" uploads file "filesForUpload/davtest.txt" asynchronously to "/davtest.txt" in 3 chunks with new chunking and using the WebDAV API @@ -42,7 +42,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 + 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 @@ -51,14 +51,14 @@ Feature: dav-versions And the version folder of file "/davtest.txt-newdav-regular" for user "Alice" should contain "1" element And the version folder of file "/davtest.txt-olddav-oldchunking" for user "Alice" should contain "1" element - @issue-ocis-reva-17 @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload a file twice and versions are available using new chunking When user "Alice" uploads file "filesForUpload/davtest.txt" to "/davtest.txt" in 2 chunks with new chunking and using the WebDAV API And user "Alice" uploads file "filesForUpload/davtest.txt" to "/davtest.txt" in 2 chunks with new chunking and using the WebDAV API Then the HTTP status code of responses on each endpoint should be "201, 204" respectively And the version folder of file "/davtest.txt" for user "Alice" should contain "1" element - @issue-ocis-reva-17 @issue-ocis-reva-56 @newChunking @issue-ocis-1321 + @newChunking @issue-ocis-1321 Scenario: Upload a file twice and versions are available using async upload Given the administrator has enabled async operations When user "Alice" uploads file "filesForUpload/davtest.txt" asynchronously to "/davtest.txt" in 2 chunks with new chunking and using the WebDAV API @@ -94,7 +94,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 Scenario Outline: Uploading a chunked file does create the correct version that can be restored Given using DAV path And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" @@ -114,7 +114,7 @@ Feature: dav-versions | dav-path | status-code | | new | 204 | - @skipOnStorage:ceph @files_primary_s3-issue-161 @newChunking @issue-ocis-1321 @issue-ocis-reva-17 @issue-ocis-reva-56 @skipOnStorage:scality + @skipOnStorage:ceph @files_primary_s3-issue-161 @newChunking @skipOnStorage:scality Scenario: Uploading a file asynchronously does create the correct version that can be restored Given the administrator has enabled async operations And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" diff --git a/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature b/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature index 63dc7e502579..695fdab9ac89 100644 --- a/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature +++ b/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature @@ -169,7 +169,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Alice" should be "old content" And the content of file "/received/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 diff --git a/tests/acceptance/features/apiWebdavLocks2/resharedSharesToRoot.feature b/tests/acceptance/features/apiWebdavLocks2/resharedSharesToRoot.feature index 2011873a7d73..4a99da78d5b6 100644 --- a/tests/acceptance/features/apiWebdavLocks2/resharedSharesToRoot.feature +++ b/tests/acceptance/features/apiWebdavLocks2/resharedSharesToRoot.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-reva-172 @issue-ocis-reva-11 +@api @files_sharing-app-required Feature: lock should propagate correctly if a share is reshared Background: diff --git a/tests/acceptance/features/apiWebdavLocks2/resharedSharesToShares.feature b/tests/acceptance/features/apiWebdavLocks2/resharedSharesToShares.feature index d434b582fb14..62d8b36deb70 100644 --- a/tests/acceptance/features/apiWebdavLocks2/resharedSharesToShares.feature +++ b/tests/acceptance/features/apiWebdavLocks2/resharedSharesToShares.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-reva-172 @issue-ocis-reva-11 +@api @files_sharing-app-required Feature: lock should propagate correctly if a share is reshared Background: diff --git a/tests/acceptance/features/apiWebdavMove1/moveFileAsync.feature b/tests/acceptance/features/apiWebdavMove1/moveFileAsync.feature index 557c432d626e..9b89e7670b1d 100644 --- a/tests/acceptance/features/apiWebdavMove1/moveFileAsync.feature +++ b/tests/acceptance/features/apiWebdavMove1/moveFileAsync.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-14 +@api Feature: move (rename) file As a user I want to be able to move and rename files asynchronously diff --git a/tests/acceptance/features/apiWebdavMove1/moveFileToBlacklistedNameAsync.feature b/tests/acceptance/features/apiWebdavMove1/moveFileToBlacklistedNameAsync.feature index 0bf595f3f037..0bfc96b0a511 100644 --- a/tests/acceptance/features/apiWebdavMove1/moveFileToBlacklistedNameAsync.feature +++ b/tests/acceptance/features/apiWebdavMove1/moveFileToBlacklistedNameAsync.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-14 +@api Feature: users cannot move (rename) a file to a blacklisted name As an administrator I want to be able to prevent users from moving (renaming) files to specified file names diff --git a/tests/acceptance/features/apiWebdavMove1/moveFileToExcludedDirectoryAsync.feature b/tests/acceptance/features/apiWebdavMove1/moveFileToExcludedDirectoryAsync.feature index 361325b698d2..12e7f7829083 100644 --- a/tests/acceptance/features/apiWebdavMove1/moveFileToExcludedDirectoryAsync.feature +++ b/tests/acceptance/features/apiWebdavMove1/moveFileToExcludedDirectoryAsync.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-14 +@api Feature: users cannot move (rename) a file to or into an excluded directory As an administrator I want to be able to exclude directories (folders) from being processed. Any attempt to rename an existing file or folder to one of those names should be refused. diff --git a/tests/acceptance/features/apiWebdavMove1/moveFolder.feature b/tests/acceptance/features/apiWebdavMove1/moveFolder.feature index a8927f147aa8..d4eb7c0abd3e 100644 --- a/tests/acceptance/features/apiWebdavMove1/moveFolder.feature +++ b/tests/acceptance/features/apiWebdavMove1/moveFolder.feature @@ -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 diff --git a/tests/acceptance/features/apiWebdavMove1/moveFolderToBlacklistedName.feature b/tests/acceptance/features/apiWebdavMove1/moveFolderToBlacklistedName.feature index 70bc672e3f25..d15ee9156aa3 100644 --- a/tests/acceptance/features/apiWebdavMove1/moveFolderToBlacklistedName.feature +++ b/tests/acceptance/features/apiWebdavMove1/moveFolderToBlacklistedName.feature @@ -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 diff --git a/tests/acceptance/features/apiWebdavMove1/moveFolderToExcludedDirectory.feature b/tests/acceptance/features/apiWebdavMove1/moveFolderToExcludedDirectory.feature index e08d68ed1849..6c3f8c48a6e4 100644 --- a/tests/acceptance/features/apiWebdavMove1/moveFolderToExcludedDirectory.feature +++ b/tests/acceptance/features/apiWebdavMove1/moveFolderToExcludedDirectory.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-14 +@api Feature: users cannot move (rename) a folder to or into an excluded directory As an administrator I want to be able to exclude directories (folders) from being processed. Any attempt to rename an existing folder to one of those names should be refused. diff --git a/tests/acceptance/features/apiWebdavMove2/moveFileToExcludedDirectory.feature b/tests/acceptance/features/apiWebdavMove2/moveFileToExcludedDirectory.feature index b5aa23e7e3e9..35b48940bf71 100644 --- a/tests/acceptance/features/apiWebdavMove2/moveFileToExcludedDirectory.feature +++ b/tests/acceptance/features/apiWebdavMove2/moveFileToExcludedDirectory.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-14 +@api Feature: users cannot move (rename) a file to or into an excluded directory As an administrator I want to be able to exclude directories (folders) from being processed. Any attempt to rename an existing file to one of those names should be refused. diff --git a/tests/acceptance/features/apiWebdavOperations/downloadFile.feature b/tests/acceptance/features/apiWebdavOperations/downloadFile.feature index 2d5ab31786cc..1cd290a8bc4d 100644 --- a/tests/acceptance/features/apiWebdavOperations/downloadFile.feature +++ b/tests/acceptance/features/apiWebdavOperations/downloadFile.feature @@ -20,7 +20,7 @@ Feature: download file | old | | new | - @issue-ocis-reva-12 + Scenario Outline: download a file with range Given using DAV path When user "Alice" downloads file "/welcome.txt" with range "bytes=24-50" using the WebDAV API @@ -102,7 +102,7 @@ Feature: download file | old | | new | - @issue-ocis-reva-98 + Scenario Outline: Get the content-length response header of a pdf file Given using DAV path And user "Alice" has uploaded file "filesForUpload/simple.pdf" to "/simple.pdf" @@ -116,7 +116,7 @@ Feature: download file | old | | new | - @issue-ocis-reva-98 + Scenario Outline: Get the content-length response header of an image file Given using DAV path And user "Alice" has uploaded file "filesForUpload/testavatar.png" to "/testavatar.png" diff --git a/tests/acceptance/features/apiWebdavOperations/search.feature b/tests/acceptance/features/apiWebdavOperations/search.feature index 56ccd74c3e6c..c2f0da0e47d1 100644 --- a/tests/acceptance/features/apiWebdavOperations/search.feature +++ b/tests/acceptance/features/apiWebdavOperations/search.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-39 +@api Feature: Search As a user I would like to be able to search for files diff --git a/tests/acceptance/features/apiWebdavProperties1/copyFile.feature b/tests/acceptance/features/apiWebdavProperties1/copyFile.feature index 9ec0f061730b..ff33deba38bf 100644 --- a/tests/acceptance/features/apiWebdavProperties1/copyFile.feature +++ b/tests/acceptance/features/apiWebdavProperties1/copyFile.feature @@ -48,7 +48,7 @@ Feature: copy file | old | | new | - @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 path And user "Brian" has been created with default attributes and without skeleton files @@ -67,7 +67,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 path And user "Brian" has been created with default attributes and without skeleton files @@ -88,7 +88,7 @@ Feature: copy file | old | | new | - @issue-ocis-reva-15 + Scenario Outline: Copying file to a path with extension .part should not be possible Given using DAV path When user "Alice" copies file "/textfile1.txt" to "/textfile1.part" using the WebDAV API diff --git a/tests/acceptance/features/apiWebdavProperties1/createFileFolder.feature b/tests/acceptance/features/apiWebdavProperties1/createFileFolder.feature index 89553b70b0d4..fae9d25b263f 100644 --- a/tests/acceptance/features/apiWebdavProperties1/createFileFolder.feature +++ b/tests/acceptance/features/apiWebdavProperties1/createFileFolder.feature @@ -61,7 +61,7 @@ Feature: create files and folder | old | | new | - @issue-ocis-reva-15 + Scenario Outline: Creating a directory which contains .part should not be possible Given using DAV path When user "Alice" creates folder "/folder.with.ext.part" using the WebDAV API diff --git a/tests/acceptance/features/apiWebdavProperties2/getFileProperties.feature b/tests/acceptance/features/apiWebdavProperties2/getFileProperties.feature index 20d1a7a6bf84..dadf112a1e70 100644 --- a/tests/acceptance/features/apiWebdavProperties2/getFileProperties.feature +++ b/tests/acceptance/features/apiWebdavProperties2/getFileProperties.feature @@ -122,7 +122,7 @@ Feature: get file properties | old | | new | - @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 path And user "Brian" has been created with default attributes and without skeleton files @@ -143,7 +143,7 @@ Feature: get file properties | old | | new | - @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 path And group "grp1" has been created @@ -164,7 +164,7 @@ Feature: get file properties | old | | new | - @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 path And user "Alice" has created folder "/test" @@ -182,7 +182,7 @@ Feature: get file properties | old | | new | - @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 path And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiWebdavUpload1/uploadFile.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFile.feature index 9b320ccf67a9..fe645a6be32b 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFile.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFile.feature @@ -118,7 +118,7 @@ Feature: upload file | old | | new | - @issue-ocis-reva-15 + Scenario Outline: Uploading file to path with extension .part should not be possible Given using DAV path When user "Alice" uploads file "filesForUpload/textfile.txt" to "/textfile.part" using the WebDAV API diff --git a/tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature index f333e0a32196..f47378efe3d4 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-56 @newChunking @issue-ocis-1321 +@api @newChunking @issue-ocis-1321 Feature: upload file using new chunking As a user I want to be able to upload "large" files in chunks asynchronously diff --git a/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedName.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedName.feature index 8c62775a7cef..a945d07f55cc 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedName.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedName.feature @@ -8,7 +8,7 @@ Feature: users cannot upload a file to a blacklisted name Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @issue-ocis-reva-15 + Scenario Outline: upload a file to a filename that is banned by default Given using DAV path When user "Alice" uploads file with content "uploaded content" to ".htaccess" using the WebDAV API @@ -19,7 +19,7 @@ Feature: users cannot upload a file to a blacklisted name | old | | new | - @issue-ocis-reva-54 + Scenario Outline: upload a file to a banned filename Given using DAV path And the administrator has updated system config key "blacklisted_files" with value '["blacklisted-file.txt",".htaccess"]' and type "json" @@ -31,7 +31,7 @@ Feature: users cannot upload a file to a blacklisted name | old | | new | - @issue-ocis-reva-54 + Scenario Outline: upload a file to a filename that matches (or not) blacklisted_files_regex Given using DAV path And user "Alice" has created folder "FOLDER" diff --git a/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature index 6c1c5438878f..6237303f322e 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-56 @newChunking @issue-ocis-1321 +@api @newChunking @issue-ocis-1321 Feature: users cannot upload a file to a blacklisted name using new chunking As an administrator I want to be able to prevent users from uploading files to specified file names diff --git a/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectory.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectory.feature index 6be85afddc7b..d6fa240d6065 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectory.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectory.feature @@ -8,7 +8,7 @@ Feature: users cannot upload a file to or into an excluded directory Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @issue-ocis-reva-54 + Scenario Outline: upload a file to an excluded directory name Given using DAV path And the administrator has updated system config key "excluded_directories" with value '[".github"]' and type "json" @@ -20,7 +20,7 @@ Feature: users cannot upload a file to or into an excluded directory | old | | new | - @issue-ocis-reva-54 + Scenario Outline: upload a file to an excluded directory name inside a parent directory Given using DAV path And user "Alice" has created folder "FOLDER" @@ -34,7 +34,7 @@ Feature: users cannot upload a file to or into an excluded directory | old | | new | - @issue-ocis-reva-54 + Scenario Outline: upload a file to a filename that matches (or not) excluded_directories_regex Given using DAV path And user "Alice" has created folder "FOLDER" diff --git a/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature index 617781c4afd6..a6916bc9d7b4 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-56 @newChunking @issue-ocis-1321 +@api @newChunking @issue-ocis-1321 Feature: users cannot upload a file to or into an excluded directory using new chunking As an administrator I want to be able to exclude directories (folders) from being processed. Any attempt to upload a file to one of those names should be refused. diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature index 2a7a73d3cff7..c60b00e20939 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-56 @newChunking @issue-ocis-1321 +@api @newChunking @issue-ocis-1321 Feature: users cannot upload a file to a blacklisted name using new chunking As an administrator I want to be able to prevent users from uploading files to specified file names diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature index fac24f3a2b1c..09db9dee0716 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-15 +@api Feature: users cannot upload a file to a blacklisted name using old chunking As an administrator I want to be able to prevent users from uploading files to specified file names diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunkingOc10Issue36645.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunkingOc10Issue36645.feature index 7053b0eeec7e..5ddf3ea3a0ee 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunkingOc10Issue36645.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunkingOc10Issue36645.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-15 +@api Feature: users cannot upload a file to a blacklisted name using old chunking As an administrator I want to be able to prevent users from uploading files to specified file names diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature index 539a42ad3479..3a061e00dee7 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-56 @newChunking @issue-ocis-1321 +@api @newChunking @issue-ocis-1321 Feature: users cannot upload a file to or into an excluded directory using new chunking As an administrator I want to be able to exclude directories (folders) from being processed. Any attempt to upload a file to one of those names should be refused. diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature index b86c037efe84..92e3e8edc425 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-15 +@api Feature: users cannot upload a file to or into an excluded directory using old chunking As an administrator I want to be able to exclude directories (folders) from being processed. Any attempt to upload a file to one of those names should be refused. diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunkingOc10Issue36645.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunkingOc10Issue36645.feature index d151d045a3ed..77b6a5b6f26e 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunkingOc10Issue36645.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunkingOc10Issue36645.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-15 +@api Feature: users cannot upload a file to or into an excluded directory using old chunking As an administrator I want to be able to exclude directories (folders) from being processed. Any attempt to upload a file to one of those names should be refused. diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingNewChunking.feature index e88e13f52876..8aec8d147ee9 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-56 @newChunking @issue-ocis-1321 +@api @newChunking @issue-ocis-1321 Feature: upload file using new chunking As a user I want to be able to upload "large" files in chunks diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingOldChunking.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingOldChunking.feature index c8ce710ab972..5da112780948 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingOldChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingOldChunking.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-17 +@api Feature: upload file using old chunking As a user I want to be able to upload "large" files in chunks diff --git a/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingOldChunkingOc10Issue36115.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingOldChunkingOc10Issue36115.feature index f39bbd7101b5..77dfe7cacdf9 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingOldChunkingOc10Issue36115.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingOldChunkingOc10Issue36115.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-17 +@api Feature: upload file using old chunking As a user I want to be able to upload "large" files in chunks From ff4d4d02be35ea9bc4c3c42015938ba41eb7bef6 Mon Sep 17 00:00:00 2001 From: Roshan Lamichhane Date: Mon, 6 Feb 2023 12:28:51 +0545 Subject: [PATCH 2/2] Removed more issue-ocis-* tags --- .../createShareReceivedInMultipleWays.feature | 8 +++--- ...eWhenShareWithOnlyMembershipGroups.feature | 4 +-- .../createShareWithDisabledUser.feature | 2 +- .../createShareToRootFolder.feature | 2 +- .../createShareToSharesFolder.feature | 16 ++++++------ .../deleteShareFromShares.feature | 4 +-- .../acceptShares.feature | 2 +- .../acceptShares.feature | 15 +++-------- .../moveReceivedShare.feature | 26 +++++++++---------- .../getWebDAVSharePermissions.feature | 8 +++--- .../changingPublicLinkShare.feature | 13 ---------- .../createPublicLinkShare.feature | 12 --------- .../updatePublicLinkShare.feature | 7 ----- .../uploadToPublicLinkShare.feature | 11 -------- .../reShareSubfolder.feature | 6 ++--- .../updateShare.feature | 18 ++++++------- .../apiTrashbin/trashbinFilesFolders.feature | 6 ++--- .../features/apiVersions/fileVersions.feature | 4 +-- .../copyFileFolder.feature | 2 -- .../apiWebdavMove1/moveFolder.feature | 2 +- .../apiWebdavOperations/listFiles.feature | 4 --- .../apiWebdavOperations/propfind.feature | 2 +- .../apiWebdavOperations/search.feature | 4 +-- .../apiWebdavPreviews/previews.feature | 2 +- .../apiWebdavProperties1/copyFile.feature | 26 +++++++++---------- .../cliMain/transferOwnership.feature | 1 - 26 files changed, 74 insertions(+), 133 deletions(-) diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature index 184c0cd04fdd..6a22143408ba 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature @@ -38,7 +38,7 @@ Feature: share resources where the sharee receives the share in multiple ways | 1 | 100 | /Shares/textfile0 (2).txt | | 2 | 200 | /Shares/textfile0 (2).txt | - @issue-ocis-1289 + Scenario Outline: Share of folder and sub-folder to same user Given using OCS API version "" And group "grp4" has been created @@ -63,7 +63,7 @@ Feature: share resources where the sharee receives the share in multiple ways | 1 | 100 | /CHILD | | 2 | 200 | /CHILD | - @issue-ocis-2021 + Scenario Outline: sharing subfolder when parent already shared Given using OCS API version "" And group "grp1" has been created @@ -80,7 +80,7 @@ Feature: share resources where the sharee receives the share in multiple ways | 1 | 100 | /sub | | 2 | 200 | /sub | - @issue-ocis-2021 + Scenario Outline: sharing subfolder when parent already shared with group of sharer Given using OCS API version "" And group "grp0" has been created @@ -395,7 +395,6 @@ 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 Examples: | path | | /child1 | @@ -430,7 +429,6 @@ 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 Examples: | path | | /child1 | diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature index f5c2e7323f54..35eef4364ccd 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature @@ -6,7 +6,7 @@ Feature: cannot share resources outside the group when share with membership gro And auto-accept shares has been disabled And user "Alice" has been created with default attributes and without skeleton files - @issue-ocis-1328 + Scenario Outline: sharer should not be able to share a folder to a group which he/she is not member of when share with only member group is enabled Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -66,7 +66,7 @@ Feature: cannot share resources outside the group when share with membership gro | 1 | 100 | | 2 | 200 | - @issue-ocis-1328 + Scenario Outline: sharer should not be able to share a file to a group which he/she is not member of when share with only member group is enabled Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature index 365d81730f37..ffaf099d882b 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature @@ -7,7 +7,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 + Scenario Outline: Creating a new share with a disabled user Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiShareManagementBasicToRoot/createShareToRootFolder.feature b/tests/acceptance/features/apiShareManagementBasicToRoot/createShareToRootFolder.feature index ae08ce23a80b..74355a4a0583 100644 --- a/tests/acceptance/features/apiShareManagementBasicToRoot/createShareToRootFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToRoot/createShareToRootFolder.feature @@ -563,7 +563,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-719 + Scenario Outline: Creating a share of a renamed file when another share exists Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature index 0c22d511df73..e8542fc1cfb2 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature @@ -132,7 +132,7 @@ Feature: sharing | 1 | 200 | | 2 | 400 | - @issue-ocis-2133 + Scenario Outline: Creating a share of a folder with a user, the default permissions are all permissions(31) Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -294,7 +294,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-2201 + Scenario Outline: sharing subfolder of already shared folder, GET result is correct Given using OCS API version "" And these users have been created with default attributes and without skeleton files: @@ -653,7 +653,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-903 + Scenario Outline: shares to a deleted user should not be listed as shares for the sharer Given using 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 + Scenario Outline: Creating a share of a renamed file when another share exists Given using 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 + Scenario Outline: Sharing a same file twice to the same group is not possible Given using OCS API version "" And group "grp1" has been created @@ -724,7 +724,7 @@ Feature: sharing | 1 | 200 | | 2 | 403 | - @issue-ocis-2215 + Scenario Outline: Sharing the shares folder to users is not possible Given using 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 + Scenario Outline: Sharing the shares folder to groups is not possible Given using 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 + Scenario Outline: Sharing the shares folder as public link is not possible Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature b/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature index 7497376181da..20d21f05ec2f 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature @@ -198,7 +198,7 @@ Feature: sharing | /shared | 1 | 200 | /Shares/shared | /Shares/shared | | /shared | 2 | 404 | /Shares/shared | /Shares/shared | - @issue-ocis-720 + Scenario Outline: request PROPFIND after sharer deletes the collaborator Given using OCS API version "" And user "Alice" has shared file "textfile0.txt" with user "Brian" @@ -213,7 +213,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-1229 + Scenario Outline: delete a share with wrong authentication Given using OCS API version "" And user "Alice" has shared file "textfile0.txt" with user "Brian" diff --git a/tests/acceptance/features/apiShareManagementToRoot/acceptShares.feature b/tests/acceptance/features/apiShareManagementToRoot/acceptShares.feature index 739c9d14af90..0ba909ac1079 100644 --- a/tests/acceptance/features/apiShareManagementToRoot/acceptShares.feature +++ b/tests/acceptance/features/apiShareManagementToRoot/acceptShares.feature @@ -795,7 +795,7 @@ Feature: accept/decline shares coming from internal users | /PARENT (2)/ | And the content of file "/PARENT/abc.txt" for user "David" should be "uploaded content" - @issue-ocis-765 + Scenario: shares exist after restoring already shared file to a previous version Given 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" diff --git a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature index ecd2f315521d..9324709d4edb 100644 --- a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature +++ b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature @@ -59,7 +59,6 @@ Feature: accept/decline shares coming from internal users | path | | | | | - @issue-ocis-2540 Examples: | pending_share_path_1 | pending_share_path_2 | | /Shares/PARENT/ | /Shares/textfile0.txt | @@ -82,7 +81,6 @@ Feature: accept/decline shares coming from internal users | path | | | | | - @issue-ocis-2540 Examples: | pending_share_path_1 | pending_share_path_2 | | /Shares/PARENT/ | /Shares/textfile0.txt | @@ -208,7 +206,6 @@ Feature: accept/decline shares coming from internal users | path | | | | | - @issue-ocis-2540 Examples: | declined_share_path_1 | declined_share_path_2 | | /Shares/PARENT/ | /Shares/textfile0.txt | @@ -231,7 +228,6 @@ Feature: accept/decline shares coming from internal users | path | | | | | - @issue-ocis-2540 Examples: | declined_share_path_1 | declined_share_path_2 | | /Shares/PARENT/ | /Shares/textfile0.txt | @@ -269,12 +265,11 @@ Feature: accept/decline shares coming from internal users | path | | /Shares/PARENT/ | | /Shares/textfile0.txt | - @issue-ocis-2540 Examples: | pending_share_path_1 | pending_share_path_2 | | /Shares/PARENT/ | /Shares/textfile0.txt | - @issue-ocis-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" @@ -303,7 +298,6 @@ Feature: accept/decline shares coming from internal users | path | | | And the sharing API should report that no shares are shared with user "Alice" - @issue-ocis-2540 Examples: | pending_share_path | | /Shares/PARENT/ | @@ -514,7 +508,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 + 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" @@ -523,7 +517,6 @@ 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 | | | - @issue-ocis-2540 Examples: | declined_share_path | | /Shares/PARENT | @@ -539,7 +532,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 + 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" @@ -604,7 +597,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 + 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" diff --git a/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature b/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature index ae07a87635fe..3a886aea46ba 100644 --- a/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature +++ b/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature @@ -11,7 +11,7 @@ Feature: sharing | Brian | | Carol | - @issue-ocis-2141 + Scenario: Keep usergroup shares (#22143) Given group "grp1" has been created And user "Brian" has been added to group "grp1" @@ -44,7 +44,7 @@ Feature: sharing And user "Brian" should see the following elements | /Shares/new/| - @issue-ocis-2141 + Scenario: keep user shared file name same after one of recipient has renamed the file Given user "Alice" has uploaded file with content "foo" to "/sharefile.txt" And user "Alice" has shared file "/sharefile.txt" with user "Brian" @@ -70,7 +70,7 @@ Feature: sharing And as "Alice" file "/sharefile.txt" should exist And as "Brian" file "/Shares/sharefile.txt" should exist - @issue-ocis-2141 + Scenario: keep user shared file directory same in respect to respective user if one of the recipient has moved the file Given user "Alice" has uploaded file with content "foo" to "/sharefile.txt" And user "Alice" has shared file "/sharefile.txt" with user "Brian" @@ -84,7 +84,7 @@ Feature: sharing And as "Alice" file "/sharefile.txt" should exist And as "Brian" file "/Shares/sharefile.txt" should exist - @issue-ocis-2146 + Scenario Outline: move folder inside received folder with special characters Given group "grp1" has been created And user "Carol" has been added to group "grp1" @@ -109,7 +109,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 + Scenario: receiver renames a received share with share, read, change permissions Given user "Alice" has created folder "folderToShare" And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/folderToShare/fileInside" @@ -141,7 +141,7 @@ Feature: sharing And as "Alice" file "/folderToShare/renamedFile" should exist But as "Alice" file "/folderToShare/fileInside" should not exist - @issue-ocis-2141 + Scenario: receiver tries to rename a received share with share, read permissions Given user "Alice" has created folder "folderToShare" And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/folderToShare/fileInside" @@ -215,7 +215,7 @@ Feature: sharing And as "Brian" folder "/Shares/myFolder" should exist But as "Alice" folder "myFolder" should not exist - @issue-ocis-2141 + Scenario: receiver renames a received file share with read,update,share permissions in group sharing Given group "grp1" has been created And user "Brian" has been added to group "grp1" @@ -239,7 +239,7 @@ Feature: sharing And as "Brian" file "/Shares/newFile.txt" should exist But as "Alice" file "/Shares/newFile.txt" should not exist - @issue-ocis-2141 + Scenario: receiver renames a received folder share with share, read, change permissions in group sharing Given group "grp1" has been created And user "Alice" has created folder "PARENT" @@ -263,7 +263,7 @@ Feature: sharing And as "Brian" folder "/Shares/myFolder" should exist But as "Alice" folder "/Shares/myFolder" should not exist - @issue-ocis-2141 + Scenario: receiver renames a received file share with share, read permissions in group sharing Given group "grp1" has been created And user "Brian" has been added to group "grp1" @@ -287,7 +287,7 @@ Feature: sharing And as "Brian" file "/Shares/newFile.txt" should exist But as "Alice" file "/Shares/newFile.txt" should not exist - @issue-ocis-2141 + Scenario: receiver renames a received folder share with share, read permissions in group sharing Given group "grp1" has been created And user "Alice" has created folder "PARENT" @@ -311,7 +311,7 @@ Feature: sharing And as "Brian" folder "/Shares/myFolder" should exist But as "Alice" folder "/Shares/myFolder" should not exist - @issue-ocis-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" @@ -334,7 +334,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 + 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" @@ -359,7 +359,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 + Scenario: receiver moves file within a received folder to new folder Given user "Alice" has created folder "folderToShare" And user "Brian" has created folder "FOLDER" diff --git a/tests/acceptance/features/apiShareOperationsToShares2/getWebDAVSharePermissions.feature b/tests/acceptance/features/apiShareOperationsToShares2/getWebDAVSharePermissions.feature index 5a83c61f38a7..ef2fa4cb62b0 100644 --- a/tests/acceptance/features/apiShareOperationsToShares2/getWebDAVSharePermissions.feature +++ b/tests/acceptance/features/apiShareOperationsToShares2/getWebDAVSharePermissions.feature @@ -62,7 +62,7 @@ Feature: sharing | old | | new | - @issue-ocis-2213 + Scenario Outline: Correct webdav share-permissions for received file with edit permissions but no reshare permissions Given using DAV path And user "Alice" has uploaded file with content "foo" to "/tmp.txt" @@ -77,7 +77,7 @@ Feature: sharing | old | | new | - @issue-ocis-2213 + Scenario Outline: Correct webdav share-permissions for received group shared file with edit permissions but no reshare permissions Given using DAV path And group "grp1" has been created @@ -99,7 +99,7 @@ Feature: sharing | old | | new | - @issue-ocis-2213 + Scenario Outline: Correct webdav share-permissions for received file with reshare permissions but no edit permissions Given using DAV path And user "Alice" has uploaded file with content "foo" to "/tmp.txt" @@ -187,7 +187,7 @@ Feature: sharing | old | | new | - @issue-ocis-2213 + Scenario Outline: Correct webdav share-permissions for received folder with all permissions but edit Given using DAV path And user "Alice" has created folder "/tmp" diff --git a/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature index cea7ebc76599..f793b4b040ce 100644 --- a/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature @@ -18,7 +18,6 @@ Feature: changing a public link share Then the HTTP status code should be "" And as "Alice" file "PARENT/parent.txt" exist - @issue-ocis-2079 Examples: | permissions | http-status-code | should-or-not | public-webdav-api-version | | read,update,create | 403 | should | old | @@ -40,7 +39,6 @@ Feature: changing a public link share And as "Alice" file "/PARENT/parent.txt" should exist And as "Alice" file "/PARENT/newparent.txt" should not exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -60,7 +58,6 @@ Feature: changing a public link share And as "Alice" file "/PARENT/parent.txt" should not exist And as "Alice" file "/PARENT/newparent.txt" should exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -75,7 +72,6 @@ Feature: changing a public link share Then the HTTP status code should be "403" And as "Alice" file "/PARENT/lorem.txt" should not exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -94,7 +90,6 @@ Feature: changing a public link share Then the HTTP status code should be "201" And the content of file "PARENT/lorem.txt" for user "Alice" should be "test" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -114,7 +109,6 @@ Feature: changing a public link share Then the HTTP status code should be "401" And as "Alice" file "PARENT/parent.txt" should exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -130,7 +124,6 @@ Feature: changing a public link share Then the HTTP status code should be "204" And as "Alice" file "PARENT/parent.txt" should not exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -151,7 +144,6 @@ Feature: changing a public link share And as "Alice" file "/PARENT/newparent.txt" should not exist And as "Alice" file "/PARENT/parent.txt" should exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -168,7 +160,6 @@ Feature: changing a public link share And as "Alice" file "/PARENT/newparent.txt" should exist And as "Alice" file "/PARENT/parent.txt" should not exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -184,7 +175,6 @@ Feature: changing a public link share Then the HTTP status code should be "401" And as "Alice" file "/PARENT/lorem.txt" should not exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -200,7 +190,6 @@ Feature: changing a public link share Then the HTTP status code should be "201" And as "Alice" file "/PARENT/lorem.txt" should exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -216,7 +205,6 @@ Feature: changing a public link share And as "Alice" file "/PARENT/parent.txt" should exist And as "Alice" file "/PARENT/newparent.txt" should not exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -235,7 +223,6 @@ Feature: changing a public link share Then the HTTP status code should be "403" And as "Alice" file "PARENT/parent.txt" should exist - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | diff --git a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature index a501eccd881e..3321b524a272 100644 --- a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature @@ -30,7 +30,6 @@ 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-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -158,7 +157,6 @@ 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-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -261,7 +259,6 @@ 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-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -277,7 +274,6 @@ Feature: create a public link share | permissions | read,create | Then the OCS status code should be "" - @issue-ocis-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 403 | @@ -325,7 +321,6 @@ Feature: create a public link share | permissions | read,update,create | Then the OCS status code should be "" - @issue-ocis-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 403 | @@ -363,7 +358,6 @@ 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 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -385,7 +379,6 @@ 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 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -415,7 +408,6 @@ Feature: create 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 "long file" 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 "long file" - @issue-ocis-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -434,7 +426,6 @@ Feature: create a public link share And the public should be able to download file "/randomfile.txt" from inside the last public link shared folder using the old public WebDAV API without password and the content should be "Random data" And the public should be able to download file "/randomfile.txt" from inside the last public link shared folder using the new public WebDAV API without password and the content should be "Random data" - @issue-ocis-2079 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -472,7 +463,6 @@ Feature: create 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 Examples: | ocs_api_version | ocs_status_code | http_status_code | | 1 | 100 | 200 | @@ -488,7 +478,6 @@ Feature: create a public link share When user "Alice" deletes folder "PARENT" using the WebDAV API And the public download of file "/parent.txt" from inside the last public link shared folder using the public WebDAV API should fail with HTTP status code "404" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -509,7 +498,6 @@ Feature: create a public link share Then the value of the item "//s:message" in the response should be "" And the HTTP status code should be "404" - @issue-ocis-2079 Examples: | public-webdav-api-version | response | | old | | diff --git a/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature index 4795e7e450a8..b6b369d871c6 100644 --- a/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature @@ -136,7 +136,6 @@ 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 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -157,7 +156,6 @@ 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 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -343,7 +341,6 @@ 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 Examples: | ocs_api_version | http_status_code | | 1 | 200 | @@ -367,7 +364,6 @@ 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 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -392,7 +388,6 @@ 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 Examples: | ocs_api_version | http_status_code | | 1 | 200 | @@ -417,7 +412,6 @@ 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 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -463,7 +457,6 @@ Feature: update a public link share And as "Alice" file "PARENT/CHILD/child.txt" should not exist And as "Alice" file "PARENT/parent.txt" should not exist - @issue-ocis-2079 Examples: | ocs_api_version | public-webdav-api-version | | 1 | old | diff --git a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature index 436d326c09ac..26060d34eefe 100644 --- a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature @@ -44,7 +44,6 @@ Feature: upload to a public link share When the public uploads file "test.txt" with content "test" using the public WebDAV API And the HTTP status code should be "404" - @issue-ocis-2079 Examples: | dav-path | public-webdav-api-version | | old | old | @@ -64,7 +63,6 @@ Feature: upload to a public link share When the public uploads file "test.txt" with content "test" using the public WebDAV API And the HTTP status code should be "403" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -85,7 +83,6 @@ Feature: upload to a public link share And the following headers should match these regular expressions | ETag | /^"[a-f0-9:\.]{1,32}"$/ | - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -101,7 +98,6 @@ 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" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -117,7 +113,6 @@ 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" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -132,7 +127,6 @@ Feature: upload to a public link share When the public uploads file "test.txt" with content "test-file" using the public WebDAV API Then the HTTP status code should be "507" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -151,7 +145,6 @@ Feature: upload to a public link share When the public uploads file "test.txt" with content "test-file" using the public WebDAV API Then the HTTP status code should be "507" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -170,7 +163,6 @@ Feature: upload to a public link share When the public uploads file "test.txt" with content "test-file" using the public WebDAV API Then the HTTP status code should be "403" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -185,7 +177,6 @@ Feature: upload to a public link share When the public uploads file "test.txt" with content "test-file" using the public WebDAV API And the HTTP status code should be "403" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -205,7 +196,6 @@ 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" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | @@ -223,7 +213,6 @@ 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" - @issue-ocis-2079 Examples: | public-webdav-api-version | | old | diff --git a/tests/acceptance/features/apiShareReshareToShares2/reShareSubfolder.feature b/tests/acceptance/features/apiShareReshareToShares2/reShareSubfolder.feature index 326aaf8e13eb..3f62303a67ff 100644 --- a/tests/acceptance/features/apiShareReshareToShares2/reShareSubfolder.feature +++ b/tests/acceptance/features/apiShareReshareToShares2/reShareSubfolder.feature @@ -85,7 +85,7 @@ Feature: a subfolder of a received share can be reshared | 1 | 200 | 23 | 15 | | 2 | 404 | 23 | 15 | - @issue-ocis-2214 + Scenario Outline: User is allowed to update reshare of a sub-folder with less permissions Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files @@ -108,7 +108,7 @@ Feature: a subfolder of a received share can be reshared | 1 | 100 | /SUB | | 2 | 200 | /SUB | - @issue-ocis-2214 + Scenario Outline: User is allowed to update reshare of a sub-folder to the maximum allowed permissions Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files @@ -131,7 +131,7 @@ Feature: a subfolder of a received share can be reshared | 1 | 100 | /SUB | | 2 | 200 | /SUB | - @issue-ocis-2214 + Scenario Outline: User is not allowed to update reshare of a sub-folder with more permissions Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature b/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature index 6dc39c812555..555f9c769ab2 100644 --- a/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature +++ b/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature @@ -30,7 +30,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-1289 + Scenario Outline: keep group permissions in sync when the share is moved to another folder by the receiver and then the sharer updates the permissions Given using 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-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 "" And user "Brian" has been created with default attributes and without skeleton files @@ -112,7 +112,7 @@ Feature: sharing | 1 | 200 | | 2 | 400 | - @issue-ocis-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 "" And user "Brian" has been created with default attributes and without skeleton files @@ -134,7 +134,7 @@ Feature: sharing | 1 | 200 | create,delete | | 2 | 400 | create,delete | - @issue-ocis-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 "" And user "Brian" has been created with default attributes and without skeleton files @@ -298,7 +298,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-1328 + Scenario Outline: Forbid sharing with groups Given using OCS API version "" And group "grp1" has been created @@ -312,7 +312,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | - @issue-ocis-1328 + Scenario Outline: Editing share permission of existing share is forbidden when sharing with groups is forbidden Given using OCS API version "" And group "grp1" has been created @@ -337,7 +337,7 @@ Feature: sharing | 1 | 200 | | 2 | 400 | - @issue-ocis-1328 + Scenario Outline: Deleting group share is allowed when sharing with groups is forbidden Given using OCS API version "" And group "grp1" has been created @@ -356,7 +356,7 @@ Feature: sharing | 1 | 100 | 200 | | 2 | 200 | 404 | - @issue-ocis-1328 + Scenario Outline: user can update the role in an existing share after the system maximum expiry date has been reduced Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "yes" @@ -383,7 +383,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-1328 + Scenario Outline: user cannot concurrently update the role and date in an existing share after the system maximum expiry date has been reduced Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "yes" diff --git a/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature b/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature index 581871c3ef06..f92d9302e73a 100644 --- a/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature +++ b/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature @@ -288,7 +288,7 @@ Feature: files and folders exist in the trashbin after being deleted | dav-path | | new | - @issue-ocis-541 + Scenario Outline: deleted file has appropriate deletion time information Given using 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 @@ -300,7 +300,7 @@ Feature: files and folders exist in the trashbin after being deleted | dav-path | | new | - @issue-ocis-1547 + Scenario Outline: deleting files with special characters moves it to trashbin Given using DAV path And user "Alice" has uploaded the following files with content "special character file" @@ -332,7 +332,7 @@ Feature: files and folders exist in the trashbin after being deleted | dav-path | | new | - @issue-ocis-1547 + Scenario Outline: deleting folders with special characters moves it to trashbin Given using DAV path And user "Alice" has created the following folders diff --git a/tests/acceptance/features/apiVersions/fileVersions.feature b/tests/acceptance/features/apiVersions/fileVersions.feature index 3fee5ce58127..0e3a50348efc 100644 --- a/tests/acceptance/features/apiVersions/fileVersions.feature +++ b/tests/acceptance/features/apiVersions/fileVersions.feature @@ -410,7 +410,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 + 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" @@ -429,7 +429,7 @@ Feature: dav-versions Then the HTTP status code should be "207" And the number of versions should be "0" - @issue-ocis-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" diff --git a/tests/acceptance/features/apiWebdavEtagPropagation2/copyFileFolder.feature b/tests/acceptance/features/apiWebdavEtagPropagation2/copyFileFolder.feature index f3e4ee304c54..06835509f456 100644 --- a/tests/acceptance/features/apiWebdavEtagPropagation2/copyFileFolder.feature +++ b/tests/acceptance/features/apiWebdavEtagPropagation2/copyFileFolder.feature @@ -92,7 +92,6 @@ 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 Examples: | dav_version | | old | @@ -120,7 +119,6 @@ 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 Examples: | dav_version | | old | diff --git a/tests/acceptance/features/apiWebdavMove1/moveFolder.feature b/tests/acceptance/features/apiWebdavMove1/moveFolder.feature index d4eb7c0abd3e..983bf5101f36 100644 --- a/tests/acceptance/features/apiWebdavMove1/moveFolder.feature +++ b/tests/acceptance/features/apiWebdavMove1/moveFolder.feature @@ -97,7 +97,7 @@ Feature: move (rename) folder | new | /... | | new | /..upload | - @issue-ocis-3023 + Scenario Outline: Moving a folder into a sub-folder of itself Given using DAV path And user "Alice" has created folder "PARENT" diff --git a/tests/acceptance/features/apiWebdavOperations/listFiles.feature b/tests/acceptance/features/apiWebdavOperations/listFiles.feature index a6d00709b35f..94e9d7b5d232 100644 --- a/tests/acceptance/features/apiWebdavOperations/listFiles.feature +++ b/tests/acceptance/features/apiWebdavOperations/listFiles.feature @@ -173,7 +173,6 @@ Feature: list files | /simple-folder1/simple-folder2/welcome.txt | | /simple-folder1/simple-folder2/simple-folder3 | | /simple-folder1/simple-folder2/simple-folder3/simple-folder4 | - @issue-ocis-2079 Examples: | dav_version | | old | @@ -203,7 +202,6 @@ Feature: list files | /simple-folder1/simple-folder2 | | /simple-folder1/textfile0.txt | | /simple-folder1/simple-folder2/simple-folder3/simple-folder4 | - @issue-ocis-2079 Examples: | dav_version | | old | @@ -232,7 +230,6 @@ Feature: list files | /simple-folder1/simple-folder2/welcome.txt | | /simple-folder1/simple-folder2/simple-folder3 | | /simple-folder1/simple-folder2/simple-folder3/simple-folder4 | - @issue-ocis-2079 Examples: | dav_version | | old | @@ -339,7 +336,6 @@ Feature: list files And user "Alice" has created a public link share of folder "simple-folder" When the public lists the resources in the last created public link with depth "infinity" using the WebDAV API Then the HTTP status code should be "412" - @issue-ocis-2079 Examples: | dav_version | | old | diff --git a/tests/acceptance/features/apiWebdavOperations/propfind.feature b/tests/acceptance/features/apiWebdavOperations/propfind.feature index 574be079d731..9fce1bd91ff0 100644 --- a/tests/acceptance/features/apiWebdavOperations/propfind.feature +++ b/tests/acceptance/features/apiWebdavOperations/propfind.feature @@ -1,7 +1,7 @@ @api Feature: PROPFIND - @issue-ocis-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 "" with "PROPFIND" using basic auth diff --git a/tests/acceptance/features/apiWebdavOperations/search.feature b/tests/acceptance/features/apiWebdavOperations/search.feature index c2f0da0e47d1..98703a7392d7 100644 --- a/tests/acceptance/features/apiWebdavOperations/search.feature +++ b/tests/acceptance/features/apiWebdavOperations/search.feature @@ -145,7 +145,7 @@ Feature: Search | old | | new | - @issue-ocis-4712 + Scenario Outline: report extra properties in search entries for a file Given using DAV path When user "Alice" searches for "upload" using the WebDAV API requesting these properties: @@ -173,7 +173,7 @@ Feature: Search | old | | new | - @issue-ocis-4712 + Scenario Outline: report extra properties in search entries for a folder Given using DAV path When user "Alice" searches for "upload" using the WebDAV API requesting these properties: diff --git a/tests/acceptance/features/apiWebdavPreviews/previews.feature b/tests/acceptance/features/apiWebdavPreviews/previews.feature index 3b97bf72d9a6..05d063e53b65 100644 --- a/tests/acceptance/features/apiWebdavPreviews/previews.feature +++ b/tests/acceptance/features/apiWebdavPreviews/previews.feature @@ -194,7 +194,7 @@ Feature: previews of files downloaded through the webdav API Then the HTTP status code should be "204" And as user "Brian" the preview of "/parent.txt" with width "32" and height "32" should have been changed - @issue-ocis-2538 + Scenario: when owner updates a shared file, previews for sharee are also updated (to shared folder) Given the administrator has set the default folder for received shares to "Shares" And auto-accept shares has been disabled diff --git a/tests/acceptance/features/apiWebdavProperties1/copyFile.feature b/tests/acceptance/features/apiWebdavProperties1/copyFile.feature index ff33deba38bf..5cad3b520b36 100644 --- a/tests/acceptance/features/apiWebdavProperties1/copyFile.feature +++ b/tests/acceptance/features/apiWebdavProperties1/copyFile.feature @@ -205,7 +205,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a file over the top of an existing folder received as a user share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -224,7 +224,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a folder over the top of an existing file received as a user share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -242,7 +242,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a folder into another folder at different level which is received as a user share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -265,7 +265,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a file into a folder at different level received as a user share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -290,7 +290,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a file into a file at different level received as a user share Given using 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 + Scenario Outline: copy a folder into a file at different level received as a user share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -338,7 +338,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a file over the top of an existing folder received as a group share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -360,7 +360,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a folder over the top of an existing file received as a group share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -381,7 +381,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a folder into another folder at different level which is received as a group share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -407,7 +407,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a file into a folder at different level received as a group share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -435,7 +435,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a file into a file at different level received as a group share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -462,7 +462,7 @@ Feature: copy file | old | | new | - @issue-ocis-1239 + Scenario Outline: copy a folder into a file at different level received as a group share Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -754,7 +754,7 @@ Feature: copy file | old | | new | - @issue-ocis-3023 + Scenario Outline: Copying a folder into a sub-folder of itself Given using DAV path And user "Alice" has created folder "/PARENT" diff --git a/tests/acceptance/features/cliMain/transferOwnership.feature b/tests/acceptance/features/cliMain/transferOwnership.feature index 91e3da563a91..147a560fb12d 100644 --- a/tests/acceptance/features/cliMain/transferOwnership.feature +++ b/tests/acceptance/features/cliMain/transferOwnership.feature @@ -204,7 +204,6 @@ Feature: transfer-ownership Then the command should have been successful And the public should be able to download the last publicly shared file using the public WebDAV API without a password and the content should be "Random data" - @issue-ocis-2079 Examples: | webdav_api_version | | old |