From 85bd5e912a5e605a5b001aeba48a6ed775185c7f Mon Sep 17 00:00:00 2001 From: Roshan Lamichhane Date: Mon, 6 Feb 2023 12:39:01 +0545 Subject: [PATCH 1/5] Removed issue-ocis-* tags from the end of lines --- .../features/apiMain/checksums.feature | 14 +++---- .../acceptance/features/apiMain/quota.feature | 20 +++++----- .../features/apiMain/userSync.feature | 2 +- .../createShareExpirationDate.feature | 2 +- .../createShareUniqueReceivedNames.feature | 2 +- ...hareDefaultFolderForReceivedShares.feature | 2 +- ...eWhenShareWithOnlyMembershipGroups.feature | 2 +- .../createShareWithDisabledUser.feature | 2 +- .../createShareToSharesFolder.feature | 10 ++--- .../deleteShareFromShares.feature | 2 +- .../acceptShares.feature | 8 ++-- .../moveReceivedShare.feature | 2 +- .../changingFilesShare.feature | 2 +- .../uploadToShare.feature | 2 +- .../createPublicLinkShare.feature | 2 +- .../reShareAsPublicLinkToSharesOldDav.feature | 2 +- .../uploadToPublicLinkShare.feature | 4 +- .../apiShareReshareToShares1/reShare.feature | 2 +- .../reShareChain.feature | 2 +- .../reShareDisabled.feature | 2 +- .../reShareSubfolder.feature | 4 +- ...eWhenShareWithOnlyMembershipGroups.feature | 2 +- .../reShareUpdate.feature | 2 +- .../reShareWithExpiryDate.feature | 2 +- ...eShareWithExpiryDateOc10Issue37013.feature | 2 +- .../updateShare.feature | 2 +- ...pdateShareGroupAndUserWithSameName.feature | 2 +- .../features/apiSharees/sharees.feature | 40 +++++++++---------- .../sharingNotifications.feature | 2 +- .../trashbinRestore.feature | 2 +- .../features/apiVersions/fileVersions.feature | 18 ++++----- .../lockBreakersGroups.feature | 2 +- .../uploadFileAsyncUsingNewChunking.feature | 2 +- ...acklistedNameAsyncUsingNewChunking.feature | 2 +- ...udedDirectoryAsyncUsingNewChunking.feature | 2 +- ...eToBlacklistedNameUsingNewChunking.feature | 2 +- ...oExcludedDirectoryUsingNewChunking.feature | 2 +- .../uploadFileUsingNewChunking.feature | 2 +- 38 files changed, 89 insertions(+), 89 deletions(-) diff --git a/tests/acceptance/features/apiMain/checksums.feature b/tests/acceptance/features/apiMain/checksums.feature index de68fc4c2968..59751de1077b 100644 --- a/tests/acceptance/features/apiMain/checksums.feature +++ b/tests/acceptance/features/apiMain/checksums.feature @@ -170,7 +170,7 @@ Feature: checksums | dav_version | checksum | | new | SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a | - @newChunking @issue-ocis-1321 + @newChunking 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" - @newChunking @issue-ocis-1321 + @newChunking 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 | - @newChunking @issue-ocis-1321 + @newChunking 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" - @newChunking @issue-ocis-1321 + @newChunking 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 | - @newChunking @issue-ocis-1321 + @newChunking 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 @@ -353,7 +353,7 @@ Feature: checksums | old | | new | - @newChunking @issue-ocis-1321 + @newChunking 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 @newChunking @issue-ocis-1321 + @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @newChunking 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" diff --git a/tests/acceptance/features/apiMain/quota.feature b/tests/acceptance/features/apiMain/quota.feature index f2004b38304a..3d817a21bb3f 100644 --- a/tests/acceptance/features/apiMain/quota.feature +++ b/tests/acceptance/features/apiMain/quota.feature @@ -12,7 +12,7 @@ Feature: quota When user "Alice" uploads file "filesForUpload/textfile.txt" to filenames based on "/testquota.txt" with all mechanisms except new chunking using the WebDAV API Then the HTTP status code of all upload responses should be "201" - @newChunking @issue-ocis-1321 + @newChunking Scenario: Uploading a file as owner having enough quota (new chunking) Given the quota of user "Alice" has been set to "10 MB" And using new DAV path @@ -26,7 +26,7 @@ Feature: quota Then the HTTP status code of all upload responses should be "507" And as "Alice" the files uploaded to "/testquota.txt" with all mechanisms except new chunking should not exist - @smokeTest @newChunking @issue-ocis-1321 + @smokeTest @newChunking Scenario: Uploading a file as owner having insufficient quota (new chunking) Given the quota of user "Alice" has been set to "10 B" And using new DAV path @@ -41,7 +41,7 @@ Feature: quota When user "Alice" overwrites from file "filesForUpload/textfile.txt" to file "/testquota.txt" with all mechanisms except new chunking using the WebDAV API Then the HTTP status code of all upload responses should be between "201" and "204" - @newChunking @issue-ocis-1321 + @newChunking Scenario: Overwriting a file as owner having enough quota (new chunking) Given user "Alice" has uploaded file with content "test" to "/testquota.txt" And the quota of user "Alice" has been set to "10 MB" @@ -57,7 +57,7 @@ Feature: quota Then the HTTP status code of all upload responses should be "507" And the content of file "/testquota.txt" for user "Alice" should be "test" - @newChunking @issue-ocis-1321 + @newChunking Scenario: Overwriting a file as owner having insufficient quota (new chunking) Given user "Alice" has uploaded file with content "test" to "/testquota.txt" And the quota of user "Alice" has been set to "10 B" @@ -78,7 +78,7 @@ Feature: quota When user "Brian" uploads file "filesForUpload/textfile.txt" to filenames based on "/testquota/testquota.txt" with all mechanisms except new chunking using the WebDAV API Then the HTTP status code of all upload responses should be "201" - @files_sharing-app-required @newChunking @issue-ocis-1321 + @files_sharing-app-required @newChunking Scenario: Uploading a file in received folder having enough quota (new chunking) Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/testquota" @@ -100,7 +100,7 @@ Feature: quota Then the HTTP status code of all upload responses should be "507" And as "Brian" the files uploaded to "/testquota/testquota.txt" with all mechanisms except new chunking should not exist - @files_sharing-app-required @newChunking @issue-ocis-1321 + @files_sharing-app-required @newChunking Scenario: Uploading a file in a received folder having insufficient quota (new chunking) Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/testquota" @@ -123,7 +123,7 @@ Feature: quota When user "Brian" overwrites from file "filesForUpload/textfile.txt" to file "/testquota/testquota.txt" with all mechanisms except new chunking using the WebDAV API Then the HTTP status code of all upload responses should be between "201" and "204" - @files_sharing-app-required @newChunking @issue-ocis-1321 + @files_sharing-app-required @newChunking Scenario: Overwriting a file in received folder having enough quota (new chunking) Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/testquota" @@ -147,7 +147,7 @@ Feature: quota Then the HTTP status code of all upload responses should be "507" And the content of file "/testquota/testquota.txt" for user "Alice" should be "test" - @files_sharing-app-required @newChunking @issue-ocis-1321 + @files_sharing-app-required @newChunking Scenario: Overwriting a file in received folder having insufficient quota (new chunking) Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/testquota" @@ -172,7 +172,7 @@ Feature: quota When user "Brian" overwrites from file "filesForUpload/textfile.txt" to file "/testquota.txt" with all mechanisms except new chunking using the WebDAV API Then the HTTP status code of all upload responses should be between "201" and "204" - @files_sharing-app-required @newChunking @issue-ocis-1321 + @files_sharing-app-required @newChunking Scenario: Overwriting a received file having enough quota (new chunking) Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "test" to "/testquota.txt" @@ -194,7 +194,7 @@ Feature: quota Then the HTTP status code of all upload responses should be "507" And the content of file "/testquota.txt" for user "Alice" should be "test" - @files_sharing-app-required @newChunking @issue-ocis-1321 + @files_sharing-app-required @newChunking Scenario: Overwriting a received file having insufficient quota (new chunking) Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "test" to "/testquota.txt" diff --git a/tests/acceptance/features/apiMain/userSync.feature b/tests/acceptance/features/apiMain/userSync.feature index 962e441a59c0..cebbfd1b1b27 100644 --- a/tests/acceptance/features/apiMain/userSync.feature +++ b/tests/acceptance/features/apiMain/userSync.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-1241 +@api Feature: Users sync Background: diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature b/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature index 315d32804675..193b9a8c7b5d 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 @issue-ocis-1250 +@api @files_sharing-app-required @issue-ocis-1328 Feature: a default expiration date can be specified for shares with users or groups Background: diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature b/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature index 5dc8a996be8f..ec2a8f367296 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature @@ -11,7 +11,7 @@ Feature: resources shared with the same name are received with unique names | Brian | | Carol | - @smokeTest @issue-ocis-2131 + @smokeTest Scenario Outline: unique target names for incoming shares Given user "Alice" has created folder "/foo" And user "Brian" has created folder "/foo" diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature index 6080180b09ac..ff9093513b79 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1327 +@api @files_sharing-app-required Feature: shares are received in the default folder for received shares Background: diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature index 35eef4364ccd..a993f098ef9c 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: cannot share resources outside the group when share with membership groups is enabled Background: diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature index ffaf099d882b..83c213695832 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: share resources with a disabled user Background: diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature index e8542fc1cfb2..59fa31b39de8 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature @@ -36,7 +36,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @skipOnEncryptionType:user-keys @issue-32322 @issue-ocis-2133 + @smokeTest @skipOnEncryptionType:user-keys @issue-32322 Scenario Outline: Creating a share of a file containing commas in the filename, with a user, the default permissions are read(1)+update(2)+can-share(16) Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -528,7 +528,7 @@ Feature: sharing | 1 | 100 | /Shares/textfile0.txt | | 2 | 200 | /Shares/textfile0.txt | - @skipOnFilesClassifier @issue-files-classifier-291 @issue-ocis-2146 + @skipOnFilesClassifier @issue-files-classifier-291 Scenario: Share a file by multiple channels and download from sub-folder and direct file share Given these users have been created with default attributes and without skeleton files: | username | @@ -557,7 +557,7 @@ Feature: sharing And the content of file "/Shares/common/sub/textfile0.txt" for user "Brian" should be "BLABLABLA" plus end-of-line And the content of file "/common/sub/textfile0.txt" for user "Alice" should be "BLABLABLA" plus end-of-line - @issue-enterprise-3896 @issue-ocis-2201 + @issue-enterprise-3896 Scenario Outline: sharing back to resharer is allowed Given these users have been created with default attributes and without skeleton files: | username | @@ -578,7 +578,7 @@ Feature: sharing | pending_share_path | | /userOneFolder | - @issue-enterprise-3896 @issue-ocis-2201 + @issue-enterprise-3896 Scenario Outline: sharing back to original sharer is allowed Given these users have been created with default attributes and without skeleton files: | username | @@ -599,7 +599,7 @@ Feature: sharing | pending_share_path | | /userOneFolder | - @issue-enterprise-3896 @issue-ocis-2201 + @issue-enterprise-3896 Scenario Outline: sharing a subfolder to a user that already received parent folder share Given these users have been created with default attributes and without skeleton files: | username | diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature b/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature index 20d21f05ec2f..c961a2c4d466 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 @issue-ocis-1289 +@api @files_sharing-app-required @issue-ocis-1328 Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature index 9324709d4edb..7d4ddf338d92 100644 --- a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature +++ b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-1328 +@api @files_sharing-app-required @issue-ocis-1289 Feature: accept/decline shares coming from internal users As a user I want to have control of which received shares I accept @@ -85,7 +85,7 @@ Feature: accept/decline shares coming from internal users | pending_share_path_1 | pending_share_path_2 | | /Shares/PARENT/ | /Shares/textfile0.txt | - @smokeTest @issue-ocis-2131 + @smokeTest Scenario: accept a pending share Given user "Alice" has shared folder "/PARENT" with user "Brian" And user "Alice" has shared file "/textfile0.txt" with user "Brian" @@ -210,7 +210,7 @@ Feature: accept/decline shares coming from internal users | declined_share_path_1 | declined_share_path_2 | | /Shares/PARENT/ | /Shares/textfile0.txt | - @smokeTest @issue-ocis-2128 + @smokeTest Scenario Outline: decline an accepted share Given user "Alice" has shared folder "/PARENT" with user "Brian" And user "Alice" has shared file "/textfile0.txt" with user "Brian" @@ -521,7 +521,7 @@ Feature: accept/decline shares coming from internal users | declined_share_path | | /Shares/PARENT | - @issue-ocis-765 @issue-ocis-2131 + @issue-ocis-765 Scenario: shares exist after restoring already shared file to a previous version And user "Alice" has uploaded file with content "Test Content." to "/toShareFile.txt" And user "Alice" has uploaded file with content "Content Test Updated." to "/toShareFile.txt" diff --git a/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature b/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature index 3a886aea46ba..a12e0a5f5b11 100644 --- a/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature +++ b/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-1328 +@api @files_sharing-app-required @issue-ocis-1289 Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature b/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature index 6f099112469f..5fac1e995bde 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-1328 +@api @files_sharing-app-required @issue-ocis-1289 Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareOperationsToShares2/uploadToShare.feature b/tests/acceptance/features/apiShareOperationsToShares2/uploadToShare.feature index 45d8d73fd2d1..a3dd066571bc 100644 --- a/tests/acceptance/features/apiShareOperationsToShares2/uploadToShare.feature +++ b/tests/acceptance/features/apiShareOperationsToShares2/uploadToShare.feature @@ -252,7 +252,7 @@ Feature: sharing | old | | new | - @newChunking @issue-ocis-1321 + @newChunking Scenario: Uploading a file in to a shared folder without edit permissions Given using new DAV path And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature index 3321b524a272..73d6693e4770 100644 --- a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature @@ -35,7 +35,7 @@ Feature: create a public link share | 1 | 100 | | 2 | 200 | - @smokeTest @issue-ocis-2079 + @smokeTest Scenario Outline: Creating a new public link share of a file with password using the old public WebDAV API Given using OCS API version "" And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt" diff --git a/tests/acceptance/features/apiSharePublicLink2/reShareAsPublicLinkToSharesOldDav.feature b/tests/acceptance/features/apiSharePublicLink2/reShareAsPublicLinkToSharesOldDav.feature index fb44105c1de2..d3c3c351bd58 100644 --- a/tests/acceptance/features/apiSharePublicLink2/reShareAsPublicLinkToSharesOldDav.feature +++ b/tests/acceptance/features/apiSharePublicLink2/reShareAsPublicLinkToSharesOldDav.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-2079 +@api @files_sharing-app-required @public_link_share-feature-required Feature: reshare as public link As a user I want to create public link shares from files/folders shared with me diff --git a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature index 26060d34eefe..a69da8a5c2b4 100644 --- a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature @@ -6,7 +6,7 @@ Feature: upload to a public link share Given user "Alice" has been created with default attributes and without skeleton files And user "Alice" has created folder "FOLDER" - @smokeTest @issue-ocis-2079 + @smokeTest Scenario: Uploading same file to a public upload-only share multiple times via old API # The old API needs to have the header OC-Autorename: 1 set to do the autorename Given user "Alice" has created a public link share with settings @@ -218,7 +218,7 @@ Feature: upload to a public link share | old | | new | - @smokeTest @issue-ocis-2079 + @smokeTest Scenario: Uploading same file to a public upload-write and no edit and no overwrite share multiple times with old public API Given user "Alice" has created a public link share with settings | path | FOLDER | diff --git a/tests/acceptance/features/apiShareReshareToShares1/reShare.feature b/tests/acceptance/features/apiShareReshareToShares1/reShare.feature index 17b615b79f3e..26ccf50d262b 100644 --- a/tests/acceptance/features/apiShareReshareToShares1/reShare.feature +++ b/tests/acceptance/features/apiShareReshareToShares1/reShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareReshareToShares2/reShareChain.feature b/tests/acceptance/features/apiShareReshareToShares2/reShareChain.feature index 2e9e1a771cb2..c256283243e8 100644 --- a/tests/acceptance/features/apiShareReshareToShares2/reShareChain.feature +++ b/tests/acceptance/features/apiShareReshareToShares2/reShareChain.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-2141 +@api @files_sharing-app-required Feature: resharing can be done on a reshared resource Background: diff --git a/tests/acceptance/features/apiShareReshareToShares2/reShareDisabled.feature b/tests/acceptance/features/apiShareReshareToShares2/reShareDisabled.feature index 81d07a6a8727..04477a359ffe 100644 --- a/tests/acceptance/features/apiShareReshareToShares2/reShareDisabled.feature +++ b/tests/acceptance/features/apiShareReshareToShares2/reShareDisabled.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: resharing can be disabled Background: diff --git a/tests/acceptance/features/apiShareReshareToShares2/reShareSubfolder.feature b/tests/acceptance/features/apiShareReshareToShares2/reShareSubfolder.feature index 3f62303a67ff..f42ff346d2fe 100644 --- a/tests/acceptance/features/apiShareReshareToShares2/reShareSubfolder.feature +++ b/tests/acceptance/features/apiShareReshareToShares2/reShareSubfolder.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: a subfolder of a received share can be reshared Background: @@ -9,7 +9,7 @@ Feature: a subfolder of a received share can be reshared | Alice | | Brian | - @smokeTest @issue-ocis-2214 + @smokeTest Scenario Outline: User is allowed to reshare a sub-folder with the same 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/apiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature b/tests/acceptance/features/apiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature index 98bed0e7647d..337a23603b63 100644 --- a/tests/acceptance/features/apiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature +++ b/tests/acceptance/features/apiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-reva-194 @issue-ocis-1328 +@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-reva-194 Feature: resharing a resource with an expiration date Background: diff --git a/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature b/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature index d8447d45319c..982e7a669c09 100644 --- a/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature +++ b/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature index 5cbef9a893d3..0ea564fe72b1 100644 --- a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature +++ b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: resharing a resource with an expiration date Background: diff --git a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDateOc10Issue37013.feature b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDateOc10Issue37013.feature index c1e332f5da06..17380173358f 100644 --- a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDateOc10Issue37013.feature +++ b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDateOc10Issue37013.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1250 +@api @files_sharing-app-required Feature: resharing a resource with an expiration date Background: diff --git a/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature b/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature index 555f9c769ab2..421390398ed8 100644 --- a/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature +++ b/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature @@ -158,7 +158,7 @@ Feature: sharing | 1 | 200 | create,delete | | 2 | 400 | create,delete | - @skipOnFilesClassifier @issue-files-classifier-291 @toFixOnOCIS @issue-ocis-2201 + @skipOnFilesClassifier @issue-files-classifier-291 @toFixOnOCIS Scenario Outline: Share ownership change after moving a shared file outside of an outer share Given these users have been created with default attributes and without skeleton files: | username | diff --git a/tests/acceptance/features/apiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature b/tests/acceptance/features/apiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature index 090d8c2f3cc4..0a7fa8720764 100644 --- a/tests/acceptance/features/apiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature +++ b/tests/acceptance/features/apiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-1328 +@api @files_sharing-app-required @issue-ocis-1289 Feature: updating shares to users and groups that have the same name Background: diff --git a/tests/acceptance/features/apiSharees/sharees.feature b/tests/acceptance/features/apiSharees/sharees.feature index fde752d8a6e2..67292913d513 100644 --- a/tests/acceptance/features/apiSharees/sharees.feature +++ b/tests/acceptance/features/apiSharees/sharees.feature @@ -54,7 +54,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search only with group members - denied Given using OCS API version "" And parameter "shareapi_only_share_with_group_members" of app "core" has been set to "yes" @@ -100,7 +100,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search only with group members - no group as non-member Given using OCS API version "" And parameter "shareapi_only_share_with_group_members" of app "core" has been set to "yes" @@ -121,7 +121,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search only with membership groups - denied Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -141,7 +141,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search only with membership groups - denied but users match Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -162,7 +162,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search only with membership groups - allowed Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -183,7 +183,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search only with membership groups - allowed including users Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -205,7 +205,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search without exact match no iteration allowed Given using OCS API version "" And parameter "shareapi_allow_share_dialog_user_enumeration" of app "core" has been set to "no" @@ -225,7 +225,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search with exact match no iteration allowed Given using OCS API version "" And parameter "shareapi_allow_share_dialog_user_enumeration" of app "core" has been set to "no" @@ -246,7 +246,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Search with exact match group no iteration allowed Given using OCS API version "" And parameter "shareapi_allow_share_dialog_user_enumeration" of app "core" has been set to "no" @@ -267,7 +267,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Try to search for users and groups when in a group that is excluded from sharing (could match both users and groups) Given using OCS API version "" And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" @@ -288,7 +288,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Try to search for users and groups when in a group that is excluded from sharing (exact match to a user) Given using OCS API version "" And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" @@ -309,7 +309,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Try to search for users and groups when in a group that is excluded from sharing (exact match to a group) Given using OCS API version "" And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" @@ -449,7 +449,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Group sharees not returned when group sharing is disabled Given using OCS API version "" And parameter "shareapi_allow_group_sharing" of app "core" has been set to "no" @@ -495,7 +495,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Enumerate only group members - accept exact match from non-member groups Given using OCS API version "" And parameter "shareapi_share_dialog_user_enumeration_group_members" of app "core" has been set to "yes" @@ -516,7 +516,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: Enumerate only group members - only show partial results from member groups Given using OCS API version "" And parameter "shareapi_share_dialog_user_enumeration_group_members" of app "core" has been set to "yes" @@ -537,7 +537,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @skipOnLDAP @issue-ocis-1317 @issue-ocis-1328 + @skipOnLDAP @issue-ocis-1317 Scenario Outline: Enumerate only group members - only accept exact group match from non-memberships Given using OCS API version "" And group "ShareeGroupNonMember" has been created @@ -583,7 +583,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: empty search for sharees when search min length is set to 0 Given the administrator has updated system config key "user.search_min_length" with value "0" And user "sharee2" has been created with default attributes and without skeleton files @@ -609,7 +609,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: empty search for sharees when search min length is set to 2 Given the administrator has updated system config key "user.search_min_length" with value "2" And user "sharee2" has been created with default attributes and without skeleton files @@ -680,7 +680,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: search for sharees without search when min length is set to 0 Given the administrator has updated system config key "user.search_min_length" with value "0" And user "sharee2" has been created with default attributes and without skeleton files @@ -705,7 +705,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 @issue-ocis-1328 + @issue-ocis-1317 Scenario Outline: search for sharees without search when min length is set to 2 Given the administrator has updated system config key "user.search_min_length" with value "2" And user "sharee2" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiSharingNotificationsToShares/sharingNotifications.feature b/tests/acceptance/features/apiSharingNotificationsToShares/sharingNotifications.feature index e5ce35c0d3a2..a72ecc1dd306 100644 --- a/tests/acceptance/features/apiSharingNotificationsToShares/sharingNotifications.feature +++ b/tests/acceptance/features/apiSharingNotificationsToShares/sharingNotifications.feature @@ -1,4 +1,4 @@ -@api @app-required @notifications-app-required @files_sharing-app-required @issue-ocis-1328 +@api @app-required @notifications-app-required @files_sharing-app-required Feature: Display notifications when receiving a share As a user I want to see notifications about shares that have been offered to me diff --git a/tests/acceptance/features/apiTrashbinRestore/trashbinRestore.feature b/tests/acceptance/features/apiTrashbinRestore/trashbinRestore.feature index c0739b0c2971..ab7f7a5682c3 100644 --- a/tests/acceptance/features/apiTrashbinRestore/trashbinRestore.feature +++ b/tests/acceptance/features/apiTrashbinRestore/trashbinRestore.feature @@ -167,7 +167,7 @@ Feature: Restore deleted files/folders And as "Alice" the folder with original path "/local_storage/tmp/textfile0.txt" should not exist in the trashbin And the content of file "/local_storage/tmp/textfile0.txt" for user "Alice" should be "AA" - @local_storage @files_external-app-required @skipOnEncryptionType:user-keys @encryption-issue-42 @skip_on_objectstore @newChunking @issue-ocis-1321 + @local_storage @files_external-app-required @skipOnEncryptionType:user-keys @encryption-issue-42 @skip_on_objectstore @newChunking Scenario: Deleting an updated file into external storage moves it to the trashbin and can be restored with new chunking Given using new DAV path And the administrator has invoked occ command "files:scan --all" diff --git a/tests/acceptance/features/apiVersions/fileVersions.feature b/tests/acceptance/features/apiVersions/fileVersions.feature index 0e3a50348efc..f4b4736e7869 100644 --- a/tests/acceptance/features/apiVersions/fileVersions.feature +++ b/tests/acceptance/features/apiVersions/fileVersions.feature @@ -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 - @newChunking @issue-ocis-1321 + @newChunking 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 - @newChunking @issue-ocis-1321 + @newChunking 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 @@ -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 - @newChunking @issue-ocis-1321 + @newChunking 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 - @newChunking @issue-ocis-1321 + @newChunking 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 @@ -109,7 +109,7 @@ Feature: dav-versions Examples: | dav-path | status-code | | old | 201 | - @newChunking @issue-ocis-1321 + @newChunking Examples: | dav-path | status-code | | new | 204 | @@ -290,7 +290,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-1289 @issue-ocis-1321 + @files_sharing-app-required @issue-ocis-1289 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 @@ -308,7 +308,7 @@ Feature: dav-versions And the content of file "/sharingfolder/sharefile.txt" for user "Brian" should be "First content" And the content of file "/sharingfolder/sharefile.txt" for user "Carol" should be "First content" - @files_sharing-app-required @issue-ocis-1238 + @files_sharing-app-required Scenario Outline: Moving a file (with versions) into a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -335,7 +335,7 @@ Feature: dav-versions | old | Brian | | new | Brian | - @files_sharing-app-required @issue-ocis-1238 + @files_sharing-app-required Scenario Outline: Moving a file (with versions) out of a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -361,7 +361,7 @@ Feature: dav-versions | old | Brian | | new | Brian | - @files_sharing-app-required @issue-ocis-1238 + @files_sharing-app-required Scenario: Receiver tries to get file versions of unshared file from the sharer Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" diff --git a/tests/acceptance/features/apiWebdavLocksUnlock/lockBreakersGroups.feature b/tests/acceptance/features/apiWebdavLocksUnlock/lockBreakersGroups.feature index b7a70d223c68..ae2939993ab6 100644 --- a/tests/acceptance/features/apiWebdavLocksUnlock/lockBreakersGroups.feature +++ b/tests/acceptance/features/apiWebdavLocksUnlock/lockBreakersGroups.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-2413 +@api Feature: UNLOCK locked items Background: diff --git a/tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature index f47378efe3d4..fa3ce9f7b0ad 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @newChunking @issue-ocis-1321 +@api @newChunking 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/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature index 6237303f322e..85a30646b997 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @newChunking @issue-ocis-1321 +@api @newChunking 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/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature index a6916bc9d7b4..d7441a0b3f28 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @newChunking @issue-ocis-1321 +@api @newChunking 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 c60b00e20939..72e6177131b8 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @newChunking @issue-ocis-1321 +@api @newChunking 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/uploadFileToExcludedDirectoryUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature index 3a061e00dee7..de3831023f1e 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @newChunking @issue-ocis-1321 +@api @newChunking 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/uploadFileUsingNewChunking.feature b/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingNewChunking.feature index 8aec8d147ee9..1b727a90f1e9 100644 --- a/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingNewChunking.feature +++ b/tests/acceptance/features/apiWebdavUpload2/uploadFileUsingNewChunking.feature @@ -1,4 +1,4 @@ -@api @newChunking @issue-ocis-1321 +@api @newChunking Feature: upload file using new chunking As a user I want to be able to upload "large" files in chunks From 9841452a63cab54ebfc79e07fc0d5dbbc05c54e3 Mon Sep 17 00:00:00 2001 From: Roshan Lamichhane Date: Mon, 6 Feb 2023 12:43:37 +0545 Subject: [PATCH 2/5] Removed issue-ocis-* tag from start of lines --- .../acceptShares.feature | 2 +- .../features/apiSharees/sharees.feature | 38 +++++++++---------- 2 files changed, 20 insertions(+), 20 deletions(-) diff --git a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature index 7d4ddf338d92..e308eade6a0d 100644 --- a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature +++ b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature @@ -521,7 +521,7 @@ Feature: accept/decline shares coming from internal users | declined_share_path | | /Shares/PARENT | - @issue-ocis-765 + Scenario: shares exist after restoring already shared file to a previous version And user "Alice" has uploaded file with content "Test Content." to "/toShareFile.txt" And user "Alice" has uploaded file with content "Content Test Updated." to "/toShareFile.txt" diff --git a/tests/acceptance/features/apiSharees/sharees.feature b/tests/acceptance/features/apiSharees/sharees.feature index 67292913d513..83fb5a8754e4 100644 --- a/tests/acceptance/features/apiSharees/sharees.feature +++ b/tests/acceptance/features/apiSharees/sharees.feature @@ -54,7 +54,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search only with group members - denied Given using OCS API version "" And parameter "shareapi_only_share_with_group_members" of app "core" has been set to "yes" @@ -100,7 +100,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search only with group members - no group as non-member Given using OCS API version "" And parameter "shareapi_only_share_with_group_members" of app "core" has been set to "yes" @@ -121,7 +121,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search only with membership groups - denied Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -141,7 +141,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search only with membership groups - denied but users match Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -162,7 +162,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search only with membership groups - allowed Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -183,7 +183,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search only with membership groups - allowed including users Given using OCS API version "" And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" @@ -205,7 +205,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search without exact match no iteration allowed Given using OCS API version "" And parameter "shareapi_allow_share_dialog_user_enumeration" of app "core" has been set to "no" @@ -225,7 +225,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search with exact match no iteration allowed Given using OCS API version "" And parameter "shareapi_allow_share_dialog_user_enumeration" of app "core" has been set to "no" @@ -246,7 +246,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Search with exact match group no iteration allowed Given using OCS API version "" And parameter "shareapi_allow_share_dialog_user_enumeration" of app "core" has been set to "no" @@ -267,7 +267,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Try to search for users and groups when in a group that is excluded from sharing (could match both users and groups) Given using OCS API version "" And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" @@ -288,7 +288,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Try to search for users and groups when in a group that is excluded from sharing (exact match to a user) Given using OCS API version "" And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" @@ -309,7 +309,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Try to search for users and groups when in a group that is excluded from sharing (exact match to a group) Given using OCS API version "" And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" @@ -449,7 +449,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Group sharees not returned when group sharing is disabled Given using OCS API version "" And parameter "shareapi_allow_group_sharing" of app "core" has been set to "no" @@ -495,7 +495,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Enumerate only group members - accept exact match from non-member groups Given using OCS API version "" And parameter "shareapi_share_dialog_user_enumeration_group_members" of app "core" has been set to "yes" @@ -516,7 +516,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: Enumerate only group members - only show partial results from member groups Given using OCS API version "" And parameter "shareapi_share_dialog_user_enumeration_group_members" of app "core" has been set to "yes" @@ -583,7 +583,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: empty search for sharees when search min length is set to 0 Given the administrator has updated system config key "user.search_min_length" with value "0" And user "sharee2" has been created with default attributes and without skeleton files @@ -609,7 +609,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: empty search for sharees when search min length is set to 2 Given the administrator has updated system config key "user.search_min_length" with value "2" And user "sharee2" has been created with default attributes and without skeleton files @@ -680,7 +680,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: search for sharees without search when min length is set to 0 Given the administrator has updated system config key "user.search_min_length" with value "0" And user "sharee2" has been created with default attributes and without skeleton files @@ -705,7 +705,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-1317 + Scenario Outline: search for sharees without search when min length is set to 2 Given the administrator has updated system config key "user.search_min_length" with value "2" And user "sharee2" has been created with default attributes and without skeleton files From ddffe689f95b86fd0474ac6d44ff28a4b4cda17d Mon Sep 17 00:00:00 2001 From: Roshan Lamichhane Date: Mon, 6 Feb 2023 14:20:59 +0545 Subject: [PATCH 3/5] Removed remaining issue-ocis-* tags --- .../apiAuthWebDav/webDavMKCOLAuth.feature | 4 ++-- .../features/apiAuthWebDav/webDavPOSTAuth.feature | 2 +- .../apiAuthWebDav/webDavPROPPATCHAuth.feature | 2 +- .../capabilitiesWithNormalUser.feature | 2 +- .../features/apiFavorites/favorites.feature | 8 ++++---- .../acceptance/features/apiMain/checksums.feature | 14 +++++++------- tests/acceptance/features/apiMain/main.feature | 2 +- tests/acceptance/features/apiMain/quota.feature | 2 +- .../createShareExpirationDate.feature | 2 +- .../createShareToSharesFolder.feature | 2 +- .../deleteShareFromShares.feature | 2 +- .../acceptShares.feature | 2 +- .../apiShareManagementToShares/mergeShare.feature | 2 +- .../moveReceivedShare.feature | 2 +- .../gettingShares.feature | 2 +- .../accessToShare.feature | 4 ++-- .../changingFilesShare.feature | 2 +- .../gettingShares.feature | 12 ++++++------ .../accessToPublicLinkShare.feature | 2 +- .../changingPublicLinkShare.feature | 8 +------- .../createPublicLinkShare.feature | 13 +++++-------- .../deletePublicLinkShare.feature | 2 +- .../copyFromPublicLink.feature | 10 +++++----- .../copyFromPublicLinkOc10Issue37683.feature | 6 +++--- .../apiSharePublicLink2/multilinkSharing.feature | 4 ++-- .../updatePublicLinkShare.feature | 15 +++++++-------- .../uploadToPublicLinkShare.feature | 10 +++------- .../reShareWithExpiryDate.feature | 12 ++++++------ ...ShareWhenShareWithOnlyMembershipGroups.feature | 2 +- .../reShareWithExpiryDate.feature | 12 ++++++------ .../apiShareUpdateToShares/updateShare.feature | 2 +- .../updateShareGroupAndUserWithSameName.feature | 2 +- .../features/apiSharees/sharees.feature | 2 +- .../apiTrashbin/trashbinFilesFolders.feature | 10 +++++----- .../apiVersions/fileVersionAuthor.feature | 2 +- .../fileVersionAuthorSharingToShares.feature | 2 +- .../features/apiVersions/fileVersions.feature | 10 +++++----- .../fileVersionsSharingToShares.feature | 6 +++--- .../features/apiWebdavDelete/deleteFolder.feature | 4 ++-- .../apiWebdavLocks/exclusiveLocks.feature | 2 +- .../exclusiveLocksOc10Issue34358.feature | 2 +- .../features/apiWebdavLocks/folder.feature | 2 +- .../features/apiWebdavLocks/publicLink.feature | 2 +- .../publicLinkLockdiscovery.feature | 2 +- .../apiWebdavLocks/requestsWithToken.feature | 2 +- .../requestsWithTokenOc10Issue34338.feature | 2 +- .../requestsWithTokenOc10Issue34360.feature | 2 +- .../features/apiWebdavLocks2/setTimeout.feature | 2 +- .../setTimeoutSharesToRoot.feature | 2 +- .../setTimeoutSharesToShares.feature | 2 +- .../apiWebdavLocks3/independentLocks.feature | 2 +- .../independentLocksShareToRoot.feature | 2 +- .../independentLocksShareToShares.feature | 2 +- .../features/apiWebdavLocksUnlock/unlock.feature | 2 +- .../unlockOc10Issue34302.feature | 2 +- .../unlockSharingToRoot.feature | 2 +- .../unlockSharingToShares.feature | 2 +- .../features/apiWebdavMove2/moveFile.feature | 6 +++--- .../moveFileToBlacklistedName.feature | 2 +- .../apiWebdavProperties1/copyFile.feature | 12 ++++++------ .../apiWebdavProperties1/createFileFolder.feature | 6 +++--- .../apiWebdavProperties1/getQuota.feature | 2 +- .../setFileProperties.feature | 10 +++++----- .../getFileProperties.feature | 12 ++++++------ .../features/apiWebdavUpload1/uploadFile.feature | 12 ++++++------ 65 files changed, 144 insertions(+), 158 deletions(-) diff --git a/tests/acceptance/features/apiAuthWebDav/webDavMKCOLAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavMKCOLAuth.feature index 26491febba60..372a2f361edf 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-reva-197 + @skipOnOcV10 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-reva-197 + @skipOnOcV10 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" diff --git a/tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature index 9b8410db962e..82ef02422515 100644 --- a/tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature +++ b/tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature @@ -34,7 +34,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-179 + Scenario: send POST requests to another user's webDav endpoints as normal user When user "Brian" requests these endpoints with "POST" including body "doesnotmatter" about user "Alice" | endpoint | diff --git a/tests/acceptance/features/apiAuthWebDav/webDavPROPPATCHAuth.feature b/tests/acceptance/features/apiAuthWebDav/webDavPROPPATCHAuth.feature index 02f7d4a781aa..adf668b72aa1 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-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 | diff --git a/tests/acceptance/features/apiCapabilities/capabilitiesWithNormalUser.feature b/tests/acceptance/features/apiCapabilities/capabilitiesWithNormalUser.feature index 55fa7a43840f..b5df8ab7d55c 100644 --- a/tests/acceptance/features/apiCapabilities/capabilitiesWithNormalUser.feature +++ b/tests/acceptance/features/apiCapabilities/capabilitiesWithNormalUser.feature @@ -5,9 +5,9 @@ Feature: default capabilities for normal user Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files + # adjust this scenario after fixing tagged issues as its just created to show difference # in the response items in different environment (core & ocis-reva) - @issue-ocis-reva-175 @issue-ocis-reva-176 Scenario: getting default capabilities with normal user When user "Alice" retrieves the capabilities using the capabilities API Then the OCS status code should be "100" diff --git a/tests/acceptance/features/apiFavorites/favorites.feature b/tests/acceptance/features/apiFavorites/favorites.feature index 6f4a60652b4c..cb326901880c 100644 --- a/tests/acceptance/features/apiFavorites/favorites.feature +++ b/tests/acceptance/features/apiFavorites/favorites.feature @@ -13,7 +13,7 @@ Feature: favorite And user "Alice" has created folder "/PARENT" And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt" - @issue-ocis-reva-276 + Scenario Outline: Favorite a folder Given using DAV path When user "Alice" favorites element "/FOLDER" using the WebDAV API @@ -29,7 +29,7 @@ Feature: favorite | old | | new | - @issue-ocis-reva-276 + Scenario Outline: Unfavorite a folder Given using DAV path And user "Alice" has favorited element "/FOLDER" @@ -46,7 +46,7 @@ Feature: favorite | old | | new | - @smokeTest @issue-ocis-reva-276 + @smokeTest Scenario Outline: Favorite a file Given using DAV path When user "Alice" favorites element "/textfile0.txt" using the WebDAV API @@ -62,7 +62,7 @@ Feature: favorite | old | | new | - @smokeTest @issue-ocis-reva-276 + @smokeTest Scenario Outline: Unfavorite a file Given using DAV path And user "Alice" has favorited element "/textfile0.txt" diff --git a/tests/acceptance/features/apiMain/checksums.feature b/tests/acceptance/features/apiMain/checksums.feature index 59751de1077b..338bb254c53a 100644 --- a/tests/acceptance/features/apiMain/checksums.feature +++ b/tests/acceptance/features/apiMain/checksums.feature @@ -13,7 +13,7 @@ Feature: checksums | old | | new | - @smokeTest @issue-ocis-reva-196 + @smokeTest Scenario Outline: Uploading a file with checksum should return the checksum in the propfind Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" @@ -36,7 +36,7 @@ Feature: checksums | old | | new | - @issue-ocis-reva-196 + Scenario Outline: Moving a file with checksum should return the checksum in the propfind Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" @@ -61,7 +61,7 @@ Feature: checksums | old | | new | - @issue-ocis-reva-196 + Scenario Outline: Uploading a chunked file with checksum should return the checksum in the propfind Given using DAV path And user "Alice" has uploaded chunk file "1" of "3" with "AAAAA" to "/myChecksumFile.txt" with checksum "MD5:45a72715acdd5019c5be30bdbb75233e" @@ -116,7 +116,7 @@ Feature: checksums | old | | new | - @issue-ocis-reva-196 + Scenario Outline: Copying a file with checksum should return the checksum in the propfind using new DAV path Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" @@ -138,7 +138,7 @@ Feature: checksums | dav_version | | new | - @files_sharing-app-required @issue-ocis-reva-196 + @files_sharing-app-required Scenario Outline: Sharing a file with checksum should return the checksum in the propfind using new DAV path Given the administrator has set the default folder for received shares to "Shares" And auto-accept shares has been disabled @@ -154,7 +154,7 @@ Feature: checksums | dav_version | | new | - @files_sharing-app-required @issue-ocis-reva-196 @skipOnOcV10 + @files_sharing-app-required Scenario Outline: Modifying a shared file should return correct checksum in the propfind using new DAV path Given the administrator has set the default folder for received shares to "Shares" And auto-accept shares has been disabled @@ -340,7 +340,7 @@ Feature: checksums | old | | new | - @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @issue-ocis-reva-196 + @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 Scenario Outline: Uploading a file with invalid SHA1 checksum overwriting an existing file Given using DAV path And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" diff --git a/tests/acceptance/features/apiMain/main.feature b/tests/acceptance/features/apiMain/main.feature index 47be8bbc0ff1..0202e537f3fe 100644 --- a/tests/acceptance/features/apiMain/main.feature +++ b/tests/acceptance/features/apiMain/main.feature @@ -1,7 +1,7 @@ @api Feature: Other tests related to api - @issue-ocis-reva-100 + Scenario: robots.txt file should be accessible When a user requests "/robots.txt" with "GET" and no authentication Then the HTTP status code should be "200" diff --git a/tests/acceptance/features/apiMain/quota.feature b/tests/acceptance/features/apiMain/quota.feature index 3d817a21bb3f..be81be48c17e 100644 --- a/tests/acceptance/features/apiMain/quota.feature +++ b/tests/acceptance/features/apiMain/quota.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-101 @skipOnGraph +@api @skipOnGraph Feature: quota Background: diff --git a/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature b/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature index 193b9a8c7b5d..9b4689699f8b 100644 --- a/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature +++ b/tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: a default expiration date can be specified for shares with users or groups Background: diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature index 59fa31b39de8..f67f5410a425 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature @@ -65,7 +65,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-2133 @issue-ocis-reva-301 @issue-ocis-reva-302 + Scenario Outline: Creating a share of a file with a user and asking for various permission combinations 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 c961a2c4d466..ebd80718320a 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/deleteShareFromShares.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1328 +@api @files_sharing-app-required Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature index e308eade6a0d..9a725ecb03b5 100644 --- a/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature +++ b/tests/acceptance/features/apiShareManagementToShares/acceptShares.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 +@api @files_sharing-app-required Feature: accept/decline shares coming from internal users As a user I want to have control of which received shares I accept diff --git a/tests/acceptance/features/apiShareManagementToShares/mergeShare.feature b/tests/acceptance/features/apiShareManagementToShares/mergeShare.feature index 526178ea422a..dd4db6c861c9 100644 --- a/tests/acceptance/features/apiShareManagementToShares/mergeShare.feature +++ b/tests/acceptance/features/apiShareManagementToShares/mergeShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-reva-1328 @issues-ocis-1289 +@api @files_sharing-app-required Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature b/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature index a12e0a5f5b11..14354c7655a9 100644 --- a/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature +++ b/tests/acceptance/features/apiShareManagementToShares/moveReceivedShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 +@api @files_sharing-app-required Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareOperationsToRoot1/gettingShares.feature b/tests/acceptance/features/apiShareOperationsToRoot1/gettingShares.feature index a2276349213e..a5182431c0ec 100644 --- a/tests/acceptance/features/apiShareOperationsToRoot1/gettingShares.feature +++ b/tests/acceptance/features/apiShareOperationsToRoot1/gettingShares.feature @@ -94,7 +94,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-374 + Scenario Outline: Get a share with a user that didn't receive the share Given using OCS API version "" And user "Carol" has 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 3b17801f163f..7f6a84f5c989 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/accessToShare.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/accessToShare.feature @@ -41,7 +41,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @issue-ocis-reva-260 + @smokeTest Scenario Outline: Sharee can't see the share that is filtered out Given using OCS API version "" And user "Alice" has uploaded file with content "some data" to "/textfile1.txt" @@ -58,7 +58,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @issue-ocis-reva-194 + @smokeTest 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/changingFilesShare.feature b/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature index 5fac1e995bde..6e4e0f7bcd78 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/changingFilesShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 +@api @files_sharing-app-required Feature: sharing Background: diff --git a/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature b/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature index 674202777800..19d7711c2c1e 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature @@ -9,7 +9,7 @@ Feature: sharing | Alice | | Brian | - @smokeTest @issue-ocis-reva-262 + @smokeTest Scenario Outline: getting all shares of a user using that user Given using OCS API version "" And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt" @@ -106,7 +106,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @toFixOnOCIS @issue-ocis-reva-357 @issue-ocis-reva-301 @issue-ocis-reva-302 + @smokeTest @toFixOnOCIS #after fixing all the issues merge this scenario with the one below Scenario Outline: getting share info of a share Given using OCS API version "" @@ -138,7 +138,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @toFixOnOCIS @issue-ocis-reva-357 @issue-ocis-reva-301 @issue-ocis-reva-302 + @smokeTest @toFixOnOCIS #after fixing all the issues merge this scenario with the one above Scenario Outline: getting share info of a share (Bug demonstration for ocis) Given using OCS API version "" @@ -170,7 +170,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-374 + Scenario Outline: Get a share with a user that didn't receive the share Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files @@ -184,7 +184,7 @@ Feature: sharing | 1 | 200 | | 2 | 404 | - @skipOnLDAP @issue-ocis-reva-194 @skipOnGraph + @skipOnLDAP @skipOnGraph Scenario: Share of folder to a group, remove user from that group Given using OCS API version "1" And user "Carol" has been created with default attributes and without skeleton files @@ -205,7 +205,7 @@ Feature: sharing | /Shares/PARENT/ | | /Shares/PARENT/parent.txt | - @issue-ocis-reva-372 + Scenario Outline: getting all the shares inside the folder Given using OCS API version "" And user "Alice" has created folder "/PARENT" diff --git a/tests/acceptance/features/apiSharePublicLink1/accessToPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/accessToPublicLinkShare.feature index cb1875acfbe5..0a65b9423b9e 100644 --- a/tests/acceptance/features/apiSharePublicLink1/accessToPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/accessToPublicLinkShare.feature @@ -1,4 +1,4 @@ -@api @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-282 +@api @public_link_share-feature-required @files_sharing-app-required Feature: accessing a public link share Background: diff --git a/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature index f793b4b040ce..059b112f8362 100644 --- a/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-315 @issue-ocis-reva-316 +@api @files_sharing-app-required @public_link_share-feature-required Feature: changing a public link share @@ -23,7 +23,6 @@ Feature: changing a public link share | read,update,create | 403 | should | old | | read,update,create,delete | 204 | should not | old | - @issue-ocis-reva-292 Examples: | permissions | http-status-code | should-or-not | public-webdav-api-version | | read,update,create | 403 | should | new | @@ -43,7 +42,6 @@ Feature: changing a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-292 Examples: | public-webdav-api-version | | new | @@ -76,7 +74,6 @@ Feature: changing a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-292 Examples: | public-webdav-api-version | | new | @@ -128,7 +125,6 @@ Feature: changing a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-292 Examples: | public-webdav-api-version | | new | @@ -209,7 +205,6 @@ Feature: changing a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-292 Examples: | public-webdav-api-version | | new | @@ -227,7 +222,6 @@ Feature: changing a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-292 Examples: | public-webdav-api-version | | new | diff --git a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature index 73d6693e4770..496aec19f846 100644 --- a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-315 @issue-ocis-reva-316 +@api @files_sharing-app-required @public_link_share-feature-required Feature: create a public link share @@ -67,7 +67,7 @@ Feature: create a public link share | 1 | 100 | | 2 | 200 | - @smokeTest @issue-ocis-reva-199 + @smokeTest Scenario Outline: Creating a new public link share of a file with password using the new public WebDAV API Given using OCS API version "" And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt" @@ -125,7 +125,6 @@ Feature: create a public link share And uploading content to a public link shared file should work using the old public WebDAV API And uploading content to a public link shared file should work using the new public WebDAV API - @issue-ocis-2079 @issue-ocis-reva-292 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | @@ -191,13 +190,12 @@ Feature: create a public link share And the public should not be able to download file "/randomfile.txt" from inside the last public link shared folder using the old public WebDAV API with password "%regular%" And the public should not be able to download file "/randomfile.txt" from inside the last public link shared folder using the new public WebDAV API without a password And the public should not be able to download file "/randomfile.txt" from inside the last public link shared folder using the new public WebDAV API with password "%regular%" - @issue-ocis-2079 @issue-ocis-reva-292 Examples: | ocs_api_version | ocs_status_code | | 1 | 100 | | 2 | 200 | - @smokeTest @issue-ocis-reva-294 + @smokeTest Scenario Outline: Getting the share information of public link share from the OCS API does not expose sensitive information Given using OCS API version "" And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt" @@ -385,7 +383,6 @@ Feature: create a public link share | 2 | 200 | - @issue-ocis-reva-283 Scenario Outline: Do not allow public sharing of the root on ownCloud10 Given using OCS API version "" When user "Alice" creates a public link share using the sharing API with settings @@ -468,7 +465,7 @@ Feature: create a public link share | 1 | 100 | 200 | | 2 | 200 | 200 | - @issue-ocis-reva-199 + Scenario Outline: Delete a folder that has been publicly shared and try to access using the public WebDAV API Given user "Alice" has created folder "PARENT" And user "Alice" has uploaded file with content "Random data" to "/PARENT/parent.txt" @@ -487,7 +484,7 @@ Feature: create a public link share | public-webdav-api-version | | new | - @issue-ocis-reva-292 + Scenario Outline: try to download from a public share that has upload only permissions using the public webdav api Given user "Alice" has created folder "PARENT" And user "Alice" has uploaded file with content "Random data" to "/PARENT/parent.txt" diff --git a/tests/acceptance/features/apiSharePublicLink1/deletePublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/deletePublicLinkShare.feature index 61612e977dc8..af2e3e95050f 100644 --- a/tests/acceptance/features/apiSharePublicLink1/deletePublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/deletePublicLinkShare.feature @@ -20,7 +20,7 @@ Feature: delete a public link share | 1 | 100 | | 2 | 200 | - @issue-product-60 @issue-ocis-reva-311 + @issue-product-60 Scenario Outline: Deleting a public link after renaming a file Given using OCS API version "" And user "Alice" has uploaded file with content "This is a test file" to "test-file.txt" diff --git a/tests/acceptance/features/apiSharePublicLink2/copyFromPublicLink.feature b/tests/acceptance/features/apiSharePublicLink2/copyFromPublicLink.feature index 95dfc7f4327d..dfacc446eb60 100644 --- a/tests/acceptance/features/apiSharePublicLink2/copyFromPublicLink.feature +++ b/tests/acceptance/features/apiSharePublicLink2/copyFromPublicLink.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-310 +@api @files_sharing-app-required @public_link_share-feature-required Feature: copying from public link share Background: @@ -59,7 +59,7 @@ Feature: copying from public link share And as "Alice" file "/PARENT/copy1.txt" should exist And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data 0" - @skipOnOcV10 @issue-ocis-reva-373 @issue-37683 + @skipOnOcV10 Scenario: Copy folder within a public link folder to the same folder name as an already existing file Given user "Alice" has created folder "/PARENT/testFolder" And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt" @@ -85,7 +85,7 @@ Feature: copying from public link share Then the HTTP status code should be "204" And as "Alice" file "/PARENT/copy1.txt" should not exist - @skipOnOcV10 @issue-ocis-reva-373 @issue-37683 + @skipOnOcV10 Scenario: Copy file within a public link folder to a file with name same as an existing folder Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt" And user "Alice" has created folder "/PARENT/new-folder" @@ -158,7 +158,7 @@ Feature: copying from public link share | C++ file.cpp | | sample,1.txt | - @issue-ocis-reva-368 + Scenario Outline: Copy file within a public link folder to a file with unusual destination names Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt" And user "Alice" has created a public link share with settings @@ -173,7 +173,7 @@ Feature: copying from public link share | testfile.txt | | | - @issue-ocis-reva-368 + Scenario Outline: Copy folder within a public link folder to a folder with unusual destination names Given user "Alice" has created folder "/PARENT/testFolder" And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt" diff --git a/tests/acceptance/features/apiSharePublicLink2/copyFromPublicLinkOc10Issue37683.feature b/tests/acceptance/features/apiSharePublicLink2/copyFromPublicLinkOc10Issue37683.feature index 9378b55a0e16..1e960c4176bd 100644 --- a/tests/acceptance/features/apiSharePublicLink2/copyFromPublicLinkOc10Issue37683.feature +++ b/tests/acceptance/features/apiSharePublicLink2/copyFromPublicLinkOc10Issue37683.feature @@ -1,11 +1,11 @@ -@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-310 +@api @files_sharing-app-required @public_link_share-feature-required Feature: copying from public link share Background: Given user "Alice" has been created with default attributes and without skeleton files And user "Alice" has created folder "/PARENT" - @issue-ocis-reva-373 @issue-37683 @skipOnLDAP @issue-user_ldap-702 + Scenario: Copy folder within a public link folder to the same folder name as an already existing file Given user "Alice" has created folder "/PARENT/testFolder" And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt" @@ -21,7 +21,7 @@ Feature: copying from public link share And the content of file "/PARENT/copy1.txt/testfile.txt" for user "Alice" should be "some data" And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data" - @issue-ocis-reva-373 @issue-37683 + Scenario: Copy file within a public link folder to a file with name same as an existing folder Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt" And user "Alice" has created folder "/PARENT/new-folder" diff --git a/tests/acceptance/features/apiSharePublicLink2/multilinkSharing.feature b/tests/acceptance/features/apiSharePublicLink2/multilinkSharing.feature index 9fec07a8b9cb..fb1cc7990f1c 100644 --- a/tests/acceptance/features/apiSharePublicLink2/multilinkSharing.feature +++ b/tests/acceptance/features/apiSharePublicLink2/multilinkSharing.feature @@ -1,4 +1,4 @@ -@api @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-288 @issue-ocis-reva-252 +@api @public_link_share-feature-required @files_sharing-app-required Feature: multilinksharing Background: @@ -199,7 +199,7 @@ Feature: multilinksharing | old | | new | - @issue-ocis-reva-335 + Scenario Outline: Renaming a folder doesn't remove its public shares Given using OCS API version "1" And using DAV path diff --git a/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature index b6b369d871c6..bd3a45b223b2 100644 --- a/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-252 +@api @files_sharing-app-required @public_link_share-feature-required Feature: update a public link share Background: @@ -45,7 +45,7 @@ Feature: update a public link share | 1 | 100 | | 2 | 200 | - @smokeTest @issue-ocis-reva-336 + @smokeTest Scenario Outline: Creating a new public link share, updating its expiration date and getting its info Given using OCS API version "" And user "Alice" has created folder "FOLDER" @@ -161,7 +161,7 @@ Feature: update a public link share | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-336 + Scenario Outline: Creating a new public link share, updating its expiration date and getting its info (ocis Bug demonstration) Given using OCS API version "" And user "Alice" has created folder "FOLDER" @@ -194,7 +194,7 @@ Feature: update a public link share | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-336 + Scenario Outline: Creating a new public link share, updating its password and getting its info Given using OCS API version "" And user "Alice" has created folder "FOLDER" @@ -226,7 +226,7 @@ Feature: update a public link share | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-336 + Scenario Outline: Creating a new public link share, updating its permissions and getting its info Given using OCS API version "" And user "Alice" has created folder "FOLDER" @@ -258,7 +258,7 @@ Feature: update a public link share | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-336 + Scenario Outline: Creating a new public link share, updating its permissions to view download and upload and getting its info Given using OCS API version "" And user "Alice" has created folder "FOLDER" @@ -290,7 +290,7 @@ Feature: update a public link share | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-336 + Scenario Outline: Creating a new public link share, updating publicUpload option and getting its info Given using OCS API version "" And user "Alice" has created folder "FOLDER" @@ -433,7 +433,6 @@ Feature: update a public link share And the HTTP status code of responses on all endpoints should be "403" And as "Alice" file "PARENT/CHILD/child.txt" should exist - @issue-ocis-2079 @issue-ocis-reva-292 Examples: | ocs_api_version | | 1 | diff --git a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature index a69da8a5c2b4..72e3831d381c 100644 --- a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-315 @issue-ocis-reva-316 +@api @files_sharing-app-required @public_link_share-feature-required Feature: upload to a public link share @@ -20,7 +20,7 @@ Feature: upload to a public link share And the content of file "/FOLDER/test.txt" for user "Alice" should be "test" And the content of file "/FOLDER/test (2).txt" for user "Alice" should be "test2" - @smokeTest @issue-ocis-reva-286 + @smokeTest Scenario: Uploading same file to a public upload-only share multiple times via new API # The new API does the autorename automatically in upload-only folders Given user "Alice" has created a public link share with settings @@ -49,7 +49,6 @@ Feature: upload to a public link share | old | old | | new | old | - @issue-ocis-reva-290 Examples: | dav-path | public-webdav-api-version | | old | new | @@ -67,7 +66,6 @@ Feature: upload to a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-292 Examples: | public-webdav-api-version | | new | @@ -131,7 +129,6 @@ Feature: upload to a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-195 Examples: | public-webdav-api-version | | new | @@ -149,7 +146,6 @@ Feature: upload to a public link share | public-webdav-api-version | | old | - @issue-ocis-reva-195 Examples: | public-webdav-api-version | | new | @@ -235,7 +231,7 @@ Feature: upload to a public link share Then the HTTP status code should be "403" And the content of file "/FOLDER/test.txt" for user "Alice" should be "test" - @smokeTest @issue-ocis-reva-286 + @smokeTest Scenario: Uploading same file to a public upload-write and no edit and no overwrite share multiple times with new public API Given user "Alice" has created a public link share with settings | path | FOLDER | diff --git a/tests/acceptance/features/apiShareReshareToRoot3/reShareWithExpiryDate.feature b/tests/acceptance/features/apiShareReshareToRoot3/reShareWithExpiryDate.feature index a4ff417a29c1..566b725db500 100644 --- a/tests/acceptance/features/apiShareReshareToRoot3/reShareWithExpiryDate.feature +++ b/tests/acceptance/features/apiShareReshareToRoot3/reShareWithExpiryDate.feature @@ -30,7 +30,7 @@ Feature: resharing a resource with an expiration date | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-194 + Scenario Outline: User should be able to set expiration while resharing a file with group Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files @@ -80,7 +80,7 @@ Feature: resharing a resource with an expiration date | 1 | no | yes | | 100 | | 2 | no | yes | | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing with group using the sharing API with expire days set and combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" @@ -133,7 +133,7 @@ Feature: resharing a resource with an expiration date | 1 | no | yes | | 100 | | 2 | no | yes | | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing with group using the sharing API without expire days set and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" @@ -187,7 +187,7 @@ Feature: resharing a resource with an expiration date | 1 | no | yes | 100 | | 2 | no | yes | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing with group using the sharing API with expire days set and with combinations of default/enforce expire date enabled and specify expire date in share Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" @@ -239,7 +239,7 @@ Feature: resharing a resource with an expiration date | 1 | no | yes | 100 | | 2 | no | yes | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing group share with user using the sharing API with default expire date set and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" @@ -267,7 +267,7 @@ Feature: resharing a resource with an expiration date | 1 | no | yes | | 100 | | 2 | no | yes | | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing group share with user using the sharing API with default expire date set and specifying expiration on share and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" diff --git a/tests/acceptance/features/apiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature b/tests/acceptance/features/apiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature index 337a23603b63..97344c80eb5f 100644 --- a/tests/acceptance/features/apiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature +++ b/tests/acceptance/features/apiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-reva-194 +@api @files_sharing-app-required Feature: resharing a resource with an expiration date Background: diff --git a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature index 0ea564fe72b1..5ebde0be0d65 100644 --- a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature +++ b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature @@ -34,7 +34,7 @@ Feature: resharing a resource with an expiration date | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-194 + Scenario Outline: User should be able to set expiration while resharing a file with group Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files @@ -88,7 +88,7 @@ Feature: resharing a resource with an expiration date | 1 | no | | 100 | | 2 | no | | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing with group using the sharing API with expire days set and combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" @@ -145,7 +145,7 @@ Feature: resharing a resource with an expiration date | 1 | no | | 100 | | 2 | no | | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing with group using the sharing API without expire days set and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" @@ -203,7 +203,7 @@ Feature: resharing a resource with an expiration date | 1 | no | 100 | | 2 | no | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing with group using the sharing API with expire days set and with combinations of default/enforce expire date enabled and specify expire date in share Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" @@ -259,7 +259,7 @@ Feature: resharing a resource with an expiration date | 1 | no | 100 | | 2 | no | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing group share with user using the sharing API with default expire date set and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" @@ -289,7 +289,7 @@ Feature: resharing a resource with an expiration date | 1 | no | | 100 | | 2 | no | | 200 | - @issue-ocis-reva-194 + Scenario Outline: resharing group share with user using the sharing API with default expire date set and specifying expiration on share and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" diff --git a/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature b/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature index 421390398ed8..55e4b250b0a1 100644 --- a/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature +++ b/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature @@ -228,7 +228,7 @@ Feature: sharing | path | | /Shares/Carol-folder | - @toFixOnOCIS @toFixOnOcV10 @issue-ocis-reva-349 @issue-ocis-reva-350 @issue-ocis-reva-352 @issue-37653 + @toFixOnOCIS @toFixOnOcV10 #after fixing all the issues merge this scenario with the one below Scenario Outline: API responds with a full set of parameters when owner changes the permission of a share Given using OCS API version "" diff --git a/tests/acceptance/features/apiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature b/tests/acceptance/features/apiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature index 0a7fa8720764..0a61f49354d8 100644 --- a/tests/acceptance/features/apiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature +++ b/tests/acceptance/features/apiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature @@ -1,4 +1,4 @@ -@api @files_sharing-app-required @issue-ocis-1289 +@api @files_sharing-app-required Feature: updating shares to users and groups that have the same name Background: diff --git a/tests/acceptance/features/apiSharees/sharees.feature b/tests/acceptance/features/apiSharees/sharees.feature index 83fb5a8754e4..5fb786241fe4 100644 --- a/tests/acceptance/features/apiSharees/sharees.feature +++ b/tests/acceptance/features/apiSharees/sharees.feature @@ -537,7 +537,7 @@ Feature: sharees | 1 | 100 | 200 | | 2 | 200 | 200 | - @skipOnLDAP @issue-ocis-1317 + @skipOnLDAP Scenario Outline: Enumerate only group members - only accept exact group match from non-memberships Given using OCS API version "" And group "ShareeGroupNonMember" has been created diff --git a/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature b/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature index f92d9302e73a..7ba350a3dc4c 100644 --- a/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature +++ b/tests/acceptance/features/apiTrashbin/trashbinFilesFolders.feature @@ -136,7 +136,7 @@ Feature: files and folders exist in the trashbin after being deleted | dav-path | | new | - @issue-ocis-3561 @skipOnLDAP @skip_on_objectstore + @skipOnLDAP @skip_on_objectstore Scenario Outline: Listing other user's trashbin is prohibited Given using DAV path And user "testtrashbin100" has been created with default attributes and without skeleton files @@ -152,7 +152,7 @@ Feature: files and folders exist in the trashbin after being deleted | dav-path | status-code | | new | 401 | - @issue-ocis-3561 @smokeTest @skipOnLDAP @skip_on_objectstore + @smokeTest @skipOnLDAP @skip_on_objectstore Scenario Outline: Listing other user's trashbin is prohibited with multiple files on trashbin Given using DAV path And user "testtrashbin101" has been created with default attributes and without skeleton files @@ -171,7 +171,7 @@ Feature: files and folders exist in the trashbin after being deleted | dav-path | status-code | | new | 401 | - @issue-ocis-3561 @skipOnLDAP @skip_on_objectstore @provisioning_api-app-required + @skipOnLDAP @skip_on_objectstore @provisioning_api-app-required Scenario Outline: Listing other user's trashbin is prohibited for newly recreated user with same name Given using DAV path And user "testtrashbin102" has been created with default attributes and without skeleton files @@ -195,7 +195,7 @@ Feature: files and folders exist in the trashbin after being deleted | dav-path | status-code | | new | 401 | - @issue-ocis-3561 @skipOnLDAP @skip_on_objectstore + @skipOnLDAP @skip_on_objectstore Scenario Outline: Listing other user's empty unused trashbin is prohibited Given using DAV path And user "testtrashbinempty" has been created with default attributes and without skeleton files @@ -206,7 +206,7 @@ Feature: files and folders exist in the trashbin after being deleted | dav-path | status-code | | new | 401 | - @issue-ocis-3561 @skipOnLDAP @skip_on_objectstore + @skipOnLDAP @skip_on_objectstore Scenario Outline: Listing non-existent user's trashbin is prohibited Given using DAV path When user "Alice" tries to list the trashbin content for user "testtrashbinnotauser" diff --git a/tests/acceptance/features/apiVersions/fileVersionAuthor.feature b/tests/acceptance/features/apiVersions/fileVersionAuthor.feature index 140afb796592..2b6efbd5ce6d 100644 --- a/tests/acceptance/features/apiVersions/fileVersionAuthor.feature +++ b/tests/acceptance/features/apiVersions/fileVersionAuthor.feature @@ -1,4 +1,4 @@ -@api @files_versions-app-required @issue-ocis-reva-275 +@api @files_versions-app-required Feature: file versions remember the author of each version diff --git a/tests/acceptance/features/apiVersions/fileVersionAuthorSharingToShares.feature b/tests/acceptance/features/apiVersions/fileVersionAuthorSharingToShares.feature index 16bcf8811da6..c16cee37025b 100644 --- a/tests/acceptance/features/apiVersions/fileVersionAuthorSharingToShares.feature +++ b/tests/acceptance/features/apiVersions/fileVersionAuthorSharingToShares.feature @@ -1,4 +1,4 @@ -@api @files_versions-app-required @issue-ocis-reva-275 +@api @files_versions-app-required Feature: file versions remember the author of each version diff --git a/tests/acceptance/features/apiVersions/fileVersions.feature b/tests/acceptance/features/apiVersions/fileVersions.feature index f4b4736e7869..4e221a47a365 100644 --- a/tests/acceptance/features/apiVersions/fileVersions.feature +++ b/tests/acceptance/features/apiVersions/fileVersions.feature @@ -1,4 +1,4 @@ -@api @files_versions-app-required @issue-ocis-reva-275 +@api @files_versions-app-required Feature: dav-versions @@ -290,7 +290,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-1289 + @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 @@ -532,14 +532,14 @@ Feature: dav-versions Then the HTTP status code should be "204" And the content of file "/davtest.txt" for user "Alice" should be "Old Test Content." - @issue-ocis-5010 @skip_on_objectstore + @skip_on_objectstore Scenario: Upload the same file twice with the same mtime and a version is available Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API When user "Alice" uploads file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API Then the HTTP status code should be "204" And the version folder of file "/file.txt" for user "Alice" should contain "1" element - @issue-ocis-5010 @skip_on_objectstore + @skip_on_objectstore Scenario: Upload the same file more than twice with the same mtime and only one version is available Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API @@ -547,7 +547,7 @@ Feature: dav-versions Then the HTTP status code should be "204" And the version folder of file "/file.txt" for user "Alice" should contain "1" element - @issue-ocis-5010 @skip_on_objectstore + @skip_on_objectstore Scenario: Upload the same file twice with the same mtime and no version after restoring Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API diff --git a/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature b/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature index 695fdab9ac89..0e3f38812a71 100644 --- a/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature +++ b/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature @@ -1,4 +1,4 @@ -@api @files_versions-app-required @issue-ocis-reva-275 +@api @files_versions-app-required Feature: dav-versions @@ -189,7 +189,7 @@ Feature: dav-versions And the content of file "/Shares/sharingfolder/sharefile.txt" for user "Brian" should be "First content" And the content of file "/Shares/sharingfolder/sharefile.txt" for user "Carol" should be "First content" - @files_sharing-app-required @issue-ocis-reva-386 + @files_sharing-app-required Scenario Outline: Moving a file (with versions) into a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -217,7 +217,7 @@ Feature: dav-versions | old | Brian | /testshare | | new | Brian | /testshare | - @files_sharing-app-required @issue-ocis-reva-386 + @files_sharing-app-required Scenario Outline: Moving a file (with versions) out of a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/apiWebdavDelete/deleteFolder.feature b/tests/acceptance/features/apiWebdavDelete/deleteFolder.feature index 4c33656bbb79..fc6075ae0c9d 100644 --- a/tests/acceptance/features/apiWebdavDelete/deleteFolder.feature +++ b/tests/acceptance/features/apiWebdavDelete/deleteFolder.feature @@ -19,7 +19,7 @@ Feature: delete folder | old | | new | - @issue-ocis-reva-269 + Scenario Outline: delete a folder when 2 folder exist with different case Given using DAV path And user "Alice" has created folder "/parent" @@ -32,7 +32,7 @@ Feature: delete folder | old | | new | - @issue-ocis-reva-269 + Scenario Outline: delete a sub-folder Given using DAV path And user "Alice" has created folder "/PARENT/CHILD" diff --git a/tests/acceptance/features/apiWebdavLocks/exclusiveLocks.feature b/tests/acceptance/features/apiWebdavLocks/exclusiveLocks.feature index d1723d96dc55..7fff2431d6f7 100644 --- a/tests/acceptance/features/apiWebdavLocks/exclusiveLocks.feature +++ b/tests/acceptance/features/apiWebdavLocks/exclusiveLocks.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: there can be only one exclusive lock on a resource Background: diff --git a/tests/acceptance/features/apiWebdavLocks/exclusiveLocksOc10Issue34358.feature b/tests/acceptance/features/apiWebdavLocks/exclusiveLocksOc10Issue34358.feature index 90f17ccee4b5..362f7aa6ec3f 100644 --- a/tests/acceptance/features/apiWebdavLocks/exclusiveLocksOc10Issue34358.feature +++ b/tests/acceptance/features/apiWebdavLocks/exclusiveLocksOc10Issue34358.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: there can be only one exclusive lock on a resource @issue-34358 diff --git a/tests/acceptance/features/apiWebdavLocks/folder.feature b/tests/acceptance/features/apiWebdavLocks/folder.feature index 90a227f2d1ab..bca48b8c1946 100644 --- a/tests/acceptance/features/apiWebdavLocks/folder.feature +++ b/tests/acceptance/features/apiWebdavLocks/folder.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: lock folders Background: diff --git a/tests/acceptance/features/apiWebdavLocks/publicLink.feature b/tests/acceptance/features/apiWebdavLocks/publicLink.feature index 6b48c1420174..d63a8194f83d 100644 --- a/tests/acceptance/features/apiWebdavLocks/publicLink.feature +++ b/tests/acceptance/features/apiWebdavLocks/publicLink.feature @@ -1,4 +1,4 @@ -@api @smokeTest @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-172 +@api @smokeTest @public_link_share-feature-required @files_sharing-app-required Feature: persistent-locking in case of a public link Background: diff --git a/tests/acceptance/features/apiWebdavLocks/publicLinkLockdiscovery.feature b/tests/acceptance/features/apiWebdavLocks/publicLinkLockdiscovery.feature index 5950450c8741..0e3421a9a33d 100644 --- a/tests/acceptance/features/apiWebdavLocks/publicLinkLockdiscovery.feature +++ b/tests/acceptance/features/apiWebdavLocks/publicLinkLockdiscovery.feature @@ -1,4 +1,4 @@ -@api @smokeTest @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-172 +@api @smokeTest @public_link_share-feature-required @files_sharing-app-required Feature: LOCKDISCOVERY for public links Background: diff --git a/tests/acceptance/features/apiWebdavLocks/requestsWithToken.feature b/tests/acceptance/features/apiWebdavLocks/requestsWithToken.feature index a7190ad7e4d8..5c0c9199345f 100644 --- a/tests/acceptance/features/apiWebdavLocks/requestsWithToken.feature +++ b/tests/acceptance/features/apiWebdavLocks/requestsWithToken.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: actions on a locked item are possible if the token is sent with the request Background: diff --git a/tests/acceptance/features/apiWebdavLocks/requestsWithTokenOc10Issue34338.feature b/tests/acceptance/features/apiWebdavLocks/requestsWithTokenOc10Issue34338.feature index c4957c8c8ad1..4cb80e325e12 100644 --- a/tests/acceptance/features/apiWebdavLocks/requestsWithTokenOc10Issue34338.feature +++ b/tests/acceptance/features/apiWebdavLocks/requestsWithTokenOc10Issue34338.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: actions on a locked item are possible if the token is sent with the request @issue-34338 @files_sharing-app-required diff --git a/tests/acceptance/features/apiWebdavLocks/requestsWithTokenOc10Issue34360.feature b/tests/acceptance/features/apiWebdavLocks/requestsWithTokenOc10Issue34360.feature index 6cd12737cbe8..a6d354fc4e78 100644 --- a/tests/acceptance/features/apiWebdavLocks/requestsWithTokenOc10Issue34360.feature +++ b/tests/acceptance/features/apiWebdavLocks/requestsWithTokenOc10Issue34360.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: actions on a locked item are possible if the token is sent with the request @issue-34360 @files_sharing-app-required diff --git a/tests/acceptance/features/apiWebdavLocks2/setTimeout.feature b/tests/acceptance/features/apiWebdavLocks2/setTimeout.feature index 4478d9621c0f..3c64c226189e 100644 --- a/tests/acceptance/features/apiWebdavLocks2/setTimeout.feature +++ b/tests/acceptance/features/apiWebdavLocks2/setTimeout.feature @@ -1,4 +1,4 @@ -@api @smokeTest @public_link_share-feature-required @issue-ocis-reva-172 +@api @smokeTest @public_link_share-feature-required Feature: set timeouts of LOCKS Background: diff --git a/tests/acceptance/features/apiWebdavLocks2/setTimeoutSharesToRoot.feature b/tests/acceptance/features/apiWebdavLocks2/setTimeoutSharesToRoot.feature index e2fce0492a61..ead1ad5daff4 100644 --- a/tests/acceptance/features/apiWebdavLocks2/setTimeoutSharesToRoot.feature +++ b/tests/acceptance/features/apiWebdavLocks2/setTimeoutSharesToRoot.feature @@ -1,4 +1,4 @@ -@api @smokeTest @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-172 +@api @smokeTest @public_link_share-feature-required @files_sharing-app-required Feature: set timeouts of LOCKS on shares Background: diff --git a/tests/acceptance/features/apiWebdavLocks2/setTimeoutSharesToShares.feature b/tests/acceptance/features/apiWebdavLocks2/setTimeoutSharesToShares.feature index 52b3c0d13760..1ab9e0f22be3 100644 --- a/tests/acceptance/features/apiWebdavLocks2/setTimeoutSharesToShares.feature +++ b/tests/acceptance/features/apiWebdavLocks2/setTimeoutSharesToShares.feature @@ -1,4 +1,4 @@ -@api @smokeTest @public_link_share-feature-required @files_sharing-app-required @issue-ocis-reva-172 +@api @smokeTest @public_link_share-feature-required @files_sharing-app-required Feature: set timeouts of LOCKS on shares Background: diff --git a/tests/acceptance/features/apiWebdavLocks3/independentLocks.feature b/tests/acceptance/features/apiWebdavLocks3/independentLocks.feature index d43a4d3138ce..65794153ee3c 100644 --- a/tests/acceptance/features/apiWebdavLocks3/independentLocks.feature +++ b/tests/acceptance/features/apiWebdavLocks3/independentLocks.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: independent locks Make sure all locks are independent and don't interact with other items that have the same name diff --git a/tests/acceptance/features/apiWebdavLocks3/independentLocksShareToRoot.feature b/tests/acceptance/features/apiWebdavLocks3/independentLocksShareToRoot.feature index 469fbc1423cf..6ed704f06222 100644 --- a/tests/acceptance/features/apiWebdavLocks3/independentLocksShareToRoot.feature +++ b/tests/acceptance/features/apiWebdavLocks3/independentLocksShareToRoot.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: independent locks Make sure all locks are independent and don't interact with other items that have the same name diff --git a/tests/acceptance/features/apiWebdavLocks3/independentLocksShareToShares.feature b/tests/acceptance/features/apiWebdavLocks3/independentLocksShareToShares.feature index 1899e8e41d99..93a508b0d090 100644 --- a/tests/acceptance/features/apiWebdavLocks3/independentLocksShareToShares.feature +++ b/tests/acceptance/features/apiWebdavLocks3/independentLocksShareToShares.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: independent locks Make sure all locks are independent and don't interact with other items that have the same name diff --git a/tests/acceptance/features/apiWebdavLocksUnlock/unlock.feature b/tests/acceptance/features/apiWebdavLocksUnlock/unlock.feature index c736c421b88f..f59ef43c04ad 100644 --- a/tests/acceptance/features/apiWebdavLocksUnlock/unlock.feature +++ b/tests/acceptance/features/apiWebdavLocksUnlock/unlock.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: UNLOCK locked items Background: diff --git a/tests/acceptance/features/apiWebdavLocksUnlock/unlockOc10Issue34302.feature b/tests/acceptance/features/apiWebdavLocksUnlock/unlockOc10Issue34302.feature index e631c6a0f4f9..c1a8a240de4c 100644 --- a/tests/acceptance/features/apiWebdavLocksUnlock/unlockOc10Issue34302.feature +++ b/tests/acceptance/features/apiWebdavLocksUnlock/unlockOc10Issue34302.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 +@api Feature: UNLOCK locked items @issue-34302 @files_sharing-app-required diff --git a/tests/acceptance/features/apiWebdavLocksUnlock/unlockSharingToRoot.feature b/tests/acceptance/features/apiWebdavLocksUnlock/unlockSharingToRoot.feature index ac3edeac515a..3b73df634b4f 100644 --- a/tests/acceptance/features/apiWebdavLocksUnlock/unlockSharingToRoot.feature +++ b/tests/acceptance/features/apiWebdavLocksUnlock/unlockSharingToRoot.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 @files_sharing-app-required +@api @files_sharing-app-required Feature: UNLOCK locked items (sharing) Background: diff --git a/tests/acceptance/features/apiWebdavLocksUnlock/unlockSharingToShares.feature b/tests/acceptance/features/apiWebdavLocksUnlock/unlockSharingToShares.feature index c37be3ef232b..12949846dce1 100644 --- a/tests/acceptance/features/apiWebdavLocksUnlock/unlockSharingToShares.feature +++ b/tests/acceptance/features/apiWebdavLocksUnlock/unlockSharingToShares.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-172 @files_sharing-app-required +@api @files_sharing-app-required Feature: UNLOCK locked items (sharing) Background: diff --git a/tests/acceptance/features/apiWebdavMove2/moveFile.feature b/tests/acceptance/features/apiWebdavMove2/moveFile.feature index b0245aee2aa1..795d15341d15 100644 --- a/tests/acceptance/features/apiWebdavMove2/moveFile.feature +++ b/tests/acceptance/features/apiWebdavMove2/moveFile.feature @@ -177,7 +177,7 @@ Feature: move (rename) file | old | | new | - @issue-ocis-reva-211 + Scenario Outline: rename a file into an invalid filename Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToRename.txt" @@ -229,7 +229,7 @@ Feature: move (rename) file | old | | new | - @issue-ocis-reva-211 + Scenario Outline: Renaming a file to a path with extension .part should not be possible Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToRename.txt" @@ -270,7 +270,7 @@ Feature: move (rename) file | old | | new | - @issue-ocis-reva-265 + #after fixing the issues merge this Scenario into the one above Scenario Outline: renaming to a file with question mark in its name Given using DAV path diff --git a/tests/acceptance/features/apiWebdavMove2/moveFileToBlacklistedName.feature b/tests/acceptance/features/apiWebdavMove2/moveFileToBlacklistedName.feature index 5b39d923f17a..edc80d31e8bd 100644 --- a/tests/acceptance/features/apiWebdavMove2/moveFileToBlacklistedName.feature +++ b/tests/acceptance/features/apiWebdavMove2/moveFileToBlacklistedName.feature @@ -9,7 +9,7 @@ Feature: users cannot move (rename) a file to a blacklisted name And user "Alice" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt" - @issue-ocis-reva-211 + Scenario Outline: rename a file to a filename that is banned by default Given using DAV path When user "Alice" moves file "/textfile0.txt" to "/.htaccess" using the WebDAV API diff --git a/tests/acceptance/features/apiWebdavProperties1/copyFile.feature b/tests/acceptance/features/apiWebdavProperties1/copyFile.feature index 5cad3b520b36..8ecc91202e92 100644 --- a/tests/acceptance/features/apiWebdavProperties1/copyFile.feature +++ b/tests/acceptance/features/apiWebdavProperties1/copyFile.feature @@ -105,7 +105,7 @@ Feature: copy file | old | | new | - @issue-ocis-reva-387 + Scenario Outline: copy a file over the top of an existing folder Given using DAV path And user "Alice" has created folder "FOLDER/sample-folder" @@ -119,7 +119,7 @@ Feature: copy file | old | | new | - @issue-ocis-reva-387 + Scenario Outline: copy a folder over the top of an existing file Given using DAV path And user "Alice" has created folder "FOLDER/sample-folder" @@ -132,7 +132,7 @@ Feature: copy file | old | | new | - @issue-ocis-reva-387 + Scenario Outline: copy a folder into another folder at different level Given using DAV path And user "Alice" has created folder "FOLDER/second-level-folder" @@ -149,7 +149,7 @@ Feature: copy file | old | | new | - @issue-ocis-reva-387 + Scenario Outline: copy a file into a folder at different level Given using DAV path And user "Alice" has created folder "FOLDER/second-level-folder" @@ -168,7 +168,7 @@ Feature: copy file | old | | new | - @issue-ocis-reva-387 + Scenario Outline: copy a file into a file at different level Given using DAV path And user "Alice" has uploaded file with content "file at second level" to "FOLDER/second-level-file.txt" @@ -186,7 +186,7 @@ Feature: copy file | old | | new | - @issue-ocis-reva-387 + Scenario Outline: copy a folder into a file at different level Given using DAV path And user "Alice" has created folder "FOLDER/second-level-folder" diff --git a/tests/acceptance/features/apiWebdavProperties1/createFileFolder.feature b/tests/acceptance/features/apiWebdavProperties1/createFileFolder.feature index fae9d25b263f..9310aa9f3dc0 100644 --- a/tests/acceptance/features/apiWebdavProperties1/createFileFolder.feature +++ b/tests/acceptance/features/apiWebdavProperties1/createFileFolder.feature @@ -8,7 +8,7 @@ Feature: create files and folder Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @issue-ocis-reva-269 + Scenario Outline: create a folder Given using DAV path When user "Alice" creates folder "" using the WebDAV API @@ -76,7 +76,7 @@ Feature: create files and folder | old | | new | - @issue-ocis-reva-168 + Scenario Outline: try to create a folder that already exists Given using DAV path And user "Alice" has created folder "my-data" @@ -90,7 +90,7 @@ Feature: create files and folder | old | | new | - @issue-ocis-reva-168 + Scenario Outline: try to create a folder with a name of an existing file Given using DAV path And user "Alice" has uploaded file with content "uploaded data" to "/my-data.txt" diff --git a/tests/acceptance/features/apiWebdavProperties1/getQuota.feature b/tests/acceptance/features/apiWebdavProperties1/getQuota.feature index 79605157d6ce..69b45a59516b 100644 --- a/tests/acceptance/features/apiWebdavProperties1/getQuota.feature +++ b/tests/acceptance/features/apiWebdavProperties1/getQuota.feature @@ -1,4 +1,4 @@ -@api @issue-ocis-reva-101 @skipOnGraph +@api @skipOnGraph Feature: get quota As a user I want to be able to find out my available storage quota diff --git a/tests/acceptance/features/apiWebdavProperties1/setFileProperties.feature b/tests/acceptance/features/apiWebdavProperties1/setFileProperties.feature index 7f5a89c635f5..41b53f4a739c 100644 --- a/tests/acceptance/features/apiWebdavProperties1/setFileProperties.feature +++ b/tests/acceptance/features/apiWebdavProperties1/setFileProperties.feature @@ -8,7 +8,7 @@ Feature: set file properties Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @smokeTest @issue-ocis-reva-276 + @smokeTest Scenario Outline: Setting custom DAV property and reading it Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustomprop.txt" @@ -20,7 +20,7 @@ Feature: set file properties | old | | new | - @issue-ocis-reva-217 + Scenario Outline: Setting custom complex DAV property and reading it Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustomprop.txt" @@ -32,7 +32,7 @@ Feature: set file properties | old | | new | - @issue-ocis-reva-276 + Scenario Outline: Setting custom DAV property and reading it after the file is renamed Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustompropwithmove.txt" @@ -45,7 +45,7 @@ Feature: set file properties | old | | new | - @files_sharing-app-required @issue-ocis-reva-217 + @files_sharing-app-required Scenario Outline: Setting custom DAV property on a shared file as an owner and reading as a recipient Given using DAV path And user "Brian" has been created with default attributes and without skeleton files @@ -63,7 +63,7 @@ Feature: set file properties | old | | new | - @issue-ocis-reva-276 + Scenario Outline: Setting custom DAV property using one endpoint and reading it with other endpoint Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testnewold.txt" diff --git a/tests/acceptance/features/apiWebdavProperties2/getFileProperties.feature b/tests/acceptance/features/apiWebdavProperties2/getFileProperties.feature index dadf112a1e70..264870ec1e38 100644 --- a/tests/acceptance/features/apiWebdavProperties2/getFileProperties.feature +++ b/tests/acceptance/features/apiWebdavProperties2/getFileProperties.feature @@ -26,7 +26,7 @@ Feature: get file properties | new | /नेपाली.txt | | new | s,a,m,p,l,e.txt | - @issue-ocis-reva-214 + Scenario Outline: Do a PROPFIND of various file names Given using DAV path And user "Alice" has uploaded file with content "uploaded content" to "" @@ -45,7 +45,7 @@ Feature: get file properties | new | /file ?2.txt | remote.php/dav/files/%username%/file ?2.txt | | new | /file &2.txt | remote.php/dav/files/%username%/file &2.txt | - @issue-ocis-reva-214 + Scenario Outline: Do a PROPFIND of various folder names Given using DAV path And user "Alice" has created folder "" @@ -94,7 +94,7 @@ Feature: get file properties | new | /नेपाली | नेपाली | | new | /folder #2.txt | file #2.txt | - @issue-ocis-reva-265 + #after fixing all issues delete this Scenario and merge with the one above Scenario Outline: Do a PROPFIND of various files inside various folders Given using DAV path @@ -226,7 +226,7 @@ Feature: get file properties | old | | new | - @smokeTest @issue-ocis-reva-216 + @smokeTest Scenario Outline: Retrieving private link Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/somefile.txt" @@ -251,7 +251,7 @@ Feature: get file properties | /remote.php/dav/files/does-not-exist | Principal with name does-not-exist not found | | | /remote.php/dav/does-not-exist | File not found: does-not-exist in 'root' | | - @issue-ocis-reva-217 + Scenario Outline: add, receive multiple custom meta properties to a file Given using DAV path And user "Alice" has created folder "/TestFolder" @@ -274,7 +274,7 @@ Feature: get file properties | dav_version | | new | - @issue-36920 @issue-ocis-reva-217 + @issue-36920 Scenario Outline: add multiple properties to files inside a folder and do a propfind of the parent folder Given using DAV path And user "Alice" has created folder "/TestFolder" diff --git a/tests/acceptance/features/apiWebdavUpload1/uploadFile.feature b/tests/acceptance/features/apiWebdavUpload1/uploadFile.feature index fe645a6be32b..8cca05a7b384 100644 --- a/tests/acceptance/features/apiWebdavUpload1/uploadFile.feature +++ b/tests/acceptance/features/apiWebdavUpload1/uploadFile.feature @@ -40,7 +40,7 @@ Feature: upload file | new | "C++ file.cpp" | | new | "file #2.txt" | - @issue-ocis-reva-265 + #after fixing all issues delete this Scenario and merge with the one above Scenario Outline: upload a file and check download content Given using DAV path @@ -91,7 +91,7 @@ Feature: upload file | new | /नेपाली | नेपाली | | new | /folder #2.txt | file #2.txt | - @issue-ocis-reva-265 + #after fixing all issues delete this Scenario and merge with the one above Scenario Outline: upload a file into a folder and check download content Given using DAV path @@ -155,7 +155,7 @@ Feature: upload file | new | /upload...1.. | abc...txt.. | | new | /... | ... | - @issue-ocis-reva-174 + Scenario Outline: upload file with mtime Given using DAV path When user "Alice" uploads file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API @@ -167,7 +167,7 @@ Feature: upload file | old | | new | - @issue-ocis-reva-174 + Scenario Outline: upload a file with mtime in a folder Given using DAV path And user "Alice" has created folder "testFolder" @@ -180,7 +180,7 @@ Feature: upload file | old | | new | - @issue-ocis-reva-174 + Scenario Outline: moving a file does not change its mtime Given using DAV path And user "Alice" has created folder "testFolder" @@ -194,7 +194,7 @@ Feature: upload file | old | | new | - @issue-ocis-reva-174 + Scenario Outline: overwriting a file changes its mtime Given using DAV path And user "Alice" has uploaded file with content "first time upload content" to "file.txt" From 9f90b3e1ae16e6396aa2032071db37cb45072da8 Mon Sep 17 00:00:00 2001 From: Roshan Lamichhane Date: Mon, 6 Feb 2023 14:34:38 +0545 Subject: [PATCH 4/5] Merged examples tables after removing ocis/reva tags --- .../changingPublicLinkShare.feature | 22 ------------------- .../createPublicLinkShare.feature | 10 +-------- .../uploadToPublicLinkShare.feature | 18 --------------- .../apiWebdavLocks/publicLink.feature | 3 --- 4 files changed, 1 insertion(+), 52 deletions(-) diff --git a/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature index 059b112f8362..b296baf6cd71 100644 --- a/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature @@ -22,9 +22,6 @@ Feature: changing a public link share | permissions | http-status-code | should-or-not | public-webdav-api-version | | read,update,create | 403 | should | old | | read,update,create,delete | 204 | should not | old | - - Examples: - | permissions | http-status-code | should-or-not | public-webdav-api-version | | read,update,create | 403 | should | new | | read,update,create,delete | 204 | should not | new | @@ -41,9 +38,6 @@ Feature: changing a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @skipOnRansomwareProtection @issue-ransomware-208 @@ -73,9 +67,6 @@ Feature: changing a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @@ -90,10 +81,6 @@ Feature: changing a public link share Examples: | public-webdav-api-version | | old | - - - Examples: - | public-webdav-api-version | | new | @@ -124,9 +111,6 @@ Feature: changing a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @@ -204,9 +188,6 @@ Feature: changing a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @@ -221,7 +202,4 @@ Feature: changing a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | diff --git a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature index 496aec19f846..d2c6de363c48 100644 --- a/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink1/createPublicLinkShare.feature @@ -478,10 +478,6 @@ Feature: create a public link share Examples: | public-webdav-api-version | | old | - - - Examples: - | public-webdav-api-version | | new | @@ -495,13 +491,9 @@ 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" - Examples: - | public-webdav-api-version | response | - | old | | - - Examples: | public-webdav-api-version | response | + | old | | | new | File not found: parent.txt | diff --git a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature index 72e3831d381c..64ee24b3c743 100644 --- a/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink3/uploadToPublicLinkShare.feature @@ -48,9 +48,6 @@ Feature: upload to a public link share | dav-path | public-webdav-api-version | | old | old | | new | old | - - Examples: - | dav-path | public-webdav-api-version | | old | new | | new | new | @@ -65,9 +62,6 @@ Feature: upload to a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @@ -128,9 +122,6 @@ Feature: upload to a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @@ -145,9 +136,6 @@ Feature: upload to a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @@ -176,9 +164,6 @@ Feature: upload to a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @@ -195,9 +180,6 @@ Feature: upload to a public link share Examples: | public-webdav-api-version | | old | - - Examples: - | public-webdav-api-version | | new | @smokeTest diff --git a/tests/acceptance/features/apiWebdavLocks/publicLink.feature b/tests/acceptance/features/apiWebdavLocks/publicLink.feature index d63a8194f83d..b2919eae8d87 100644 --- a/tests/acceptance/features/apiWebdavLocks/publicLink.feature +++ b/tests/acceptance/features/apiWebdavLocks/publicLink.feature @@ -93,8 +93,5 @@ Feature: persistent-locking in case of a public link | public-webdav-api-version | lock-scope | | old | shared | | old | exclusive | - - Examples: - | public-webdav-api-version | lock-scope | | new | shared | | new | exclusive | From 0761a6ce12e6c5a28e5b39956398109b6bb7823b Mon Sep 17 00:00:00 2001 From: Phil Davis Date: Tue, 7 Feb 2023 08:08:04 +0545 Subject: [PATCH 5/5] Refactor scenarios for issue 38835 --- .../apiMain/checksums-TestOc10Issue38835.feature | 2 +- tests/acceptance/features/apiMain/checksums.feature | 12 +++++------- 2 files changed, 6 insertions(+), 8 deletions(-) diff --git a/tests/acceptance/features/apiMain/checksums-TestOc10Issue38835.feature b/tests/acceptance/features/apiMain/checksums-TestOc10Issue38835.feature index 7adbf648b119..12157f1ee6e7 100644 --- a/tests/acceptance/features/apiMain/checksums-TestOc10Issue38835.feature +++ b/tests/acceptance/features/apiMain/checksums-TestOc10Issue38835.feature @@ -5,7 +5,7 @@ Feature: checksums Given user "Alice" has been created with default attributes and without skeleton files # this is a bug demo scenario for https://github.com/owncloud/core/issues/38835 - # Once this scenario is fixed Delete this file and remove @skipOnOcV10 tag from tests/acceptance/features/apiMain/checksums.feature:132 + # Once this scenario is fixed Delete this file and remove @skipOnOcV10 tag from tests/acceptance/features/apiMain/checksums.feature:158 @files_sharing-app-required @skipOnStorage:ceph @skipOnStorage:scality Scenario: Sharing and modifying a file should return correct checksum in the propfind using new DAV path Given the administrator has set the default folder for received shares to "Shares" diff --git a/tests/acceptance/features/apiMain/checksums.feature b/tests/acceptance/features/apiMain/checksums.feature index 338bb254c53a..540266ff53c1 100644 --- a/tests/acceptance/features/apiMain/checksums.feature +++ b/tests/acceptance/features/apiMain/checksums.feature @@ -154,21 +154,19 @@ Feature: checksums | dav_version | | new | - @files_sharing-app-required - Scenario Outline: Modifying a shared file should return correct checksum in the propfind using new DAV path + @files_sharing-app-required @skipOnOcV10 + Scenario: Modifying a shared file should return correct checksum in the propfind using new DAV path Given the administrator has set the default folder for received shares to "Shares" And auto-accept shares has been disabled - And using DAV path + And using new DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian" And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice" When user "Brian" uploads file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/Shares/myChecksumFile.txt" using the WebDAV API Then the HTTP status code should be "204" - And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "" - Examples: - | dav_version | checksum | - | new | SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a | + And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a" + @newChunking Scenario: Upload new DAV chunked file where checksum matches