diff --git a/tests/acceptance/features/apiNotification/emailNotification.feature b/tests/acceptance/features/apiNotification/emailNotification.feature index ccd0fae962..d7bf0b9c00 100644 --- a/tests/acceptance/features/apiNotification/emailNotification.feature +++ b/tests/acceptance/features/apiNotification/emailNotification.feature @@ -11,7 +11,7 @@ Feature: Email notification | Brian | - Scenario: a user gets an email notification when someone shares a project space + Scenario: user gets an email notification when someone shares a project space Given the administrator has given "Alice" the role "Space Admin" using the settings api And user "Alice" has created a space "new-space" with the default quota using the GraphApi When user "Alice" shares a space "new-space" with settings: @@ -28,7 +28,7 @@ Feature: Email notification """ - Scenario: a user gets an email notification when someone shares a file + Scenario: user gets an email notification when someone shares a file Given user "Alice" has uploaded file with content "sample text" to "lorem.txt" When user "Alice" has shared file "lorem.txt" with user "Brian" with permissions "17" Then the HTTP status code should be "200" diff --git a/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature b/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature index ab0ad04aa0..0a1dbe5dd1 100644 --- a/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature +++ b/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature @@ -1,12 +1,15 @@ @api Feature: copying from public link share + As a user + I want to make a copy of a resource within a public link + So that I can have a backup Background: Given user "Alice" has been created with default attributes and without skeleton files And user "Alice" has created folder "/PARENT" - Scenario: Copy file within a public link folder new public WebDAV API + Scenario: copy file within a public link folder new public WebDAV API 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 | path | /PARENT | @@ -19,7 +22,7 @@ Feature: copying from public link share And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data" - Scenario: Copy folder within a public link folder new public WebDAV API + Scenario: copy folder within a public link folder new public WebDAV API Given user "Alice" has created folder "/PARENT/testFolder" And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt" And user "Alice" has created a public link share with settings @@ -33,7 +36,7 @@ Feature: copying from public link share And the content of file "/PARENT/testFolder-copy/testfile.txt" for user "Alice" should be "some data" - Scenario: Copy file within a public link folder to a new folder + Scenario: copy file within a public link folder to a new folder Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt" And user "Alice" has created folder "/PARENT/testFolder" And user "Alice" has created a public link share with settings @@ -47,7 +50,7 @@ Feature: copying from public link share And the content of file "/PARENT/testFolder/copy1.txt" for user "Alice" should be "some data" - Scenario: Copy file within a public link folder to same file name as already existing one + Scenario: copy file within a public link folder to same file name as already existing one Given user "Alice" has uploaded file with content "some data 0" to "/PARENT/testfile.txt" And user "Alice" has uploaded file with content "some data 1" to "/PARENT/copy1.txt" And user "Alice" has created a public link share with settings @@ -60,7 +63,7 @@ Feature: copying from public link share And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data 0" @issue-1232 - Scenario: Copy folder within a public link folder to the same folder name as an already existing file + 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" And user "Alice" has uploaded file with content "some data 1" to "/PARENT/copy1.txt" @@ -75,7 +78,7 @@ Feature: copying from public link share And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data" - Scenario: Copy file within a public link folder and delete file + Scenario: copy file within a public link folder and delete file 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 | path | /PARENT | @@ -86,7 +89,7 @@ Feature: copying from public link share And as "Alice" file "/PARENT/copy1.txt" should not exist @issue-1232 - Scenario: Copy file within a public link folder to a file with name same as an existing folder + 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" And user "Alice" has uploaded file with content "some data 1" to "/PARENT/new-folder/testfile1.txt" @@ -101,7 +104,7 @@ Feature: copying from public link share And the content of file "/PARENT/new-folder/testfile.txt" for user "Alice" should be "some data" - Scenario Outline: Copy file with special characters in it's name within a public link folder + Scenario Outline: copy file with special characters in it's name within a public link folder Given user "Alice" has uploaded file with content "some data" to "/PARENT/" And user "Alice" has created a public link share with settings | path | /PARENT | @@ -120,7 +123,7 @@ Feature: copying from public link share | sample,1.txt | - Scenario Outline: Copy file within a public link folder to a file with special characters in it's name + Scenario Outline: copy file within a public link folder to a file with special characters in it's name 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 | path | /PARENT | @@ -139,7 +142,7 @@ Feature: copying from public link share | sample,1.txt | - Scenario Outline: Copy file within a public link folder into a folder with special characters + Scenario Outline: copy file within a public link folder into a folder with special characters Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt" And user "Alice" has created folder "/PARENT/" And user "Alice" has created a public link share with settings @@ -159,7 +162,7 @@ Feature: copying from public link share | sample,1.txt | @issue-1230 - Scenario Outline: Copy file within a public link folder to a file with unusual destination names + 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 | path | /PARENT | @@ -174,7 +177,7 @@ Feature: copying from public link share | | @issue-1230 - Scenario Outline: Copy folder within a public link folder to a folder with unusual destination names + 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" And user "Alice" has created a public link share with settings diff --git a/tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature b/tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature index 23a0f55989..4cdc3b7d86 100644 --- a/tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature +++ b/tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature @@ -1,11 +1,14 @@ @api -Feature: multilinksharing +Feature: multi-link sharing + As a user + I want to create multiple public link for a single resource + So that I can share them with various permissions Background: Given user "Alice" has been created with default attributes and without skeleton files @smokeTest - Scenario Outline: Creating three public shares of a folder + Scenario Outline: creating three public shares of a folder Given using OCS API version "" And user "Alice" has created folder "FOLDER" And user "Alice" has created a public link share with settings @@ -44,7 +47,7 @@ Feature: multilinksharing | 2 | 200 | - Scenario Outline: Creating three public shares of a file + Scenario Outline: creating three public shares of a file Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has created a public link share with settings @@ -80,7 +83,7 @@ Feature: multilinksharing | 2 | 200 | - Scenario Outline: Check that updating password doesn't remove name of links + Scenario Outline: check that updating password doesn't remove name of links Given using OCS API version "" And user "Alice" has created folder "FOLDER" And user "Alice" has created a public link share with settings @@ -111,7 +114,7 @@ Feature: multilinksharing | 2 | 200 | - Scenario Outline: Deleting a file deletes also its public links + Scenario Outline: deleting a file also deletes its public links Given using OCS API version "1" And using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" @@ -143,7 +146,7 @@ Feature: multilinksharing | spaces | - Scenario Outline: Deleting one public link share of a file doesn't affect the rest + Scenario Outline: deleting one public link share of a file doesn't affect the rest Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has created a public link share with settings @@ -177,7 +180,7 @@ Feature: multilinksharing | 2 | 200 | - Scenario Outline: Overwriting a file doesn't remove its public shares + Scenario Outline: overwriting a file doesn't remove its public shares Given using OCS API version "1" And using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" @@ -210,7 +213,7 @@ Feature: multilinksharing | spaces | @issue-1251 - Scenario Outline: Renaming a folder doesn't remove its public shares + Scenario Outline: renaming a folder doesn't remove its public shares Given using OCS API version "1" And using DAV path And user "Alice" has created folder "FOLDER" diff --git a/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature index 9b8d68a169..5664945a4e 100644 --- a/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature @@ -1,12 +1,15 @@ @api Feature: update a public link share + As a user + I want to update a public link + So that I change permissions whenever I want Background: Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: API responds with a full set of parameters when owner changes the expireDate of a public share + Scenario Outline: change expiration date of a public link share and get its info Given using OCS API version "" And user "Alice" has created folder "FOLDER" And user "Alice" has created a public link share with settings @@ -46,7 +49,7 @@ Feature: update a public link share | 2 | 200 | @smokeTest - Scenario Outline: Creating a new public link share, updating its expiration date and getting its info + Scenario Outline: change expiration date of a newly created public link share and get its info Given using OCS API version "" And user "Alice" has created folder "FOLDER" And user "Alice" has created a public link share with settings @@ -79,7 +82,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Creating a new public link share with password and adding an expiration date using public API + Scenario Outline: creating a new public link share with password and adding an expiration date using public API Given using OCS API version "" And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt" And user "Alice" has created a public link share with settings @@ -97,7 +100,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Creating a new public link share with password and removing (updating) it to make the resources accessible without password using public API + Scenario Outline: creating a new public link share with password and removing (updating) it to make the resources accessible without password using public API Given using OCS API version "" And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt" And user "Alice" has created a public link share with settings @@ -116,7 +119,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Creating a new public link share, updating its password and getting its info + 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" And user "Alice" has created a public link share with settings @@ -148,7 +151,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Creating a new public link share, updating its permissions and getting its info + 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" And user "Alice" has created a public link share with settings @@ -180,7 +183,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Creating a new public link share, updating its permissions to view download and upload and getting its info + 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" And user "Alice" has created a public link share with settings @@ -212,7 +215,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Creating a new public link share, updating publicUpload option and getting its info + 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" And user "Alice" has created a public link share with settings @@ -244,7 +247,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Adding public upload to a read only shared folder as recipient is not allowed using the public API + Scenario Outline: adding public upload to a read only shared folder as recipient is not allowed using the public API Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/test" @@ -265,7 +268,7 @@ Feature: update a public link share | 2 | 404 | - Scenario Outline: Adding public upload to a shared folder as recipient is allowed with permissions using the public API + Scenario Outline:adding public upload to a shared folder as recipient is allowed with permissions using the public API Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/test" @@ -286,7 +289,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Adding public link with all permissions to a read only shared folder as recipient is not allowed using the public API + Scenario Outline: adding public link with all permissions to a read only shared folder as recipient is not allowed using the public API Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/test" @@ -307,7 +310,7 @@ Feature: update a public link share | 2 | 404 | - Scenario Outline: Adding public link with all permissions to a read only shared folder as recipient is allowed with permissions using the public API + Scenario Outline: adding public link with all permissions to a read only shared folder as recipient is allowed with permissions using the public API Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/test" @@ -328,7 +331,7 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: Updating share permissions from change to read restricts public from deleting files using the public API + Scenario Outline: updating share permissions from change to read restricts public from deleting files using the public API Given using OCS API version "" And user "Alice" has created folder "PARENT" And user "Alice" has created folder "PARENT/CHILD" @@ -350,7 +353,7 @@ Feature: update a public link share | 2 | - Scenario Outline: Updating share permissions from read to change allows public to delete files using the public API + Scenario Outline: updating share permissions from read to change allows public to delete files using the public API Given using OCS API version "" And user "Alice" has created folder "PARENT" And user "Alice" has created folder "PARENT/CHILD" @@ -372,7 +375,7 @@ Feature: update a public link share | 2 | - Scenario Outline: API responds with a full set of parameters when owner renames the folder with a public link in ocis + Scenario Outline: rename a folder with public link and get its info Given using OCS API version "" And using DAV path And user "Alice" has created folder "FOLDER" @@ -418,7 +421,7 @@ Feature: update a public link share | spaces | 2 | 200 | - Scenario Outline: API responds with a full set of parameters when owner renames the file with a public link in ocis + Scenario Outline: rename a file with public link and get its info Given using OCS API version "" And using DAV path And user "Alice" has uploaded file with content "some content" to "/lorem.txt" @@ -464,7 +467,7 @@ Feature: update a public link share | spaces | 2 | 200 | - Scenario Outline: Updating the role of a public link to internal + Scenario Outline: update the role of a public link to internal Given using OCS API version "" And using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile.txt" diff --git a/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature index 7be7c529e1..08e83784ab 100644 --- a/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature @@ -1,14 +1,17 @@ @api @issue-1276 @issue-1277 Feature: upload to a public link share + As a user + I want to create a public link with upload permission + So that the recipient can upload resources Background: Given user "Alice" has been created with default attributes and without skeleton files And user "Alice" has created folder "FOLDER" @smokeTest @issue-1267 - Scenario: Uploading same file to a public upload-only share multiple times via new API - # The new API does the autorename automatically in upload-only folders + Scenario: uploading same file to a public upload-only share multiple times via new API + # The new API does the auto rename in upload-only folders Given user "Alice" has created a public link share with settings | path | FOLDER | | permissions | create | @@ -21,7 +24,7 @@ Feature: upload to a public link share And the content of file "/FOLDER/test (2).txt" for user "Alice" should be "test2" - Scenario Outline: Uploading file to a public upload-only share using public API that was deleted does not work + Scenario Outline: uploading file to a public upload-only share using public API that was deleted does not work Given using DAV path And user "Alice" has created a public link share with settings | path | FOLDER | @@ -42,7 +45,7 @@ Feature: upload to a public link share | spaces | @issue-1269 - Scenario: Uploading file to a public read-only share folder with public API does not work + Scenario: uploading file to a public read-only share folder with public API does not work Given user "Alice" has created a public link share with settings | path | FOLDER | | permissions | read | @@ -50,7 +53,7 @@ Feature: upload to a public link share And the HTTP status code should be "403" - Scenario: Uploading to a public upload-only share with public API + Scenario: uploading to a public upload-only share with public API Given user "Alice" has created a public link share with settings | path | FOLDER | | permissions | create | @@ -61,7 +64,7 @@ Feature: upload to a public link share | ETag | /^"[a-f0-9:\.]{1,32}"$/ | - Scenario: Uploading to a public upload-only share with password with public API + Scenario: uploading to a public upload-only share with password with public API Given user "Alice" has created a public link share with settings | path | FOLDER | | password | %public% | @@ -71,7 +74,7 @@ Feature: upload to a public link share And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file" - Scenario: Uploading to a public read/write share with password with public API + Scenario: uploading to a public read/write share with password with public API Given user "Alice" has created a public link share with settings | path | FOLDER | | password | %public% | @@ -81,7 +84,7 @@ Feature: upload to a public link share And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file" - Scenario: Uploading file to a public shared folder with read/write permission when the sharer has insufficient quota does not work with public API + Scenario: uploading file to a public shared folder with read/write permission when the sharer has insufficient quota does not work with public API When user "Alice" creates a public link share using the sharing API with settings | path | FOLDER | | permissions | change | @@ -90,7 +93,7 @@ Feature: upload to a public link share Then the HTTP status code should be "507" @issue-1290 - Scenario: Uploading file to a public shared folder with upload-only permission when the sharer has insufficient quota does not work with public API + Scenario: uploading file to a public shared folder with upload-only permission when the sharer has insufficient quota does not work with public API When user "Alice" creates a public link share using the sharing API with settings | path | FOLDER | | permissions | create | @@ -99,7 +102,7 @@ Feature: upload to a public link share Then the HTTP status code should be "507" @smokeTest - Scenario: Uploading to a public upload-write and no edit and no overwrite share with public API + Scenario:uUploading to a public upload-write and no edit and no overwrite share with public API Given user "Alice" has created a public link share with settings | path | FOLDER | | permissions | uploadwriteonly | @@ -108,7 +111,7 @@ Feature: upload to a public link share And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file" @smokeTest @issue-1267 - Scenario: Uploading same file to a public upload-write and no edit and no overwrite share multiple times with new public API + 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 | | permissions | uploadwriteonly | diff --git a/tests/acceptance/features/coreApiShareReshareToShares1/reShare.feature b/tests/acceptance/features/coreApiShareReshareToShares1/reShare.feature index 502cd48fd7..b600d48e0e 100644 --- a/tests/acceptance/features/coreApiShareReshareToShares1/reShare.feature +++ b/tests/acceptance/features/coreApiShareReshareToShares1/reShare.feature @@ -1,5 +1,8 @@ @api @issue-1328 Feature: sharing + As a user + I want to re-share a resource + So that other users can have access to it Background: Given these users have been created with default attributes and without skeleton files: @@ -9,7 +12,7 @@ Feature: sharing | Carol | @smokeTest - Scenario Outline: User is not allowed to reshare file when reshare permission is not given + Scenario Outline: user is not allowed to reshare file when reshare permission is not given Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update" @@ -26,7 +29,7 @@ Feature: sharing | 2 | 404 | - Scenario Outline: User is not allowed to reshare folder when reshare permission is not given + Scenario Outline: user is not allowed to reshare folder when reshare permission is not given Given using OCS API version "" And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "read,update" @@ -43,7 +46,7 @@ Feature: sharing | 2 | 404 | @smokeTest - Scenario Outline: User is allowed to reshare file with the same permissions + Scenario Outline: user is allowed to reshare file with the same permissions Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "share,read" @@ -59,7 +62,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: User is allowed to reshare folder with the same permissions + Scenario Outline: user is allowed to reshare folder with the same permissions Given using OCS API version "" And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "share,read" @@ -75,7 +78,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: User is allowed to reshare file with less permissions + Scenario Outline: user is allowed to reshare file with less permissions Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "share,update,read" @@ -91,7 +94,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: User is allowed to reshare folder with less permissions + Scenario Outline: user is allowed to reshare folder with less permissions Given using OCS API version "" And user "Alice" has created folder "/FOLDER" And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "share,update,read" @@ -107,7 +110,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: User is not allowed to reshare file and set more permissions bits + Scenario Outline: user is not allowed to reshare file and set more permissions bits Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions @@ -136,7 +139,7 @@ Feature: sharing | 2 | 404 | 17 | 15 | - Scenario Outline: User is allowed to reshare file and set create (4) or delete (8) permissions bits, which get ignored + Scenario Outline: user is allowed to reshare file and set create (4) or delete (8) permissions bits, which get ignored Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions @@ -177,7 +180,7 @@ Feature: sharing | 2 | 200 | 17 | 9 | 1 | - Scenario Outline: User is not allowed to reshare folder and set more permissions bits + Scenario Outline: user is not allowed to reshare folder and set more permissions bits Given using OCS API version "" And user "Alice" has created folder "/PARENT" And user "Alice" has shared folder "/PARENT" with user "Brian" with permissions @@ -218,7 +221,7 @@ Feature: sharing | 2 | 404 | 19 | 15 | - Scenario Outline: User is not allowed to reshare folder and add delete permission bit (8) + Scenario Outline: user is not allowed to reshare folder and add delete permission bit (8) Given using OCS API version "" And user "Alice" has created folder "/PARENT" And user "Alice" has shared folder "/PARENT" with user "Brian" with permissions @@ -247,7 +250,7 @@ Feature: sharing | 2 | 404 | 23 | 15 | - Scenario Outline: Reshare a file with same name as a deleted file + Scenario Outline: reshare a file with same name as a deleted file Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has shared file "textfile0.txt" with user "Brian" @@ -265,7 +268,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Reshare a folder with same name as a deleted folder + Scenario Outline: reshare a folder with same name as a deleted folder Given using OCS API version "" And user "Alice" has created folder "/PARENT" And user "Alice" has shared folder "PARENT" with user "Brian" @@ -283,7 +286,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Reshare a folder with same name as a deleted file + Scenario Outline: reshare a folder with same name as a deleted file Given using OCS API version "" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has shared file "textfile0.txt" with user "Brian" diff --git a/tests/acceptance/features/coreApiShareReshareToShares2/reShareChain.feature b/tests/acceptance/features/coreApiShareReshareToShares2/reShareChain.feature index 8996a8be15..9a3fe06421 100644 --- a/tests/acceptance/features/coreApiShareReshareToShares2/reShareChain.feature +++ b/tests/acceptance/features/coreApiShareReshareToShares2/reShareChain.feature @@ -1,17 +1,18 @@ @api @issue-2141 Feature: resharing can be done on a reshared resource + As a user + I want to re-share a resource + So that other users can have access to it - Background: + + Scenario: reshared files can be still accessed if a user in the middle removes it Given these users have been created with default attributes and without skeleton files: | username | | Alice | | Brian | | Carol | | David | - - - Scenario: Reshared files can be still accessed if a user in the middle removes it. - Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" + And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" And user "Alice" has shared file "textfile0.txt" with user "Brian" And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice" And user "Brian" has shared file "/Shares/textfile0.txt" with user "Carol" diff --git a/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature b/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature index b0c6133f6b..a66a17d2a9 100644 --- a/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature +++ b/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature @@ -1,16 +1,17 @@ @api @issue-1328 Feature: resharing can be disabled + As a user + I want to share a resource without reshare permission + So that the resource won't be accessible to unwanted individuals - Background: + + Scenario Outline: ordinary sharing is allowed when allow resharing has been disabled Given these users have been created with default attributes and without skeleton files: | username | | Alice | | Brian | And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" - - - Scenario Outline: ordinary sharing is allowed when allow resharing has been disabled - Given using OCS API version "" + And using OCS API version "" When user "Alice" shares file "/textfile0.txt" with user "Brian" with permissions "share,update,read" using the sharing API Then the OCS status code should be "" And the HTTP status code should be "200" diff --git a/tests/acceptance/features/coreApiShareReshareToShares2/reShareSubfolder.feature b/tests/acceptance/features/coreApiShareReshareToShares2/reShareSubfolder.feature index d16ed828d1..dffeec5356 100644 --- a/tests/acceptance/features/coreApiShareReshareToShares2/reShareSubfolder.feature +++ b/tests/acceptance/features/coreApiShareReshareToShares2/reShareSubfolder.feature @@ -1,18 +1,21 @@ @api @issue-1328 Feature: a subfolder of a received share can be reshared + As a user + I want to re-share a resource + So that other users can have access to it Background: Given these users have been created with default attributes and without skeleton files: | username | | Alice | | Brian | - - @smokeTest @issue-2214 - 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 + | Carol | And user "Alice" has created folder "/TMP" And user "Alice" has created folder "/TMP/SUB" + + @smokeTest @issue-2214 + Scenario Outline: user is allowed to reshare a sub-folder with the same permissions + Given using OCS API version "" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" When user "Brian" shares folder "/Shares/TMP/SUB" with user "Carol" with permissions "share,read" using the sharing API @@ -27,11 +30,8 @@ Feature: a subfolder of a received share can be reshared | 2 | 200 | /SUB | - Scenario Outline: User is not allowed to reshare a sub-folder with more permissions + Scenario Outline: user is not allowed to reshare a sub-folder with more permissions Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files - And user "Alice" has created folder "/TMP" - And user "Alice" has created folder "/TMP/SUB" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions And user "Brian" has accepted share "/TMP" offered by user "Alice" When user "Brian" shares folder "/Shares/TMP/SUB" with user "Carol" with permissions using the sharing API @@ -84,11 +84,8 @@ Feature: a subfolder of a received share can be reshared | 2 | 404 | 23 | 15 | @issue-2214 - Scenario Outline: User is allowed to update reshare of a sub-folder with less permissions + Scenario Outline: user is allowed to update reshare of a sub-folder with less permissions Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files - And user "Alice" has created folder "/TMP" - And user "Alice" has created folder "/TMP/SUB" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "/Shares/TMP/SUB" with user "Carol" with permissions "share,create,update,read" @@ -107,11 +104,8 @@ Feature: a subfolder of a received share can be reshared | 2 | 200 | /SUB | @issue-2214 - Scenario Outline: User is allowed to update reshare of a sub-folder to the maximum allowed permissions + Scenario Outline: user is allowed to update reshare of a sub-folder to the maximum allowed permissions Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files - And user "Alice" has created folder "/TMP" - And user "Alice" has created folder "/TMP/SUB" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "/Shares/TMP/SUB" with user "Carol" with permissions "share,read" @@ -130,11 +124,8 @@ Feature: a subfolder of a received share can be reshared | 2 | 200 | /SUB | @issue-2214 - Scenario Outline: User is not allowed to update reshare of a sub-folder with more permissions + Scenario Outline: user is not allowed to update reshare of a sub-folder with more permissions Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files - And user "Alice" has created folder "/TMP" - And user "Alice" has created folder "/TMP/SUB" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "/Shares/TMP/SUB" with user "Carol" with permissions "share,read" diff --git a/tests/acceptance/features/coreApiShareReshareToShares3/reShareUpdate.feature b/tests/acceptance/features/coreApiShareReshareToShares3/reShareUpdate.feature index 1403c24565..088eada24e 100644 --- a/tests/acceptance/features/coreApiShareReshareToShares3/reShareUpdate.feature +++ b/tests/acceptance/features/coreApiShareReshareToShares3/reShareUpdate.feature @@ -1,5 +1,8 @@ @api @issue-1328 Feature: sharing + As a user + I want to update share permissions + So that I can decide what resources can be shared with which permission Background: Given these users have been created with default attributes and without skeleton files: @@ -7,11 +10,11 @@ Feature: sharing | Alice | | Brian | | Carol | - - - Scenario Outline: Update of reshare can reduce permissions - Given using OCS API version "" And user "Alice" has created folder "/TMP" + + + Scenario Outline: update of reshare can reduce permissions + Given using OCS API version "" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,create,update,read" @@ -27,9 +30,8 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Update of reshare can increase permissions to the maximum allowed + Scenario Outline: update of reshare can increase permissions to the maximum allowed Given using OCS API version "" - And user "Alice" has created folder "/TMP" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,read" @@ -45,9 +47,8 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Do not allow update of reshare to exceed permissions + Scenario Outline: do not allow update of reshare to exceed permissions Given using OCS API version "" - And user "Alice" has created folder "/TMP" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,read" @@ -63,9 +64,8 @@ Feature: sharing | 2 | 404 | - Scenario Outline: Update of user reshare by the original share owner can increase permissions up to the permissions of the top-level share + Scenario Outline: update of user reshare by the original share owner can increase permissions up to the permissions of the top-level share Given using OCS API version "" - And user "Alice" has created folder "/TMP" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,read" @@ -81,9 +81,8 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Update of user reshare by the original share owner can increase permissions to more than the permissions of the top-level share + Scenario Outline: update of user reshare by the original share owner can increase permissions to more than the permissions of the top-level share Given using OCS API version "" - And user "Alice" has created folder "/TMP" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,read" @@ -99,11 +98,10 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Update of group reshare by the original share owner can increase permissions up to permissions of the top-level share + Scenario Outline: update of group reshare by the original share owner can increase permissions up to permissions of the top-level share Given using OCS API version "" And group "grp1" has been created And user "Carol" has been added to group "grp1" - And user "Alice" has created folder "/TMP" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "Shares/TMP" with group "grp1" with permissions "share,read" @@ -119,11 +117,10 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Update of group reshare by the original share owner can increase permissions to more than the permissions of the top-level share + Scenario Outline: update of group reshare by the original share owner can increase permissions to more than the permissions of the top-level share Given using OCS API version "" And group "grp1" has been created And user "Carol" has been added to group "grp1" - And user "Alice" has created folder "/TMP" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "Shares/TMP" with group "grp1" with permissions "share,read" @@ -139,9 +136,8 @@ Feature: sharing | 2 | 200 | - Scenario Outline: After losing share permissions user can still delete a previously reshared share + Scenario Outline: after losing share permissions user can still delete a previously reshared share Given using OCS API version "" - And user "Alice" has created folder "/TMP" And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read" And user "Brian" has accepted share "/TMP" offered by user "Alice" And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,create,update,read" diff --git a/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature b/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature index 8514b0fa13..9ae14d57fc 100644 --- a/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature +++ b/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature @@ -1,5 +1,8 @@ @api @issue-1328 Feature: resharing a resource with an expiration date + As a user + I want to reshare resources with expiration date + So that other users will have access to the resources only for a limited amount of time Background: Given these users have been created with default attributes and without skeleton files: @@ -7,11 +10,11 @@ Feature: resharing a resource with an expiration date | Alice | | Brian | And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" - - - Scenario Outline: User should be able to set expiration while resharing a file with user - Given using OCS API version "" And user "Carol" has been created with default attributes and without skeleton files + + + Scenario Outline: user should be able to set expiration while resharing a file with user + Given using OCS API version "" And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share" And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice" When user "Brian" creates a share using the sharing API with settings @@ -33,9 +36,8 @@ Feature: resharing a resource with an expiration date | 2 | 200 | @issue-1289 - Scenario Outline: User should be able to set expiration while resharing a file with group + 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 And group "grp1" has been created And user "Carol" has been added to group "grp1" And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share" @@ -61,7 +63,6 @@ Feature: resharing a resource with an expiration date Scenario Outline: resharing using the sharing API with default expire date set but not enforced Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share" And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice" When user "Brian" creates a share using the sharing API with settings diff --git a/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature b/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature index 09187687a4..b284ab103b 100644 --- a/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature +++ b/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature @@ -1,12 +1,15 @@ @api Feature: sharing + As a user + I want to update share permissions + So that I can decide what resources can be shared with which permission Background: Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files @smokeTest - Scenario Outline: Allow modification of reshare + Scenario Outline: allow modification of reshare Given using OCS API version "" And these users have been created with default attributes and without skeleton files: | username | @@ -62,7 +65,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Cannot set permissions to zero + Scenario Outline: cannot set permissions to zero Given using OCS API version "" And group "grp1" has been created And user "Alice" has created folder "/FOLDER" @@ -77,7 +80,7 @@ Feature: sharing | 2 | 400 | @issue-2173 - Scenario Outline: Cannot update a share of a file with a user to have only create and/or delete permission + Scenario Outline: cannot update a share of a file with a user to have only create and/or delete permission Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" @@ -99,7 +102,7 @@ Feature: sharing | 2 | 400 | create,delete | @issue-2173 - Scenario Outline: Cannot update a share of a file with a group to have only create and/or delete permission + Scenario Outline: cannot update a share of a file with a group to have only create and/or delete permission Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files And group "grp1" has been created @@ -123,7 +126,7 @@ Feature: sharing | 2 | 400 | create,delete | @issue-2201 - Scenario Outline: Share ownership change after moving a shared file outside of an outer share + 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 | | Brian | @@ -158,7 +161,7 @@ Feature: sharing | /folder2 | - Scenario Outline: Share ownership change after moving a shared file to another share + Scenario Outline: share ownership change after moving a shared file to another share Given these users have been created with default attributes and without skeleton files: | username | | Brian | @@ -195,7 +198,7 @@ Feature: sharing @issue-1253 @issue-1224 @issue-1225 #after fixing all the issues merge this scenario with the one below - Scenario Outline: API responds with a full set of parameters when owner changes the permission of a share + Scenario Outline: change the permission of the share and check the API response Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/Alice-folder" @@ -241,7 +244,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Increasing permissions is allowed for owner + Scenario Outline: increasing permissions is allowed for owner Given using OCS API version "" And 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 @@ -264,7 +267,7 @@ Feature: sharing | 2 | 200 | - Scenario Outline: Sharer deletes file uploaded with upload-only permission by sharee to a shared folder + Scenario Outline: sharer deletes file uploaded with upload-only permission by sharee to a shared folder Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has created folder "/FOLDER" diff --git a/tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature b/tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature index 67209c4069..ed2f02a4fe 100644 --- a/tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature +++ b/tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature @@ -1,5 +1,8 @@ @api @issue-1289 @issue-1328 Feature: updating shares to users and groups that have the same name + As a user + I want to update share permissions + So that I can decide what resources can be shared with which permission Background: Given these users have been created with default attributes and without skeleton files: