diff --git a/tests/acceptance/TestHelpers/OcisHelper.php b/tests/acceptance/TestHelpers/OcisHelper.php index 93ba8ba675..c16a4e2638 100644 --- a/tests/acceptance/TestHelpers/OcisHelper.php +++ b/tests/acceptance/TestHelpers/OcisHelper.php @@ -181,79 +181,6 @@ class OcisHelper { \closedir($dir); } - /** - * Helper for Recursive Upload of file/folder - * - * @param string|null $baseUrl - * @param string|null $source - * @param string|null $userId - * @param string|null $password - * @param string|null $xRequestId - * @param string|null $destination - * - * @return void - * @throws Exception|GuzzleException - */ - public static function recurseUpload( - ?string $baseUrl, - ?string $source, - ?string $userId, - ?string $password, - ?string $xRequestId = '', - ?string $destination = '' - ):void { - if ($destination !== '') { - $response = WebDavHelper::makeDavRequest( - $baseUrl, - $userId, - $password, - "MKCOL", - $destination, - [], - null, - $xRequestId - ); - if ($response->getStatusCode() !== 201) { - throw new Exception("Could not create folder destination" . $response->getBody()->getContents()); - } - } - - $dir = \opendir($source); - while (($file = \readdir($dir)) !== false) { - if (($file != '.') && ($file != '..')) { - $sourcePath = $source . '/' . $file; - $destinationPath = $destination . '/' . $file; - if (\is_dir($sourcePath)) { - self::recurseUpload( - $baseUrl, - $sourcePath, - $userId, - $password, - $xRequestId, - $destinationPath - ); - } else { - $response = UploadHelper::upload( - $baseUrl, - $userId, - $password, - $sourcePath, - $destinationPath, - $xRequestId - ); - $responseStatus = $response->getStatusCode(); - if ($responseStatus !== 201) { - throw new Exception( - "Could not upload skeleton file $sourcePath to $destinationPath for user '$userId' status '$responseStatus' response body: '" - . $response->getBody()->getContents() . "'" - ); - } - } - } - } - \closedir($dir); - } - /** * @return int */ diff --git a/tests/acceptance/TestHelpers/SetupHelper.php b/tests/acceptance/TestHelpers/SetupHelper.php index 7754b41663..d665204015 100644 --- a/tests/acceptance/TestHelpers/SetupHelper.php +++ b/tests/acceptance/TestHelpers/SetupHelper.php @@ -405,53 +405,4 @@ class SetupHelper extends \PHPUnit\Framework\Assert { $localContent = (string)$localContent->data->element->contentUrlEncoded; return \urldecode($localContent); } - - /** - * returns the content of a file in a skeleton folder - * - * @param string|null $fileInSkeletonFolder - * @param string|null $xRequestId - * @param string|null $baseUrl - * @param string|null $adminUsername - * @param string|null $adminPassword - * - * @return string content of the file - * @throws GuzzleException - * @throws Exception - */ - public static function readSkeletonFile( - ?string $fileInSkeletonFolder, - ?string $xRequestId = '', - ?string $baseUrl = null, - ?string $adminUsername = null, - ?string $adminPassword = null - ):string { - $baseUrl = self::checkBaseUrl($baseUrl, "readSkeletonFile"); - $adminUsername = self::checkAdminUsername( - $adminUsername, - "readSkeletonFile" - ); - $adminPassword = self::checkAdminPassword( - $adminPassword, - "readSkeletonFile" - ); - - $fileInSkeletonFolder = \rawurlencode("/$fileInSkeletonFolder"); - $response = OcsApiHelper::sendRequest( - $baseUrl, - $adminUsername, - $adminPassword, - 'GET', - "/apps/testing/api/v1/file?file=$fileInSkeletonFolder&absolute=true", - $xRequestId - ); - self::assertSame( - 200, - $response->getStatusCode(), - "Failed to read the file $fileInSkeletonFolder" - ); - $localContent = HttpRequestHelper::getResponseXml($response, __METHOD__); - $localContent = (string)$localContent->data->element->contentUrlEncoded; - return \urldecode($localContent); - } } diff --git a/tests/acceptance/bootstrap/Provisioning.php b/tests/acceptance/bootstrap/Provisioning.php index 6ac64cb1f1..8fd01b396c 100644 --- a/tests/acceptance/bootstrap/Provisioning.php +++ b/tests/acceptance/bootstrap/Provisioning.php @@ -188,7 +188,7 @@ trait Provisioning { } /** - * @Given user :user has been created with default attributes and without skeleton files + * @Given user :user has been created with default attributes * * @param string $user * @@ -202,7 +202,7 @@ trait Provisioning { } /** - * @Given these users have been created without skeleton files and not initialized: + * @Given these users have been created without being initialized: * * @param TableNode $table * @@ -216,7 +216,7 @@ trait Provisioning { } /** - * @Given these users have been created with default attributes and without skeleton files: + * @Given these users have been created with default attributes: * expects a table of users with the heading * "|username|" * diff --git a/tests/acceptance/bootstrap/WebDav.php b/tests/acceptance/bootstrap/WebDav.php index 19999d18e6..62459d44d2 100644 --- a/tests/acceptance/bootstrap/WebDav.php +++ b/tests/acceptance/bootstrap/WebDav.php @@ -828,25 +828,6 @@ trait WebDav { ); } - /** - * @Then /^user "([^"]*)" should be able to access a skeleton file$/ - * - * @param string $user - * - * @return void - */ - public function userShouldBeAbleToAccessASkeletonFile(string $user):void { - $user = $this->getActualUsername($user); - $response = $this->downloadFileAsUserUsingPassword($user, "textfile0.txt"); - $actualStatus = $response->getStatusCode(); - Assert::assertEquals( - 200, - $actualStatus, - "Expected status code to be '200', but got '$actualStatus'" - ); - $this->checkDownloadedContentMatches("ownCloud test text file 0\n", '', $response); - } - /** * @Then the size of the downloaded file should be :size bytes * diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature b/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature index ec5f651ff8..c874f60b6f 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature @@ -5,7 +5,7 @@ Feature: assign role Scenario Outline: only admin user can see all existing roles - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has given "Alice" the role "" using the settings api When user "Alice" tries to get all existing roles Then the HTTP status code should be "" @@ -17,7 +17,7 @@ Feature: assign role @issue-5032 Scenario Outline: only admin user can see assignments list - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has given "Alice" the role "" using the settings api When user "Alice" tries to get list of assignment Then the HTTP status code should be "" @@ -29,7 +29,7 @@ Feature: assign role Scenario Outline: a user cannot change own role - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has given "Alice" the role "" using the settings api When user "Alice" changes his own role to "" Then the HTTP status code should be "400" @@ -45,7 +45,7 @@ Feature: assign role Scenario Outline: only admin user can change the role for another user - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature b/tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature index df198e4828..b0c6f37a22 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature @@ -10,9 +10,9 @@ Feature: sharing Scenario Outline: creating a share of a file with a user Given using OCS API version "" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0" Examples: diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature b/tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature index 71c5d580e9..04dae9232f 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature @@ -10,7 +10,7 @@ Feature: upload file Scenario Outline: upload a file and check download content Given using OCS API version "" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And using DAV path When user "Alice" uploads file with content "uploaded content" to "/upload.txt" using the WebDAV API Then the content of file "/upload.txt" for user "Alice" should be "uploaded content" diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/webDavPUTAuthInvalid.feature b/tests/acceptance/features/apiAccountsHashDifficulty/webDavPUTAuthInvalid.feature index 53b9d34117..0f80c98cca 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/webDavPUTAuthInvalid.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/webDavPUTAuthInvalid.feature @@ -8,7 +8,7 @@ Feature: attempt to PUT files with invalid password See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/PARENT" diff --git a/tests/acceptance/features/apiActivities/activities.feature b/tests/acceptance/features/apiActivities/activities.feature index 7f35a17ca1..1f844f11d8 100644 --- a/tests/acceptance/features/apiActivities/activities.feature +++ b/tests/acceptance/features/apiActivities/activities.feature @@ -4,7 +4,7 @@ Feature: check activities So that I can track modifications Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-9712 Scenario: check activities after uploading a file and a folder @@ -3203,7 +3203,7 @@ Feature: check activities @issue-9860 Scenario: user tries to check activities of another user's file - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "ownCloud test text file" to "textfile.txt" And user "Alice" has uploaded file with content "updated ownCloud test text file" to "textfile.txt" When user "Brian" tries to list the activities of file "textfile.txt" from space "Personal" owned by user "Alice" using the Graph API diff --git a/tests/acceptance/features/apiActivities/activitiesByFileId.feature b/tests/acceptance/features/apiActivities/activitiesByFileId.feature index 16e60b0e96..ffd54cd340 100644 --- a/tests/acceptance/features/apiActivities/activitiesByFileId.feature +++ b/tests/acceptance/features/apiActivities/activitiesByFileId.feature @@ -4,7 +4,7 @@ Feature: check activities So that I can track modifications Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using spaces DAV path diff --git a/tests/acceptance/features/apiActivities/shareActivities.feature b/tests/acceptance/features/apiActivities/shareActivities.feature index bd885e0100..29aee392f0 100644 --- a/tests/acceptance/features/apiActivities/shareActivities.feature +++ b/tests/acceptance/features/apiActivities/shareActivities.feature @@ -4,7 +4,7 @@ Feature: check share activity So that I can track activities of a file Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiAntivirus/antivirus.feature b/tests/acceptance/features/apiAntivirus/antivirus.feature index f2f0f65275..93bda5f6a8 100644 --- a/tests/acceptance/features/apiAntivirus/antivirus.feature +++ b/tests/acceptance/features/apiAntivirus/antivirus.feature @@ -5,7 +5,7 @@ Feature: antivirus So that I can prevent files with viruses from being uploaded Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: upload a normal file without virus @@ -147,7 +147,7 @@ Feature: antivirus Scenario Outline: upload a file with virus to a user share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "uploadFolder" And user "Alice" has sent the following resource share invitation: | resource | uploadFolder | @@ -175,7 +175,7 @@ Feature: antivirus Scenario Outline: upload a file with virus to a group share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "group1" has been created And user "Brian" has been added to group "group1" And user "Alice" has created folder "uploadFolder" @@ -230,7 +230,7 @@ Feature: antivirus Scenario Outline: upload a file with virus to a shared project space Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: @@ -360,7 +360,7 @@ Feature: antivirus Scenario Outline: try to overwrite a file with the virus content in group share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "group1" has been created And user "Brian" has been added to group "group1" And user "Alice" has been added to group "group1" @@ -388,7 +388,7 @@ Feature: antivirus Scenario Outline: try to overwrite a file with the virus content in user share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "uploadFolder" And user "Alice" has uploaded file with content "this is a test file." to "uploadFolder/test.txt" And user "Alice" has sent the following resource share invitation: @@ -444,7 +444,7 @@ Feature: antivirus Scenario: try to overwrite the .space/readme.md file in space share Given using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: | space | new-space | @@ -466,7 +466,7 @@ Feature: antivirus Scenario: member of a project space tries to overwrite a file with virus content Given using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: | space | new-space | diff --git a/tests/acceptance/features/apiArchiver/downloadById.feature b/tests/acceptance/features/apiArchiver/downloadById.feature index 968ee81a75..5d08468a25 100644 --- a/tests/acceptance/features/apiArchiver/downloadById.feature +++ b/tests/acceptance/features/apiArchiver/downloadById.feature @@ -8,7 +8,7 @@ Feature: download multiple resources bundled into an archive So that I don't have to know the full path of the resource Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: download a single file @@ -66,14 +66,14 @@ Feature: download multiple resources bundled into an archive Scenario: download a single file as different user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" When user "Brian" downloads the archive of "/textfile0.txt" of user "Alice" using the resource id Then the HTTP status code should be "404" Scenario: download multiple shared items as share receiver - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has uploaded file with content "other data" to "/textfile1.txt" And user "Alice" has created folder "my_data" @@ -123,7 +123,7 @@ Feature: download multiple resources bundled into an archive @issue-4636 Scenario Outline: download the Shares folder as share receiver - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has uploaded file with content "other data" to "/textfile1.txt" And user "Alice" has created folder "my_data" diff --git a/tests/acceptance/features/apiArchiver/downloadByPath.feature b/tests/acceptance/features/apiArchiver/downloadByPath.feature index 36936d8ef4..fbb65c816a 100644 --- a/tests/acceptance/features/apiArchiver/downloadByPath.feature +++ b/tests/acceptance/features/apiArchiver/downloadByPath.feature @@ -8,7 +8,7 @@ Feature: download multiple resources bundled into an archive So that I don't have to know the ID of the resource Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-4637 Scenario Outline: download a single file @@ -71,7 +71,7 @@ Feature: download multiple resources bundled into an archive @issue-4637 Scenario: download multiple shared items as share receiver - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has uploaded file with content "other data" to "/textfile1.txt" And user "Alice" has created folder "my_data" @@ -121,7 +121,7 @@ Feature: download multiple resources bundled into an archive @issue-4637 Scenario Outline: download the Shares folder as share receiver - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has uploaded file with content "other data" to "/textfile1.txt" And user "Alice" has created folder "my_data" diff --git a/tests/acceptance/features/apiAsyncUpload/delayPostprocessing.feature b/tests/acceptance/features/apiAsyncUpload/delayPostprocessing.feature index f99413ff3b..8fdbc5ee84 100644 --- a/tests/acceptance/features/apiAsyncUpload/delayPostprocessing.feature +++ b/tests/acceptance/features/apiAsyncUpload/delayPostprocessing.feature @@ -5,7 +5,7 @@ Feature: delay post-processing of uploaded files So that I can check the early request Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And async upload has been enabled with post-processing delayed to "30" seconds @issue-5326 diff --git a/tests/acceptance/features/apiCollaboration/checkFileInfo.feature b/tests/acceptance/features/apiCollaboration/checkFileInfo.feature index 5998860b7a..ee0eb9a938 100644 --- a/tests/acceptance/features/apiCollaboration/checkFileInfo.feature +++ b/tests/acceptance/features/apiCollaboration/checkFileInfo.feature @@ -4,7 +4,7 @@ Feature: check file info with different wopi apps So that I can get all the information of a file Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: check file info with fakeOffice diff --git a/tests/acceptance/features/apiCollaboration/wopi.feature b/tests/acceptance/features/apiCollaboration/wopi.feature index 8fbfffae8d..0755455f92 100644 --- a/tests/acceptance/features/apiCollaboration/wopi.feature +++ b/tests/acceptance/features/apiCollaboration/wopi.feature @@ -4,7 +4,7 @@ Feature: collaboration (wopi) So that I can collaborate with other users Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiContract/copy.feature b/tests/acceptance/features/apiContract/copy.feature index ae1a49914d..a727d81021 100644 --- a/tests/acceptance/features/apiContract/copy.feature +++ b/tests/acceptance/features/apiContract/copy.feature @@ -5,7 +5,7 @@ Feature: Copy test Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | And using spaces DAV path diff --git a/tests/acceptance/features/apiContract/propfind.feature b/tests/acceptance/features/apiContract/propfind.feature index 42b0b3ab81..63a9c79311 100644 --- a/tests/acceptance/features/apiContract/propfind.feature +++ b/tests/acceptance/features/apiContract/propfind.feature @@ -4,7 +4,7 @@ Feature: Propfind test So that I can make sure that the response contains all the relevant values Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiContract/sharesReport.feature b/tests/acceptance/features/apiContract/sharesReport.feature index 5ed3af9d9f..00ab519b94 100644 --- a/tests/acceptance/features/apiContract/sharesReport.feature +++ b/tests/acceptance/features/apiContract/sharesReport.feature @@ -4,7 +4,7 @@ Feature: REPORT request to Shares space So that I can make sure that the response contains all the relevant details for shares Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiContract/spacesReport.feature b/tests/acceptance/features/apiContract/spacesReport.feature index fc377ba8d9..4ab6e5279a 100644 --- a/tests/acceptance/features/apiContract/spacesReport.feature +++ b/tests/acceptance/features/apiContract/spacesReport.feature @@ -4,7 +4,7 @@ Feature: REPORT request to project space So that I can make sure that the response contains all the relevant details Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiContract/spacesSharesReport.feature b/tests/acceptance/features/apiContract/spacesSharesReport.feature index fe60376c46..fda7859314 100644 --- a/tests/acceptance/features/apiContract/spacesSharesReport.feature +++ b/tests/acceptance/features/apiContract/spacesSharesReport.feature @@ -7,7 +7,7 @@ Feature: Report test See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiCors/cors.feature b/tests/acceptance/features/apiCors/cors.feature index 7b008cde57..f242cfe588 100644 --- a/tests/acceptance/features/apiCors/cors.feature +++ b/tests/acceptance/features/apiCors/cors.feature @@ -6,7 +6,7 @@ Feature: CORS headers So that I can check if the correct headers are set Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the config "OCIS_CORS_ALLOW_ORIGINS" has been set to "https://aphno.badal" @issue-5195 diff --git a/tests/acceptance/features/apiDepthInfinity/propfind.feature b/tests/acceptance/features/apiDepthInfinity/propfind.feature index 8b600f65a2..a6e217e9be 100644 --- a/tests/acceptance/features/apiDepthInfinity/propfind.feature +++ b/tests/acceptance/features/apiDepthInfinity/propfind.feature @@ -6,7 +6,7 @@ Feature: PROPFIND with depth:infinity Background: Given the config "OCDAV_ALLOW_PROPFIND_DEPTH_INFINITY" has been set to "true" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has created the following folders | path | | simple-folder | diff --git a/tests/acceptance/features/apiDownloads/download.feature b/tests/acceptance/features/apiDownloads/download.feature index dc94389133..85e097d4ab 100644 --- a/tests/acceptance/features/apiDownloads/download.feature +++ b/tests/acceptance/features/apiDownloads/download.feature @@ -7,7 +7,7 @@ Feature: Download file in project space See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiDownloads/spaceDownload.feature b/tests/acceptance/features/apiDownloads/spaceDownload.feature index 2be3a62dc6..e551e00469 100644 --- a/tests/acceptance/features/apiDownloads/spaceDownload.feature +++ b/tests/acceptance/features/apiDownloads/spaceDownload.feature @@ -5,7 +5,7 @@ Feature: Download space Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiGraph/changeRole.feature b/tests/acceptance/features/apiGraph/changeRole.feature index 61b4dc0f4b..42697a6e7b 100644 --- a/tests/acceptance/features/apiGraph/changeRole.feature +++ b/tests/acceptance/features/apiGraph/changeRole.feature @@ -4,11 +4,11 @@ Feature: change role So that I can manage the role of user Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: admin user changes the role of another user with different roles - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And the administrator has assigned the role "" to user "Brian" using the Graph API When user "Alice" changes the role of user "Brian" to role "" using the Graph API @@ -49,7 +49,7 @@ Feature: change role Scenario Outline: non-admin cannot change the user role Given the administrator has assigned the role "" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" tries to change the role of user "Alice" to role "Admin" using the Graph API Then the HTTP status code should be "403" And user "Brian" should have the role "User" @@ -62,7 +62,7 @@ Feature: change role Scenario Outline: non-admin user tries to change the role of nonexistent user Given the administrator has assigned the role "" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" tries to change the role of user "nonexistent" to role "Admin" using the Graph API Then the HTTP status code should be "403" Examples: diff --git a/tests/acceptance/features/apiGraph/enforcePasswordPublicLink.feature b/tests/acceptance/features/apiGraph/enforcePasswordPublicLink.feature index 38bbbb798c..54e6bcb8d1 100644 --- a/tests/acceptance/features/apiGraph/enforcePasswordPublicLink.feature +++ b/tests/acceptance/features/apiGraph/enforcePasswordPublicLink.feature @@ -18,7 +18,7 @@ Feature: enforce password on public link | config | value | | OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD | false | | OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD | true | - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" And using OCS API version "" When user "Alice" creates a public link share using the sharing API with settings @@ -38,7 +38,7 @@ Feature: enforce password on public link | config | value | | OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD | false | | OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD | true | - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" And using OCS API version "" When user "Alice" creates a public link share using the sharing API with settings @@ -57,7 +57,7 @@ Feature: enforce password on public link | config | value | | OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD | false | | OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD | true | - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" And using OCS API version "" And using SharingNG @@ -89,7 +89,7 @@ Feature: enforce password on public link | OCIS_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS | 2 | | OCIS_PASSWORD_POLICY_MIN_DIGITS | 2 | | OCIS_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS | 2 | - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" And using OCS API version "" When user "Alice" creates a public link share using the sharing API with settings @@ -116,7 +116,7 @@ Feature: enforce password on public link | OCIS_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS | 2 | | OCIS_PASSWORD_POLICY_MIN_DIGITS | 2 | | OCIS_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS | 2 | - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" And using OCS API version "" When user "Alice" creates a public link share using the sharing API with settings @@ -149,7 +149,7 @@ Feature: enforce password on public link | OCIS_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS | 2 | | OCIS_PASSWORD_POLICY_MIN_DIGITS | 1 | | OCIS_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS | 2 | - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" And using OCS API version "" And using SharingNG @@ -182,7 +182,7 @@ Feature: enforce password on public link | OCIS_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS | 2 | | OCIS_PASSWORD_POLICY_MIN_DIGITS | 1 | | OCIS_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS | 2 | - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" And using OCS API version "" And using SharingNG @@ -212,7 +212,7 @@ Feature: enforce password on public link Scenario Outline: create a public link with a password in accordance with the password policy (valid cases) Given the config "" has been set to "" And using OCS API version "2" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" When user "Alice" creates a public link share using the sharing API with settings | path | /testfile.txt | @@ -238,7 +238,7 @@ Feature: enforce password on public link Scenario Outline: try to create a public link with a password that does not comply with the password policy (invalid cases) Given using OCS API version "2" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" When user "Alice" creates a public link share using the sharing API with settings | path | /testfile.txt | @@ -258,7 +258,7 @@ Feature: enforce password on public link Scenario Outline: update a public link with a password that is listed in the Banned-Password-List Given the config "OCIS_PASSWORD_POLICY_BANNED_PASSWORDS_LIST" has been set to path "config/drone/banned-password-list.txt" And using OCS API version "2" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" And using SharingNG And user "Alice" has created the following resource link share: @@ -281,7 +281,7 @@ Feature: enforce password on public link Scenario Outline: create a public link with a password that is listed in the Banned-Password-List Given the config "OCIS_PASSWORD_POLICY_BANNED_PASSWORDS_LIST" has been set to path "config/drone/banned-password-list.txt" And using OCS API version "2" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "test file" to "/testfile.txt" When user "Alice" creates a public link share using the sharing API with settings | path | /testfile.txt | diff --git a/tests/acceptance/features/apiGraph/getApplications.feature b/tests/acceptance/features/apiGraph/getApplications.feature index 0728630ec1..4e9f13d63e 100644 --- a/tests/acceptance/features/apiGraph/getApplications.feature +++ b/tests/acceptance/features/apiGraph/getApplications.feature @@ -4,7 +4,7 @@ Feature: get applications So that I can see which role belongs to what user Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: admin user lists all the groups diff --git a/tests/acceptance/features/apiGraph/getAssignedRole.feature b/tests/acceptance/features/apiGraph/getAssignedRole.feature index a75e6ca811..64f4a35911 100644 --- a/tests/acceptance/features/apiGraph/getAssignedRole.feature +++ b/tests/acceptance/features/apiGraph/getAssignedRole.feature @@ -4,7 +4,7 @@ Feature: assign role So that users without an admin role cannot get the list of roles, assignments list and assign roles to users Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: get assigned role of a user @@ -47,12 +47,12 @@ Feature: assign role Scenario: non-admin user tries to get assigned role of another user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Alice" tries to get the assigned role of user "Brian" using the Graph API Then the HTTP status code should be "403" Scenario: non-admin user tries to get assigned role of nonexistent user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Alice" tries to get the assigned role of user "nonexistent" using the Graph API Then the HTTP status code should be "403" diff --git a/tests/acceptance/features/apiGraph/roleManagementEndpoint.feature b/tests/acceptance/features/apiGraph/roleManagementEndpoint.feature index 6e9f6f39c4..3eda8bb34c 100644 --- a/tests/acceptance/features/apiGraph/roleManagementEndpoint.feature +++ b/tests/acceptance/features/apiGraph/roleManagementEndpoint.feature @@ -4,7 +4,7 @@ Feature: permissions role definitions So that I can find out if those endpoints are working correctly or not Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: get a list of permissions role definitions diff --git a/tests/acceptance/features/apiGraph/unassignRole.feature b/tests/acceptance/features/apiGraph/unassignRole.feature index ef4187ec99..95ac0e4c15 100644 --- a/tests/acceptance/features/apiGraph/unassignRole.feature +++ b/tests/acceptance/features/apiGraph/unassignRole.feature @@ -4,11 +4,11 @@ Feature: unassign user role So that the role of user is set to default Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: admin user unassigns the role of another user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And the administrator has assigned the role "" to user "Brian" using the Graph API When user "Alice" unassigns the role of user "Brian" using the Graph API @@ -32,7 +32,7 @@ Feature: unassign user role Scenario: non-admin user tries to unassign role of another user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Alice" tries to unassign the role of user "Brian" using the Graph API Then the HTTP status code should be "403" And user "Brian" should have the role "User" assigned diff --git a/tests/acceptance/features/apiGraph/userGDPRExport.feature b/tests/acceptance/features/apiGraph/userGDPRExport.feature index bbbddda910..1f2a0aa7b2 100644 --- a/tests/acceptance/features/apiGraph/userGDPRExport.feature +++ b/tests/acceptance/features/apiGraph/userGDPRExport.feature @@ -4,7 +4,7 @@ Feature: user GDPR (General Data Protection Regulation) report So that I can review what events are stored by the server Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using spaces DAV path @@ -495,7 +495,7 @@ Feature: user GDPR (General Data Protection Regulation) report Scenario Outline: user tries to generate GDPR report of other users - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Alice" using the Graph API And the administrator has assigned the role "" to user "Brian" using the Graph API When user "Alice" tries to export GDPR report of user "Brian" to "/.personal_data_export.json" using Graph API @@ -585,7 +585,7 @@ Feature: user GDPR (General Data Protection Regulation) report Scenario: generate a GDPR report and check events when a user shares a folder - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folderMain" And user "Alice" has sent the following resource share invitation: | resource | folderMain | @@ -714,7 +714,7 @@ Feature: user GDPR (General Data Protection Regulation) report Scenario: generate a GDPR report and check events when a user creates a public link share - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folderMain" And user "Alice" has created the following resource link share: | resource | folderMain | @@ -860,7 +860,7 @@ Feature: user GDPR (General Data Protection Regulation) report Scenario: generate a GDPR report and check events when a space is shared - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "GDPR Space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: diff --git a/tests/acceptance/features/apiGraphUserGroup/addUserToGroup.feature b/tests/acceptance/features/apiGraphUserGroup/addUserToGroup.feature index 22fa40b880..87c5c1f156 100644 --- a/tests/acceptance/features/apiGraphUserGroup/addUserToGroup.feature +++ b/tests/acceptance/features/apiGraphUserGroup/addUserToGroup.feature @@ -4,7 +4,7 @@ Feature: add users to group So that I can give a user access to the resources of the group Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: adding a user to a group @@ -155,7 +155,7 @@ Feature: add users to group @issue-5938 Scenario Outline: user other than the admin tries to add other user to a group - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And group "groupA" has been created When user "Alice" tries to add user "Brian" to group "groupA" using the Graph API @@ -196,7 +196,7 @@ Feature: add users to group @issue-5939 Scenario Outline: user other than the admin tries to add user to a nonexistent group - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Alice" using the Graph API When user "Alice" tries to add user "Brian" to a nonexistent group using the Graph API Then the HTTP status code should be "403" @@ -226,7 +226,7 @@ Feature: add users to group Scenario: add multiple users to a group at once Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -244,7 +244,7 @@ Feature: add users to group Scenario: admin tries to add users to a nonexistent group at once Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -267,7 +267,7 @@ Feature: add users to group Scenario: admin tries to add nonexistent and existing users to a group at once Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | And user "Alice" has created a group "grp1" using the Graph API @@ -294,7 +294,7 @@ Feature: add users to group @issue-5702 Scenario: try to add users to a group twice Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -316,7 +316,7 @@ Feature: add users to group @issue-5793 Scenario: try to add a group to another group with PATCH request Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | And these groups have been created: @@ -330,7 +330,7 @@ Feature: add users to group @issue-5793 Scenario: try to add a group to another group with POST request Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | And these groups have been created: @@ -344,7 +344,7 @@ Feature: add users to group Scenario Outline: admin tries to add a user to a group with invalid JSON Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | And user "Alice" has created a group "grp1" using the Graph API @@ -359,7 +359,7 @@ Feature: add users to group Scenario Outline: admin tries to add multiple users to a group at once with invalid JSON Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -378,7 +378,7 @@ Feature: add users to group @issue-5871 Scenario: admin tries to add multiple users with wrong host Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -392,7 +392,7 @@ Feature: add users to group @issue-5871 Scenario: admin tries to add single user with wrong host Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | And user "Alice" has created a group "grp1" using the Graph API @@ -429,7 +429,7 @@ Feature: add users to group @issue-5855 Scenario: add same user twice to a group at once Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | And user "Alice" has created a group "grp1" using the Graph API diff --git a/tests/acceptance/features/apiGraphUserGroup/changeOwnPassword.feature b/tests/acceptance/features/apiGraphUserGroup/changeOwnPassword.feature index d666a41917..5d50dd1ee0 100644 --- a/tests/acceptance/features/apiGraphUserGroup/changeOwnPassword.feature +++ b/tests/acceptance/features/apiGraphUserGroup/changeOwnPassword.feature @@ -5,7 +5,7 @@ Feature: an user changes its own password Scenario Outline: change own password - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes When the user "Alice" changes its own password "" to "" using the Graph API Then the HTTP status code should be "" Examples: diff --git a/tests/acceptance/features/apiGraphUserGroup/createGroup.feature b/tests/acceptance/features/apiGraphUserGroup/createGroup.feature index 62ec29fd63..b1b2c2a82b 100644 --- a/tests/acceptance/features/apiGraphUserGroup/createGroup.feature +++ b/tests/acceptance/features/apiGraphUserGroup/createGroup.feature @@ -4,7 +4,7 @@ Feature: create group So that I can add users to the group Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API @@ -32,7 +32,7 @@ Feature: create group @issue-5938 Scenario Outline: user other than the admin can't create a group - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API When user "Brian" tries to create a group "mygroup" using the Graph API Then the HTTP status code should be "403" diff --git a/tests/acceptance/features/apiGraphUserGroup/createUser.feature b/tests/acceptance/features/apiGraphUserGroup/createUser.feature index 821a411d30..c657585840 100644 --- a/tests/acceptance/features/apiGraphUserGroup/createUser.feature +++ b/tests/acceptance/features/apiGraphUserGroup/createUser.feature @@ -7,7 +7,7 @@ Feature: create user See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-3516 Scenario Outline: admin creates a user @@ -66,7 +66,7 @@ Feature: create user Scenario: user cannot be created with the name of the disabled user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And the user "Alice" has disabled user "Brian" When the user "Alice" creates a new user with the following attributes using the Graph API: @@ -79,7 +79,7 @@ Feature: create user Scenario: user can be created with the name of the deleted user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And the user "Alice" has deleted a user "Brian" When the user "Alice" creates a new user with the following attributes using the Graph API: diff --git a/tests/acceptance/features/apiGraphUserGroup/deleteGroup.feature b/tests/acceptance/features/apiGraphUserGroup/deleteGroup.feature index 6298ad79d0..a50c9419a1 100644 --- a/tests/acceptance/features/apiGraphUserGroup/deleteGroup.feature +++ b/tests/acceptance/features/apiGraphUserGroup/deleteGroup.feature @@ -4,7 +4,7 @@ Feature: delete groups So that I can remove unnecessary groups Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API @@ -56,7 +56,7 @@ Feature: delete groups @issue-5938 Scenario Outline: user other than the admin can't delete a group - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And group "new-group" has been created When user "Brian" tries to delete group "new-group" using the Graph API @@ -105,7 +105,7 @@ Feature: delete groups Scenario: user should not see share received via deleted group Given user "Alice" has uploaded file with content "sample text" to "lorem.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Alice" has sent the following resource share invitation: diff --git a/tests/acceptance/features/apiGraphUserGroup/deleteUser.feature b/tests/acceptance/features/apiGraphUserGroup/deleteUser.feature index ebdc6f9d22..3829d92989 100644 --- a/tests/acceptance/features/apiGraphUserGroup/deleteUser.feature +++ b/tests/acceptance/features/apiGraphUserGroup/deleteUser.feature @@ -7,7 +7,7 @@ Feature: delete user See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: admin user deletes a user @@ -28,7 +28,7 @@ Feature: delete user Scenario: delete a user and specify the user name in different case - Given user "brand-new-user" has been created with default attributes and without skeleton files + Given user "brand-new-user" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API When the user "Alice" deletes a user "Brand-New-User" using the Graph API Then the HTTP status code should be "204" @@ -36,7 +36,7 @@ Feature: delete user Scenario Outline: admin user deletes another user with different role - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And the administrator has assigned the role "" to user "Brian" using the Graph API When the user "Alice" deletes a user "Brian" using the Graph API @@ -87,7 +87,7 @@ Feature: delete user Scenario Outline: non-admin user tries to delete another user with different role - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And the administrator has assigned the role "" to user "Alice" using the Graph API When the user "Alice" deletes a user "Brian" using the Graph API @@ -111,7 +111,7 @@ Feature: delete user Scenario: admin user deletes a disabled user Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the user "Alice" has disabled user "Brian" When the user "Alice" deletes a user "Brian" using the Graph API Then the HTTP status code should be "204" @@ -120,8 +120,8 @@ Feature: delete user Scenario Outline: normal user tries to delete a disabled user Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And the administrator has assigned the role "" to user "Carol" using the Graph API And the user "Alice" has disabled user "Brian" @@ -146,7 +146,7 @@ Feature: delete user Scenario: personal space is deleted automatically when the user is deleted Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When the user "Alice" deletes a user "Brian" using the Graph API Then the HTTP status code should be "204" When user "Alice" lists all spaces via the Graph API with query "$filter=driveType eq 'personal'" @@ -155,7 +155,7 @@ Feature: delete user Scenario: accepted share is deleted automatically when the user is deleted Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "new" And user "Brian" has sent the following resource share invitation: | resource | new | diff --git a/tests/acceptance/features/apiGraphUserGroup/editGroup.feature b/tests/acceptance/features/apiGraphUserGroup/editGroup.feature index 308351f006..6da54a5b42 100644 --- a/tests/acceptance/features/apiGraphUserGroup/editGroup.feature +++ b/tests/acceptance/features/apiGraphUserGroup/editGroup.feature @@ -4,7 +4,7 @@ Feature: edit group name So that I can manage group name Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API @issue-5977 diff --git a/tests/acceptance/features/apiGraphUserGroup/editUser.feature b/tests/acceptance/features/apiGraphUserGroup/editUser.feature index 9cf45f3b96..84b1c030c6 100644 --- a/tests/acceptance/features/apiGraphUserGroup/editUser.feature +++ b/tests/acceptance/features/apiGraphUserGroup/editUser.feature @@ -7,7 +7,7 @@ Feature: edit user See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And the user "Alice" has created a new user with the following attributes: | userName | Brian | @@ -17,7 +17,7 @@ Feature: edit user @issue-7044 Scenario Outline: admin user can edit another user's name - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes When the user "Alice" changes the user name of user "Carol" to "" using the Graph API Then the HTTP status code should be "" And the user information of "" should match this JSON schema @@ -277,7 +277,7 @@ Feature: edit user Scenario Outline: normal user should not be able to disable another user - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API When the user "Brian" tries to disable user "Carol" using the Graph API Then the HTTP status code should be "403" @@ -359,7 +359,7 @@ Feature: edit user Scenario Outline: normal user should not be able to enable another user - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And the user "Alice" has disabled user "Carol" And the administrator has assigned the role "" to user "Brian" using the Graph API When the user "Brian" tries to enable user "Carol" using the Graph API diff --git a/tests/acceptance/features/apiGraphUserGroup/getGroup.feature b/tests/acceptance/features/apiGraphUserGroup/getGroup.feature index 0e552cf5f6..47b56f2338 100644 --- a/tests/acceptance/features/apiGraphUserGroup/getGroup.feature +++ b/tests/acceptance/features/apiGraphUserGroup/getGroup.feature @@ -4,7 +4,7 @@ Feature: get groups and their members So that I can see all the groups and their members Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API @@ -21,7 +21,7 @@ Feature: get groups and their members @issue-5938 Scenario Outline: user other than the admin shouldn't get the groups list - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And group "tea-lover" has been created And group "coffee-lover" has been created @@ -59,7 +59,7 @@ Feature: get groups and their members Scenario: admin user gets users of a group - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | | Carol | @@ -74,7 +74,7 @@ Feature: get groups and their members @issue-5938 Scenario Outline: user other than the admin shouldn't get users of a group - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And group "tea-lover" has been created When user "Brian" gets all the members of group "tea-lover" using the Graph API @@ -110,7 +110,7 @@ Feature: get groups and their members Scenario: admin user gets all groups along with its member's information - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | | Carol | @@ -242,7 +242,7 @@ Feature: get groups and their members @issue-5938 Scenario Outline: user other than the admin shouldn't get all groups along with its member's information - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And group "tea-lover" has been created And group "coffee-lover" has been created @@ -281,7 +281,7 @@ Feature: get groups and their members Scenario: admin user gets a group along with its member's information - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And group "tea-lover" has been created And user "Alice" has been added to group "tea-lover" And user "Brian" has been added to group "tea-lover" @@ -364,7 +364,7 @@ Feature: get groups and their members @issue-5604 Scenario Outline: user other than the admin gets a group along with its member's information - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And group "tea-lover" has been created And user "Alice" has been added to group "tea-lover" @@ -511,7 +511,7 @@ Feature: get groups and their members Scenario Outline: non-admin user searches for a group by group name - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | And group "tea-lover" has been created @@ -561,7 +561,7 @@ Feature: get groups and their members Scenario: non-admin user tries to search for a group by group name with less than 3 characters - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | And group "tea-lover" has been created @@ -593,7 +593,7 @@ Feature: get groups and their members @issue-7990 Scenario Outline: user tries to search for groups with invalid characters/token (search term without quotation) - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | And group "" has been created @@ -629,7 +629,7 @@ Feature: get groups and their members @issue-7990 Scenario Outline: user searches for groups with special characters (search term with quotation) - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | And group "" has been created diff --git a/tests/acceptance/features/apiGraphUserGroup/getUser.feature b/tests/acceptance/features/apiGraphUserGroup/getUser.feature index 900f7bff26..ee77f6040d 100644 --- a/tests/acceptance/features/apiGraphUserGroup/getUser.feature +++ b/tests/acceptance/features/apiGraphUserGroup/getUser.feature @@ -4,7 +4,7 @@ Feature: get users So that I can see the information Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -667,7 +667,7 @@ Feature: get users Scenario: admin user gets all users of certain groups Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And the user "Alice" has disabled user "Carol" And group "tea-lover" has been created And group "coffee-lover" has been created @@ -817,7 +817,7 @@ Feature: get users Scenario: admin user gets all users of two groups Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "tea-lover" has been created And group "coffee-lover" has been created And group "wine-lover" has been created @@ -938,7 +938,7 @@ Feature: get users Scenario: admin user gets all users with certain roles and members of a certain group Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Brian" using the Graph API And the administrator has assigned the role "Space Admin" to user "Carol" using the Graph API And group "tea-lover" has been created @@ -1421,7 +1421,7 @@ Feature: get users @issue-7990 Scenario Outline: user tries to search other users with invalid characters/token (search term without quotation) - Given user "" has been created with default attributes and without skeleton files + Given user "" has been created with default attributes When user "Brian" tries to search for user "" using Graph API Then the HTTP status code should be "400" And the JSON data of the response should match diff --git a/tests/acceptance/features/apiGraphUserGroup/getUserOwnInformation.feature b/tests/acceptance/features/apiGraphUserGroup/getUserOwnInformation.feature index 5f9458bf39..588ff15556 100644 --- a/tests/acceptance/features/apiGraphUserGroup/getUserOwnInformation.feature +++ b/tests/acceptance/features/apiGraphUserGroup/getUserOwnInformation.feature @@ -4,7 +4,7 @@ Feature: get user's own information So that I can see my information Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: user gets his/her own information with no group involvement diff --git a/tests/acceptance/features/apiGraphUserGroup/removeUserFromGroup.feature b/tests/acceptance/features/apiGraphUserGroup/removeUserFromGroup.feature index de7391a489..986b620af0 100644 --- a/tests/acceptance/features/apiGraphUserGroup/removeUserFromGroup.feature +++ b/tests/acceptance/features/apiGraphUserGroup/removeUserFromGroup.feature @@ -4,7 +4,7 @@ Feature: remove a user from a group So that I can manage user access to group resources Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: admin removes a user from a group @@ -157,7 +157,7 @@ Feature: remove a user from a group Scenario Outline: non-admin user tries to remove a user from a nonexistent group - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Alice" using the Graph API When user "Alice" tries to remove user "Brian" from a nonexistent group using the Graph API Then the HTTP status code should be "403" @@ -169,7 +169,7 @@ Feature: remove a user from a group @issue-5938 Scenario Outline: user other than the admin can't remove a user from their group - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "" to user "Brian" using the Graph API And group "grp1" has been created And user "Alice" has been added to group "grp1" diff --git a/tests/acceptance/features/apiGraphUserGroup/searchUserIncludingEmail.feature b/tests/acceptance/features/apiGraphUserGroup/searchUserIncludingEmail.feature index c087b22452..a53cc0f7a8 100644 --- a/tests/acceptance/features/apiGraphUserGroup/searchUserIncludingEmail.feature +++ b/tests/acceptance/features/apiGraphUserGroup/searchUserIncludingEmail.feature @@ -2,7 +2,7 @@ Feature: edit/search user including email Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And the user "Alice" has created a new user with the following attributes: | userName | Brian | diff --git a/tests/acceptance/features/apiLocks/lockFiles.feature b/tests/acceptance/features/apiLocks/lockFiles.feature index 30c92ce9ff..4cd24c317f 100644 --- a/tests/acceptance/features/apiLocks/lockFiles.feature +++ b/tests/acceptance/features/apiLocks/lockFiles.feature @@ -3,7 +3,7 @@ Feature: lock files I want to lock files Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -335,7 +335,7 @@ Feature: lock files @issue-7638 @issue-7599 Scenario Outline: locking a file in a received share does not lock other items with the same name in other received shares (shares from different users) Given using DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Alice" has created folder "FromAlice" And user "Brian" has created folder "FromBrian" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/FromAlice/textfile0.txt" diff --git a/tests/acceptance/features/apiLocks/unlockFiles.feature b/tests/acceptance/features/apiLocks/unlockFiles.feature index bbcff8fbc7..a8e1f79e3a 100644 --- a/tests/acceptance/features/apiLocks/unlockFiles.feature +++ b/tests/acceptance/features/apiLocks/unlockFiles.feature @@ -4,7 +4,7 @@ Feature: unlock locked items So that other users can make changes to the resources Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: unlock file locked by the user @@ -93,7 +93,7 @@ Feature: unlock locked items @issue-7767 Scenario Outline: trying to unlock a shared file that has been locked by the file owner - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "PARENT" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt" @@ -121,7 +121,7 @@ Feature: unlock locked items @issue-7767 Scenario Outline: trying to unlock a file inside the shared folder that has been locked by the file owner - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "PARENT" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt" @@ -149,7 +149,7 @@ Feature: unlock locked items @issue-7599 Scenario Outline: sharee unlocks a shared file - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "PARENT" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt" @@ -177,7 +177,7 @@ Feature: unlock locked items @issue-7599 Scenario Outline: try to unlock a shared file locked by the receiver - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "PARENT" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt" @@ -205,7 +205,7 @@ Feature: unlock locked items @issue-7599 Scenario Outline: try to unlock a file in a shared folder, which was locked by the sharee as the owner - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "PARENT" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt" @@ -276,7 +276,7 @@ Feature: unlock locked items Scenario: unlock a file in the shares using file-id - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using spaces DAV path And user "Alice" has uploaded a file inside space "Alice Hansen" with content "some content" to "textfile.txt" And we save it into "FILEID" diff --git a/tests/acceptance/features/apiNotification/deleteNotification.feature b/tests/acceptance/features/apiNotification/deleteNotification.feature index eb63e1a3e1..1e7ac96b48 100644 --- a/tests/acceptance/features/apiNotification/deleteNotification.feature +++ b/tests/acceptance/features/apiNotification/deleteNotification.feature @@ -4,7 +4,7 @@ Feature: Delete notification So that I can filter notifications Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiNotification/deprovisioningNotification.feature b/tests/acceptance/features/apiNotification/deprovisioningNotification.feature index 44cf878f92..1d4649f7cd 100644 --- a/tests/acceptance/features/apiNotification/deprovisioningNotification.feature +++ b/tests/acceptance/features/apiNotification/deprovisioningNotification.feature @@ -5,7 +5,7 @@ Feature: Deprovisioning notification So they can download and save their data in time Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | diff --git a/tests/acceptance/features/apiNotification/emailNotification.feature b/tests/acceptance/features/apiNotification/emailNotification.feature index b3c6a9c093..98ef0a8aa4 100644 --- a/tests/acceptance/features/apiNotification/emailNotification.feature +++ b/tests/acceptance/features/apiNotification/emailNotification.feature @@ -5,7 +5,7 @@ Feature: Email notification So that I can stay updated about the events Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -45,7 +45,7 @@ Feature: Email notification Scenario: group members get an email notification when someone shares a project space with the group Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "group1" has been created And user "Brian" has been added to group "group1" And user "Carol" has been added to group "group1" @@ -74,7 +74,7 @@ Feature: Email notification Scenario: group members get an email notification in their respective languages when someone shares a folder with the group - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "group1" has been created And user "Brian" has been added to group "group1" And user "Carol" has been added to group "group1" @@ -103,7 +103,7 @@ Feature: Email notification Scenario: group members get an email notification in their respective languages when someone shares a file with the group - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "group1" has been created And user "Brian" has been added to group "group1" And user "Carol" has been added to group "group1" @@ -133,7 +133,7 @@ Feature: Email notification @skipOnStable3.0 Scenario: group members get an email notification in their respective languages when someone shares a space with the group Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "group1" has been created And user "Brian" has been added to group "group1" And user "Carol" has been added to group "group1" @@ -186,7 +186,7 @@ Feature: Email notification @env-config Scenario: group members get an email notification in default language when someone shares a file with the group Given the config "OCIS_DEFAULT_LANGUAGE" has been set to "de" - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "group1" has been created And user "Brian" has been added to group "group1" And user "Carol" has been added to group "group1" diff --git a/tests/acceptance/features/apiNotification/notification.feature b/tests/acceptance/features/apiNotification/notification.feature index 57ab9792e7..1d1feaad8c 100644 --- a/tests/acceptance/features/apiNotification/notification.feature +++ b/tests/acceptance/features/apiNotification/notification.feature @@ -4,7 +4,7 @@ Feature: Notification So that I can stay updated about the information Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiNotification/spaceNotification.feature b/tests/acceptance/features/apiNotification/spaceNotification.feature index 7383ae8500..79f133438d 100644 --- a/tests/acceptance/features/apiNotification/spaceNotification.feature +++ b/tests/acceptance/features/apiNotification/spaceNotification.feature @@ -4,7 +4,7 @@ Feature: Notification So that I can stay updated about the spaces Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiOcm/acceptInvitation.feature b/tests/acceptance/features/apiOcm/acceptInvitation.feature index 08fb46f649..25d2cea1c9 100755 --- a/tests/acceptance/features/apiOcm/acceptInvitation.feature +++ b/tests/acceptance/features/apiOcm/acceptInvitation.feature @@ -4,9 +4,9 @@ Feature: accepting invitation I can accept invitations from users of other ocis instances Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using server "REMOTE" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | diff --git a/tests/acceptance/features/apiOcm/createInvitation.feature b/tests/acceptance/features/apiOcm/createInvitation.feature index b4f873ac70..5aeb004348 100755 --- a/tests/acceptance/features/apiOcm/createInvitation.feature +++ b/tests/acceptance/features/apiOcm/createInvitation.feature @@ -4,7 +4,7 @@ Feature: create invitation I can create an invitations and send it to the person I want to share with Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: user creates invitation @@ -79,7 +79,7 @@ Feature: create invitation @email @issue-10059 Scenario: federated user gets an email notification if their email was specified when creating the federation share invitation Given using server "REMOTE" - And user "David" has been created with default attributes and without skeleton files + And user "David" has been created with default attributes And using server "LOCAL" When "Alice" has created the federation share invitation with email "david@example.com" and description "a share invitation from Alice" And user "David" should have received the following email from user "Alice" ignoring whitespaces diff --git a/tests/acceptance/features/apiOcm/deleteFederatedConnections.feature b/tests/acceptance/features/apiOcm/deleteFederatedConnections.feature index ed0ebe6ba1..960f796ff6 100755 --- a/tests/acceptance/features/apiOcm/deleteFederatedConnections.feature +++ b/tests/acceptance/features/apiOcm/deleteFederatedConnections.feature @@ -4,9 +4,9 @@ Feature: delete federated connections I want to delete federated connections if they are no longer needed Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using server "REMOTE" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes Scenario: federated user deletes the federated connection diff --git a/tests/acceptance/features/apiOcm/searchFederationUsers.feature b/tests/acceptance/features/apiOcm/searchFederationUsers.feature index 61dc4a8e3d..08caa95c8d 100755 --- a/tests/acceptance/features/apiOcm/searchFederationUsers.feature +++ b/tests/acceptance/features/apiOcm/searchFederationUsers.feature @@ -5,12 +5,12 @@ Feature: search federation users Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Carol | And using server "REMOTE" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes Scenario: users search for federation users by display name diff --git a/tests/acceptance/features/apiOcm/share.feature b/tests/acceptance/features/apiOcm/share.feature index 5ce6bbcca1..e81431b4fd 100755 --- a/tests/acceptance/features/apiOcm/share.feature +++ b/tests/acceptance/features/apiOcm/share.feature @@ -4,9 +4,9 @@ Feature: an user shares resources using ScienceMesh application I want to share resources between different ocis instances Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using server "REMOTE" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes @issue-9534 Scenario Outline: local user shares resources to federation user diff --git a/tests/acceptance/features/apiReshare/resharing.feature b/tests/acceptance/features/apiReshare/resharing.feature index 65e359533b..15c9b10f88 100644 --- a/tests/acceptance/features/apiReshare/resharing.feature +++ b/tests/acceptance/features/apiReshare/resharing.feature @@ -4,7 +4,7 @@ Feature: re-share resources This feature has been removed from ocis Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSearch1/dateSearch.feature b/tests/acceptance/features/apiSearch1/dateSearch.feature index 706b90153d..2c3e314667 100644 --- a/tests/acceptance/features/apiSearch1/dateSearch.feature +++ b/tests/acceptance/features/apiSearch1/dateSearch.feature @@ -3,7 +3,7 @@ Feature: date search I want to do search resources by date Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-7060 @issue-10329 Scenario Outline: search resources using different dav path @@ -51,7 +51,7 @@ Feature: date search @issue-10329 Scenario: search resources using different search patterns (KQL feature) in the shares folder - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using spaces DAV path And user "Alice" has created folder "sharedFolder" And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/sharedFolder/yesterday.txt" with mtime "yesterday" via TUS inside of the space "Personal" using the WebDAV API diff --git a/tests/acceptance/features/apiSearch1/search.feature b/tests/acceptance/features/apiSearch1/search.feature index 2446276621..977269d2e2 100644 --- a/tests/acceptance/features/apiSearch1/search.feature +++ b/tests/acceptance/features/apiSearch1/search.feature @@ -4,7 +4,7 @@ Feature: Search So that I can get them quickly Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSearch2/mediaTypeSearch.feature b/tests/acceptance/features/apiSearch2/mediaTypeSearch.feature index 97a20914b0..be9cdaff0f 100644 --- a/tests/acceptance/features/apiSearch2/mediaTypeSearch.feature +++ b/tests/acceptance/features/apiSearch2/mediaTypeSearch.feature @@ -4,7 +4,7 @@ Feature: media type search So that I can find the files with specific media type Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSearch2/tagSearch.feature b/tests/acceptance/features/apiSearch2/tagSearch.feature index 2f2d01cdcc..5361e907d5 100644 --- a/tests/acceptance/features/apiSearch2/tagSearch.feature +++ b/tests/acceptance/features/apiSearch2/tagSearch.feature @@ -4,7 +4,7 @@ Feature: tag search So that I can find the files with the tag I am looking for Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-10329 Scenario Outline: search files by tag @@ -118,7 +118,7 @@ Feature: tag search @issue-10329 Scenario Outline: sharee searches shared files using a tag Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "uploadFolder" And user "Alice" has uploaded file with content "hello world" to "uploadFolder/file1.txt" And user "Alice" has uploaded file with content "Namaste nepal" to "uploadFolder/file2.txt" @@ -152,7 +152,7 @@ Feature: tag search @issue-10329 Scenario Outline: sharee searches shared project space files using a tag Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "tag-space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: diff --git a/tests/acceptance/features/apiSearchContent/contentSearch.feature b/tests/acceptance/features/apiSearchContent/contentSearch.feature index 96788555a0..327d613cb5 100644 --- a/tests/acceptance/features/apiSearchContent/contentSearch.feature +++ b/tests/acceptance/features/apiSearchContent/contentSearch.feature @@ -5,7 +5,7 @@ Feature: content search So that I can find the files with the content I am looking for Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-10329 Scenario Outline: search files by content @@ -86,7 +86,7 @@ Feature: content search @issue-10329 Scenario Outline: sharee searches files by content Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "uploadFolder" And user "Alice" has uploaded file with content "hello world from nepal" to "uploadFolder/keywordAtStart.txt" And user "Alice" has uploaded file with content "saying hello to the world" to "uploadFolder/keywordAtMiddle.txt" @@ -189,7 +189,7 @@ Feature: content search @issue-10329 Scenario Outline: sharee searches shared project space files by content Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: diff --git a/tests/acceptance/features/apiSearchContent/extractedProps.feature b/tests/acceptance/features/apiSearchContent/extractedProps.feature index 7d5d606188..db36bf33be 100644 --- a/tests/acceptance/features/apiSearchContent/extractedProps.feature +++ b/tests/acceptance/features/apiSearchContent/extractedProps.feature @@ -5,7 +5,7 @@ Feature: propfind extracted props So that I can make sure that the response contains audio, location, image and photo properties Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using spaces DAV path @@ -78,7 +78,7 @@ Feature: propfind extracted props Scenario: check extracted properties of a file by sharee from shares space - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | And user "Alice" has uploaded file "filesForUpload/testaudio.mp3" to "testaudio.mp3" @@ -392,7 +392,7 @@ Feature: propfind extracted props Scenario: GET extracted properties of an audio file (Shares space) - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded a file "filesForUpload/testaudio.mp3" to "testaudio.mp3" in space "Personal" And user "Alice" has sent the following resource share invitation: | resource | testaudio.mp3 | @@ -448,7 +448,7 @@ Feature: propfind extracted props Scenario: GET extracted properties of an image file (Shares space) - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded a file "filesForUpload/testavatar.jpg" to "testavatar.jpg" in space "Personal" And user "Alice" has sent the following resource share invitation: | resource | testavatar.jpg | diff --git a/tests/acceptance/features/apiSharingNg1/enableDisableShareSync.feature b/tests/acceptance/features/apiSharingNg1/enableDisableShareSync.feature index 7d330cb482..abf805988d 100644 --- a/tests/acceptance/features/apiSharingNg1/enableDisableShareSync.feature +++ b/tests/acceptance/features/apiSharingNg1/enableDisableShareSync.feature @@ -4,7 +4,7 @@ Feature: enable or disable sync of incoming shares So that I can filter out the files and folder shared with Me Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -91,7 +91,7 @@ Feature: enable or disable sync of incoming shares Scenario Outline: enable a group share sync by only one user in a group - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -130,7 +130,7 @@ Feature: enable or disable sync of incoming shares Scenario Outline: disable group share sync by only one user in a group - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -237,7 +237,7 @@ Feature: enable or disable sync of incoming shares Scenario Outline: enable a group share sync shared from Project Space by only one user in a group - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Carol" using the Graph API And group "grp1" has been created And user "Alice" has been added to group "grp1" @@ -278,7 +278,7 @@ Feature: enable or disable sync of incoming shares Scenario Outline: disable group share sync shared from Project space by only one user in a group - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Carol" using the Graph API And group "grp1" has been created And user "Alice" has been added to group "grp1" diff --git a/tests/acceptance/features/apiSharingNg1/listPermissions.feature b/tests/acceptance/features/apiSharingNg1/listPermissions.feature index 5b5c3dd881..72f627f524 100644 --- a/tests/acceptance/features/apiSharingNg1/listPermissions.feature +++ b/tests/acceptance/features/apiSharingNg1/listPermissions.feature @@ -2,7 +2,7 @@ Feature: List a sharing permissions https://owncloud.dev/libre-graph-api/#/drives.permissions/ListPermissions Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | @@ -168,7 +168,7 @@ Feature: List a sharing permissions Scenario: user lists permissions of a project space Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API When user "Alice" lists the permissions of space "new-space" using permissions endpoint of the Graph API @@ -291,7 +291,7 @@ Feature: List a sharing permissions @issues-8352 Scenario Outline: sharer lists permissions of a shared project space Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: @@ -897,7 +897,7 @@ Feature: List a sharing permissions @issues-8331 Scenario: user sends share invitation with all allowed roles for a file Given user "Alice" has uploaded file with content "hello text" to "textfile.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" gets permissions list for file "textfile.txt" of the space "Personal" using the Graph API Then the HTTP status code should be "200" And user "Alice" should be able to send the following resource share invitation with all allowed permission roles @@ -909,7 +909,7 @@ Feature: List a sharing permissions @issues-8331 Scenario: user sends share invitation with all allowed roles for a folder Given user "Alice" has created folder "folder" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" gets permissions list for folder "folder" of the space "Personal" using the Graph API Then the HTTP status code should be "200" And user "Alice" should be able to send the following resource share invitation with all allowed permission roles @@ -1191,7 +1191,7 @@ Feature: List a sharing permissions Given using spaces DAV path And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" lists the permissions of space "new-space" using permissions endpoint of the Graph API Then the HTTP status code should be "200" And user "Alice" should be able to send the following resource share invitation with all allowed permission roles @@ -1205,7 +1205,7 @@ Feature: List a sharing permissions And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "new-space" with content "hello world" to "textfile.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" gets permissions list for file "textfile.txt" of the space "new-space" using the Graph API Then the HTTP status code should be "200" And user "Alice" should be able to send the following resource share invitation with all allowed permission roles @@ -1218,7 +1218,7 @@ Feature: List a sharing permissions Scenario: non-member user tries to list the permissions of a project space using permissions endpoint Given using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created a space "new-space" with the default quota using the Graph API When user "Brian" tries to list the permissions of space "new-space" owned by "Alice" using permissions endpoint of the Graph API Then the HTTP status code should be "404" @@ -1262,7 +1262,7 @@ Feature: List a sharing permissions And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has created a folder "folder" in space "new-space" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" gets permissions list for folder "folder" of the space "new-space" using the Graph API Then the HTTP status code should be "200" And user "Alice" should be able to send the following resource share invitation with all allowed permission roles @@ -1274,7 +1274,7 @@ Feature: List a sharing permissions Scenario: try to list the permissions of other user's personal space Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Brian" tries to list the permissions of space "Personal" owned by "Alice" using permissions endpoint of the Graph API Then the HTTP status code should be "404" And the JSON data of the response should match @@ -1314,7 +1314,7 @@ Feature: List a sharing permissions Scenario Outline: sharer lists permissions of a shared project space using root endpoint Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: @@ -1593,7 +1593,7 @@ Feature: List a sharing permissions Given using spaces DAV path And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" lists the permissions of space "new-space" using root endpoint of the Graph API Then the HTTP status code should be "200" And user "Alice" should be able to send the following space share invitation with all allowed permission roles using root endpoint of the Graph API @@ -1605,7 +1605,7 @@ Feature: List a sharing permissions Scenario: non-member user tries to list the permissions of a project space using root endpoint Given using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created a space "new-space" with the default quota using the Graph API When user "Brian" tries to list the permissions of space "new-space" owned by "Alice" using root endpoint of the Graph API Then the HTTP status code should be "404" @@ -1784,7 +1784,7 @@ Feature: List a sharing permissions @issues-8428 Scenario: user lists permissions of a shared folder in personal space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "folder" And user "Alice" has sent the following resource share invitation: | resource | folder | @@ -1889,7 +1889,7 @@ Feature: List a sharing permissions @issues-8428 Scenario: user lists permissions of a shared file in personal space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "hello world" to "/textfile0.txt" And user "Alice" has sent the following resource share invitation: | resource | textfile0.txt | @@ -1991,7 +1991,7 @@ Feature: List a sharing permissions @issues-8428 Scenario: user lists permissions of a shared folder in project space Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has created a folder "folder" in space "new-space" @@ -2099,7 +2099,7 @@ Feature: List a sharing permissions @issues-8428 Scenario: user lists permissions of a shared file in project space Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "new-space" with content "hello world" to "textfile0.txt" diff --git a/tests/acceptance/features/apiSharingNg1/propfindShares.feature b/tests/acceptance/features/apiSharingNg1/propfindShares.feature index 897761d600..5e60d8e901 100644 --- a/tests/acceptance/features/apiSharingNg1/propfindShares.feature +++ b/tests/acceptance/features/apiSharingNg1/propfindShares.feature @@ -4,7 +4,7 @@ Feature: propfind a shares So that I can make sure that the response contains all the relevant values Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSharingNg1/removeAccessToDrive.feature b/tests/acceptance/features/apiSharingNg1/removeAccessToDrive.feature index 1a117a4d5b..175edd94c4 100644 --- a/tests/acceptance/features/apiSharingNg1/removeAccessToDrive.feature +++ b/tests/acceptance/features/apiSharingNg1/removeAccessToDrive.feature @@ -2,7 +2,7 @@ Feature: Remove access to a drive https://owncloud.dev/libre-graph-api/#/drives.root/DeletePermissionSpaceRoot Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSharingNg1/removeAccessToDriveItem.feature b/tests/acceptance/features/apiSharingNg1/removeAccessToDriveItem.feature index 23299dfdf2..f7af530046 100644 --- a/tests/acceptance/features/apiSharingNg1/removeAccessToDriveItem.feature +++ b/tests/acceptance/features/apiSharingNg1/removeAccessToDriveItem.feature @@ -2,7 +2,7 @@ Feature: Remove access to a drive item https://owncloud.dev/libre-graph-api/#/drives.permissions/DeletePermission Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSharingNg1/sharedByMe.feature b/tests/acceptance/features/apiSharingNg1/sharedByMe.feature index ad9e0c172f..71c85b51e6 100644 --- a/tests/acceptance/features/apiSharingNg1/sharedByMe.feature +++ b/tests/acceptance/features/apiSharingNg1/sharedByMe.feature @@ -6,7 +6,7 @@ Feature: resources shared by user https://owncloud.dev/libre-graph-api/#/me.drive/ListSharedByMe Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSharingNg1/sharedWithMe.feature b/tests/acceptance/features/apiSharingNg1/sharedWithMe.feature index 0e10a6cee6..65cf39ff4a 100755 --- a/tests/acceptance/features/apiSharingNg1/sharedWithMe.feature +++ b/tests/acceptance/features/apiSharingNg1/sharedWithMe.feature @@ -6,7 +6,7 @@ Feature: an user gets the resources shared to them https://owncloud.dev/libre-graph-api/#/me.drive/ListSharedWithMe Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -1855,7 +1855,7 @@ Feature: an user gets the resources shared to them Scenario: sharee lists the same name file shares received from different users (Personal space) - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And user "Alice" has uploaded file with content "to share" to "textfile.txt" And user "Carol" has uploaded file with content "to share" to "textfile.txt" And user "Alice" has sent the following resource share invitation: @@ -2137,7 +2137,7 @@ Feature: an user gets the resources shared to them Scenario: sharee lists the same name folder shares received from different users (Personal space) - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And user "Alice" has created folder "folderToShare" And user "Carol" has created folder "folderToShare" And user "Alice" has sent the following resource share invitation: @@ -2419,7 +2419,7 @@ Feature: an user gets the resources shared to them @issue-8471 Scenario: sharee lists the same name file and folder shares received from different users (Personal space) Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Brian" has created folder "folder" And user "Brian" has uploaded file with content "hello world" to "/textfile.txt" And user "Carol" has created folder "folder" diff --git a/tests/acceptance/features/apiSharingNg1/sharedWithMeSyncDisabled.feature b/tests/acceptance/features/apiSharingNg1/sharedWithMeSyncDisabled.feature index 799ca55ac3..07d8270fd6 100644 --- a/tests/acceptance/features/apiSharingNg1/sharedWithMeSyncDisabled.feature +++ b/tests/acceptance/features/apiSharingNg1/sharedWithMeSyncDisabled.feature @@ -6,7 +6,7 @@ Feature: listing sharedWithMe when auto-sync is disabled https://owncloud.dev/libre-graph-api/#/me.drive/ListSharedWithMe Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -2223,7 +2223,7 @@ Feature: listing sharedWithMe when auto-sync is disabled Scenario: user lists the file with same name shared by two users with him/her - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And user "Alice" has uploaded file with content "to share" to "textfile.txt" And user "Carol" has uploaded file with content "to share" to "textfile.txt" And user "Alice" has sent the following resource share invitation: @@ -2520,7 +2520,7 @@ Feature: listing sharedWithMe when auto-sync is disabled Scenario: user lists the folder with same name shared by two users with him/her - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And user "Alice" has created folder "folderToShare" And user "Carol" has created folder "folderToShare" And user "Alice" has sent the following resource share invitation: @@ -3160,7 +3160,7 @@ Feature: listing sharedWithMe when auto-sync is disabled Scenario: sharee lists the files with same name shared from different project-spaces - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And the administrator has assigned the role "Space Admin" to user "Carol" using the Graph API @@ -3479,7 +3479,7 @@ Feature: listing sharedWithMe when auto-sync is disabled Scenario: sharee lists the folders with same name shared from different project-spaces - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And the administrator has assigned the role "Space Admin" to user "Carol" using the Graph API diff --git a/tests/acceptance/features/apiSharingNg2/removeAccessToDriveItemInLinkShare.feature b/tests/acceptance/features/apiSharingNg2/removeAccessToDriveItemInLinkShare.feature index 2da121151c..0207864670 100644 --- a/tests/acceptance/features/apiSharingNg2/removeAccessToDriveItemInLinkShare.feature +++ b/tests/acceptance/features/apiSharingNg2/removeAccessToDriveItemInLinkShare.feature @@ -2,7 +2,7 @@ Feature: Remove access to a drive item https://owncloud.dev/libre-graph-api/#/drives.permissions/DeletePermission Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSharingNgLinkSharePermission/createLinkShare.feature b/tests/acceptance/features/apiSharingNgLinkSharePermission/createLinkShare.feature index 7248b4058b..17834133a7 100644 --- a/tests/acceptance/features/apiSharingNgLinkSharePermission/createLinkShare.feature +++ b/tests/acceptance/features/apiSharingNgLinkSharePermission/createLinkShare.feature @@ -2,7 +2,7 @@ Feature: Create a link share for a resource https://owncloud.dev/libre-graph-api/#/drives.permissions/CreateLink Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | @@ -2389,7 +2389,7 @@ Feature: Create a link share for a resource And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "projectSpace" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "projectSpace" with content "to share" to "textfile.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following space share invitation: | space | projectSpace | | sharee | Brian | @@ -2458,7 +2458,7 @@ Feature: Create a link share for a resource And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "projectSpace" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "projectSpace" with content "to share" to "textfile.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following space share invitation: | space | projectSpace | | sharee | Brian | @@ -2527,7 +2527,7 @@ Feature: Create a link share for a resource And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "projectSpace" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "projectSpace" with content "to share" to "textfile.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following space share invitation: | space | projectSpace | | sharee | Brian | @@ -2598,7 +2598,7 @@ Feature: Create a link share for a resource And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "projectSpace" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "projectSpace" with content "to share" to "textfile.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following space share invitation: | space | projectSpace | | sharee | Brian | @@ -2669,7 +2669,7 @@ Feature: Create a link share for a resource And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "projectSpace" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "projectSpace" with content "to share" to "textfile.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following space share invitation: | space | projectSpace | | sharee | Brian | @@ -2720,7 +2720,7 @@ Feature: Create a link share for a resource And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "projectSpace" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "projectSpace" with content "to share" to "textfile.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following space share invitation: | space | projectSpace | | sharee | Brian | diff --git a/tests/acceptance/features/apiSharingNgLinkSharePermission/updateLinkShare.feature b/tests/acceptance/features/apiSharingNgLinkSharePermission/updateLinkShare.feature index ad13dc68a4..37a27dd015 100644 --- a/tests/acceptance/features/apiSharingNgLinkSharePermission/updateLinkShare.feature +++ b/tests/acceptance/features/apiSharingNgLinkSharePermission/updateLinkShare.feature @@ -2,7 +2,7 @@ Feature: Update a link share for a resource https://owncloud.dev/libre-graph-api/#/drives.permissions/CreateLink Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | diff --git a/tests/acceptance/features/apiSharingNgLinkShareRoot/createLinkShare.feature b/tests/acceptance/features/apiSharingNgLinkShareRoot/createLinkShare.feature index f0ef2d61ab..4ce9685b5f 100644 --- a/tests/acceptance/features/apiSharingNgLinkShareRoot/createLinkShare.feature +++ b/tests/acceptance/features/apiSharingNgLinkShareRoot/createLinkShare.feature @@ -2,7 +2,7 @@ Feature: Create a link share for a resource https://owncloud.dev/libre-graph-api/#/drives.permissions/CreateLink Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | diff --git a/tests/acceptance/features/apiSharingNgLinkShareRoot/updateLinkShare.feature b/tests/acceptance/features/apiSharingNgLinkShareRoot/updateLinkShare.feature index c462bb5c7c..b86d8d4251 100644 --- a/tests/acceptance/features/apiSharingNgLinkShareRoot/updateLinkShare.feature +++ b/tests/acceptance/features/apiSharingNgLinkShareRoot/updateLinkShare.feature @@ -2,7 +2,7 @@ Feature: Update a link share for a resource https://owncloud.dev/libre-graph-api/#/drives.permissions/CreateLink Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | diff --git a/tests/acceptance/features/apiSharingNgShareInvitation/shareInvitations.feature b/tests/acceptance/features/apiSharingNgShareInvitation/shareInvitations.feature index e3aff5c96c..7c6379e52a 100644 --- a/tests/acceptance/features/apiSharingNgShareInvitation/shareInvitations.feature +++ b/tests/acceptance/features/apiSharingNgShareInvitation/shareInvitations.feature @@ -6,7 +6,7 @@ Feature: Send a sharing invitations https://owncloud.dev/libre-graph-api/#/drives.permissions/Invite Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -97,7 +97,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation to group with different roles - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -368,7 +368,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation for a file to group with different permissions - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -462,7 +462,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation for a folder to group with different permissions - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -649,7 +649,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation with expiration date to group with different roles - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -828,7 +828,7 @@ Feature: Send a sharing invitations Scenario Outline: send sharing invitation to a deleted group with different roles - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -927,7 +927,7 @@ Feature: Send a sharing invitations Scenario Outline: try to send sharing invitation to multiple groups - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Carol | | Bob | @@ -984,7 +984,7 @@ Feature: Send a sharing invitations Scenario Outline: try to send sharing invitation to user and group at once - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Carol | | Bob | @@ -1083,7 +1083,7 @@ Feature: Send a sharing invitations Scenario Outline: send sharing invitation to already shared group - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -1267,7 +1267,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation to group with wrong recipient type - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And user "Alice" has uploaded file with content "to share" to "textfile1.txt" And user "Alice" has created folder "FolderToShare" And group "grp1" has been created @@ -1357,7 +1357,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation to group with empty recipient type - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And user "Alice" has uploaded file with content "to share" to "textfile1.txt" And user "Alice" has created folder "FolderToShare" And group "grp1" has been created @@ -1707,7 +1707,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation for project space to group with different roles (permissions endpoint) Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -1793,7 +1793,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation for disabled project space to group with different roles (permissions endpoint) Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -1844,7 +1844,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation for deleted project space to group with different roles (permissions endpoint) Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -1934,7 +1934,7 @@ Feature: Send a sharing invitations Scenario: send share invitation to group for deleted file - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -2065,7 +2065,7 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation for project space resource to group with different roles (permissions endpoint) Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -2437,7 +2437,7 @@ Feature: Send a sharing invitations Scenario Outline: try to invite multiple users to project space with different roles using root endpoint Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "NewSpace" with the default quota using the Graph API When user "Alice" tries to send the following space share invitation using root endpoint of the Graph API: @@ -2536,7 +2536,7 @@ Feature: Send a sharing invitations Scenario Outline: try to invite multiple groups at once to project space with different roles using root endpoint Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "grp1" has been created And group "grp2" has been created And the following users have been added to the following groups @@ -2645,7 +2645,7 @@ Feature: Send a sharing invitations Scenario Outline: try to invite user and group at once to project space with different roles using root endpoint Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "grp1" has been created And the following users have been added to the following groups | username | groupname | @@ -3106,7 +3106,7 @@ Feature: Send a sharing invitations Scenario: share a file to user and group having same name (Personal space) - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And group "Brian" has been created And the following users have been added to the following groups | username | groupname | @@ -3151,7 +3151,7 @@ Feature: Send a sharing invitations Scenario: share a file to user and group having same name (Project space) Given using spaces DAV path - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "NewSpace" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "NewSpace" with content "lorem" to "textfile.txt" diff --git a/tests/acceptance/features/apiSharingNgShareInvitation/updateShareInvitations.feature b/tests/acceptance/features/apiSharingNgShareInvitation/updateShareInvitations.feature index a411bf5296..a16350bd6d 100644 --- a/tests/acceptance/features/apiSharingNgShareInvitation/updateShareInvitations.feature +++ b/tests/acceptance/features/apiSharingNgShareInvitation/updateShareInvitations.feature @@ -5,7 +5,7 @@ Feature: Update permission of a share https://owncloud.dev/libre-graph-api/#/drives.permissions/UpdatePermission Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/changeSpaces.feature b/tests/acceptance/features/apiSpaces/changeSpaces.feature index 18f7dd6da4..8222adb6c1 100644 --- a/tests/acceptance/features/apiSpaces/changeSpaces.feature +++ b/tests/acceptance/features/apiSpaces/changeSpaces.feature @@ -7,7 +7,7 @@ Feature: Change data of space See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -570,7 +570,7 @@ Feature: Change data of space Scenario: user sends PATCH request to other user's space that they don't have access to - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Carol | When user "Carol" sends PATCH request to the space "Personal" of user "Alice" with data "{}" @@ -581,7 +581,7 @@ Feature: Change data of space @env-config Scenario Outline: space member with role 'Space Editor Without Versions' and Space Editor edits the space Given the administrator has enabled the permissions role "Space Editor Without Versions" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Carol | And user "Alice" has sent the following space share invitation: diff --git a/tests/acceptance/features/apiSpaces/createSpace.feature b/tests/acceptance/features/apiSpaces/createSpace.feature index 2e9afaff26..c463560a31 100644 --- a/tests/acceptance/features/apiSpaces/createSpace.feature +++ b/tests/acceptance/features/apiSpaces/createSpace.feature @@ -4,7 +4,7 @@ Feature: create space So that I can organize a set of resources in a hierarchical tree Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-5938 Scenario Outline: user with role user and user light can't create space via Graph API diff --git a/tests/acceptance/features/apiSpaces/disableAndDeleteSpaces.feature b/tests/acceptance/features/apiSpaces/disableAndDeleteSpaces.feature index f099191d0a..54bb1be107 100644 --- a/tests/acceptance/features/apiSpaces/disableAndDeleteSpaces.feature +++ b/tests/acceptance/features/apiSpaces/disableAndDeleteSpaces.feature @@ -7,7 +7,7 @@ Feature: Disabling and deleting space See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature b/tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature index c55f9f6b29..b039b7933b 100644 --- a/tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature +++ b/tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature @@ -9,7 +9,7 @@ Feature: A manager of the space can edit public link See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/filePreviews.feature b/tests/acceptance/features/apiSpaces/filePreviews.feature index 4f7ae0f94a..baa732113c 100644 --- a/tests/acceptance/features/apiSpaces/filePreviews.feature +++ b/tests/acceptance/features/apiSpaces/filePreviews.feature @@ -7,7 +7,7 @@ Feature: Preview file in project space See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API @@ -44,7 +44,7 @@ Feature: Preview file in project space Scenario Outline: download preview of shared file inside project space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded a file from "" to "" via TUS inside of the space "previews of the files" using the WebDAV API And user "Alice" has sent the following resource share invitation: | resource | | @@ -63,7 +63,7 @@ Feature: Preview file in project space @env-config Scenario Outline: download preview of shared file shared via Secure viewer permission role - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has enabled the permissions role "Secure Viewer" And user "Alice" has uploaded a file from "" to "" via TUS inside of the space "Alice Hansen" using the WebDAV API And user "Alice" has sent the following resource share invitation: @@ -82,7 +82,7 @@ Feature: Preview file in project space Scenario: download preview of file inside shared folder in project space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created a folder "folder" in space "previews of the files" And user "Alice" has uploaded a file inside space "previews of the files" with content "test" to "/folder/lorem.txt" And user "Alice" has sent the following resource share invitation: diff --git a/tests/acceptance/features/apiSpaces/listSpaces.feature b/tests/acceptance/features/apiSpaces/listSpaces.feature index 25c0a8f8c9..7e8aabfdc2 100644 --- a/tests/acceptance/features/apiSpaces/listSpaces.feature +++ b/tests/acceptance/features/apiSpaces/listSpaces.feature @@ -7,7 +7,7 @@ Feature: List and create spaces See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using spaces DAV path @@ -78,7 +78,7 @@ Feature: List and create spaces Scenario: ordinary user can request information about their Space via the Graph API using a filter - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Brian" has created folder "folder" And user "Brian" has sent the following resource share invitation: | resource | folder | @@ -443,7 +443,7 @@ Feature: List and create spaces @issue-7160 Scenario Outline: get share jail space information of the user when user has a pending share - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has disabled auto-accepting And user "Brian" has uploaded file with content "this is a test file." to "test.txt" And the administrator has assigned the role "" to user "Alice" using the Graph API diff --git a/tests/acceptance/features/apiSpaces/publicLink.feature b/tests/acceptance/features/apiSpaces/publicLink.feature index 529d2d992a..5ecc8392e8 100644 --- a/tests/acceptance/features/apiSpaces/publicLink.feature +++ b/tests/acceptance/features/apiSpaces/publicLink.feature @@ -3,7 +3,7 @@ Feature: public link for a space Background: Given the config "OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD" has been set to "false" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | And using spaces DAV path diff --git a/tests/acceptance/features/apiSpaces/quota.feature b/tests/acceptance/features/apiSpaces/quota.feature index 7c0b1a32ec..bfd1d88654 100644 --- a/tests/acceptance/features/apiSpaces/quota.feature +++ b/tests/acceptance/features/apiSpaces/quota.feature @@ -14,7 +14,7 @@ Feature: State of the quota See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And using spaces DAV path @@ -125,14 +125,14 @@ Feature: State of the quota @env-config Scenario: upload a file by setting OCIS spaces max quota Given the config "OCIS_SPACES_MAX_QUOTA" has been set to "10" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Brian" uploads file with content "more than 10 bytes content" to "lorem.txt" using the WebDAV API Then the HTTP status code should be "507" @env-config Scenario: try to create a space with quota greater than OCIS spaces max quota Given the config "OCIS_SPACES_MAX_QUOTA" has been set to "50" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Brian" using the Graph API When user "Brian" tries to create a space "new space" of type "project" with quota "51" using the Graph API Then the HTTP status code should be "400" diff --git a/tests/acceptance/features/apiSpaces/removeSpaceObjects.feature b/tests/acceptance/features/apiSpaces/removeSpaceObjects.feature index 0526e66273..be958f4f2e 100644 --- a/tests/acceptance/features/apiSpaces/removeSpaceObjects.feature +++ b/tests/acceptance/features/apiSpaces/removeSpaceObjects.feature @@ -7,7 +7,7 @@ Feature: Remove files, folder See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/restoreSpaces.feature b/tests/acceptance/features/apiSpaces/restoreSpaces.feature index 6626964d11..f403ce872d 100644 --- a/tests/acceptance/features/apiSpaces/restoreSpaces.feature +++ b/tests/acceptance/features/apiSpaces/restoreSpaces.feature @@ -7,7 +7,7 @@ Feature: Restoring space See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/setQuota.feature b/tests/acceptance/features/apiSpaces/setQuota.feature index b069da3f0a..e023485779 100644 --- a/tests/acceptance/features/apiSpaces/setQuota.feature +++ b/tests/acceptance/features/apiSpaces/setQuota.feature @@ -4,7 +4,7 @@ Feature: Set quota So that users can only take up a certain amount of storage space Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/spaceManagement.feature b/tests/acceptance/features/apiSpaces/spaceManagement.feature index 8206fa7428..10c23f7252 100644 --- a/tests/acceptance/features/apiSpaces/spaceManagement.feature +++ b/tests/acceptance/features/apiSpaces/spaceManagement.feature @@ -10,7 +10,7 @@ Feature: Space management See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/tag.feature b/tests/acceptance/features/apiSpaces/tag.feature index 1267273049..8e7f379ea8 100644 --- a/tests/acceptance/features/apiSpaces/tag.feature +++ b/tests/acceptance/features/apiSpaces/tag.feature @@ -7,7 +7,7 @@ Feature: Tag See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/trashBin.feature b/tests/acceptance/features/apiSpaces/trashBin.feature index 61293da2c6..fa83f8b3a6 100644 --- a/tests/acceptance/features/apiSpaces/trashBin.feature +++ b/tests/acceptance/features/apiSpaces/trashBin.feature @@ -7,7 +7,7 @@ Feature: Restore files, folder See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpaces/tusUpload.feature b/tests/acceptance/features/apiSpaces/tusUpload.feature index 1c6400512c..34f561b841 100644 --- a/tests/acceptance/features/apiSpaces/tusUpload.feature +++ b/tests/acceptance/features/apiSpaces/tusUpload.feature @@ -4,7 +4,7 @@ Feature: upload resources using TUS protocol So that I can store and share files between multiple client systems Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API @@ -43,7 +43,7 @@ Feature: upload resources using TUS protocol @issue-10346 Scenario Outline: upload a zero-byte file inside a shared folder Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "testFolder" And user "Alice" has sent the following resource share invitation: | resource | testFolder | @@ -63,7 +63,7 @@ Feature: upload resources using TUS protocol Scenario: upload a zero-byte file inside a shared folder (spaces dav path) Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "testFolder" And user "Alice" has sent the following resource share invitation: | resource | testFolder | @@ -87,7 +87,7 @@ Feature: upload resources using TUS protocol @issue-8003 @issue-10346 Scenario Outline: replace a shared file with zero-byte file Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "This is TUS upload" to "textfile.txt" And user "Alice" has sent the following resource share invitation: | resource | textfile.txt | @@ -107,7 +107,7 @@ Feature: upload resources using TUS protocol @issue-8003 Scenario: replace a shared file with zero-byte file (spaces dav path) Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "This is TUS upload" to "textfile.txt" And user "Alice" has sent the following resource share invitation: | resource | textfile.txt | @@ -132,7 +132,7 @@ Feature: upload resources using TUS protocol @issue-8003 Scenario: replace a file inside a shared project space with zero-byte file Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "new-space" with content "This is TUS upload" to "textfile.txt" diff --git a/tests/acceptance/features/apiSpaces/uploadSpaces.feature b/tests/acceptance/features/apiSpaces/uploadSpaces.feature index a6e343c284..8ed3964b2d 100644 --- a/tests/acceptance/features/apiSpaces/uploadSpaces.feature +++ b/tests/acceptance/features/apiSpaces/uploadSpaces.feature @@ -7,7 +7,7 @@ Feature: Upload files into a space See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesDavOperation/copyByFileId.feature b/tests/acceptance/features/apiSpacesDavOperation/copyByFileId.feature index 85bf6982a6..7ec03e899f 100644 --- a/tests/acceptance/features/apiSpacesDavOperation/copyByFileId.feature +++ b/tests/acceptance/features/apiSpacesDavOperation/copyByFileId.feature @@ -5,7 +5,7 @@ Feature: copying file using file id Background: Given using spaces DAV path - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario: copy a file into a folder in personal space @@ -128,7 +128,7 @@ Feature: copying file using file id Scenario: copy a file from sub-folder to root folder inside Shares space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folder" And user "Alice" has created folder "folder/sub-folder" And user "Alice" has uploaded file with content "some data" to "/folder/sub-folder/test.txt" @@ -153,7 +153,7 @@ Feature: copying file using file id Scenario: copy a file from personal to share space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folder" And user "Alice" has sent the following resource share invitation: | resource | folder | @@ -176,7 +176,7 @@ Feature: copying file using file id Scenario Outline: copy a file from share to personal space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folder" And user "Alice" has uploaded file with content "some data" to "/folder/test.txt" And we save it into "FILEID" @@ -203,7 +203,7 @@ Feature: copying file using file id Scenario: sharee tries to copy a file from shares space with secure viewer to personal space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has enabled the permissions role "Secure Viewer" And user "Alice" has created folder "/folder" And user "Alice" has uploaded file with content "some data" to "/folder/test.txt" @@ -224,7 +224,7 @@ Feature: copying file using file id Scenario Outline: sharee copies a file from shares to project space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created folder "/folder" And user "Alice" has uploaded file with content "some data" to "/folder/test.txt" @@ -261,7 +261,7 @@ Feature: copying file using file id @env-config Scenario Outline: sharee tries to copy a file from shares to project space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has enabled the permissions role "Secure Viewer" And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created folder "/folder" @@ -299,7 +299,7 @@ Feature: copying file using file id Scenario Outline: sharee copies a file between shares spaces - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/share1" And user "Alice" has created folder "/share2" And user "Alice" has uploaded file with content "some data" to "/share1/test.txt" @@ -339,7 +339,7 @@ Feature: copying file using file id @env-config Scenario Outline: sharee tries to copy a file between shares space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has enabled the permissions role "Secure Viewer" And user "Alice" has created folder "/share1" And user "Alice" has created folder "/share2" @@ -384,7 +384,7 @@ Feature: copying file using file id Scenario Outline: copy a file from project to personal space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt" @@ -408,7 +408,7 @@ Feature: copying file using file id Scenario Outline: copy a file between two project spaces - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "first-project-space" with the default quota using the Graph API And user "Alice" has created a space "second-project-space" with the default quota using the Graph API @@ -443,7 +443,7 @@ Feature: copying file using file id Scenario Outline: try to copy a file from a project to another project space with read permission - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "first-project-space" with the default quota using the Graph API And user "Alice" has created a space "second-project-space" with the default quota using the Graph API @@ -475,7 +475,7 @@ Feature: copying file using file id Scenario Outline: copy a file from project to shares space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt" @@ -512,7 +512,7 @@ Feature: copying file using file id @env-config Scenario Outline: try to copy a file from project to shares space with read permission - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has enabled the permissions role "Secure Viewer" And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "project-space" with the default quota using the Graph API diff --git a/tests/acceptance/features/apiSpacesDavOperation/fileVersionByFileID.feature b/tests/acceptance/features/apiSpacesDavOperation/fileVersionByFileID.feature index 59895ce36a..c8cedc7c0a 100644 --- a/tests/acceptance/features/apiSpacesDavOperation/fileVersionByFileID.feature +++ b/tests/acceptance/features/apiSpacesDavOperation/fileVersionByFileID.feature @@ -4,7 +4,7 @@ Feature: checking file versions using file id So that I can manage the changes made to the files Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesDavOperation/getFileByFileId.feature b/tests/acceptance/features/apiSpacesDavOperation/getFileByFileId.feature index a698de27d6..cfdd63f772 100644 --- a/tests/acceptance/features/apiSpacesDavOperation/getFileByFileId.feature +++ b/tests/acceptance/features/apiSpacesDavOperation/getFileByFileId.feature @@ -5,7 +5,7 @@ Feature: accessing files using file id Background: Given using spaces DAV path - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: get content of a file @@ -45,7 +45,7 @@ Feature: accessing files using file id Scenario Outline: sharee gets content of a shared file - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile.txt" And we save it into "FILEID" And user "Alice" has sent the following resource share invitation: @@ -64,7 +64,7 @@ Feature: accessing files using file id Scenario Outline: sharee gets content of a file inside a shared folder - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "uploadFolder" And user "Alice" has uploaded file with content "some data" to "uploadFolder/textfile.txt" And we save it into "FILEID" @@ -84,7 +84,7 @@ Feature: accessing files using file id Scenario Outline: sharee gets content of a file inside a shared space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "new-space" with content "some data" to "textfile.txt" @@ -103,7 +103,7 @@ Feature: accessing files using file id Scenario Outline: user tries to get content of file owned by others - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile.txt" And we save it into "FILEID" When user "Brian" sends HTTP method "GET" to URL "" @@ -114,7 +114,7 @@ Feature: accessing files using file id Scenario Outline: sharee gets content of a shared file when sync is disable - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Brian" has disabled the auto-sync share And user "Alice" has uploaded file with content "some data" to "/textfile.txt" And we save it into "FILEID" @@ -133,7 +133,7 @@ Feature: accessing files using file id Scenario Outline: sharee gets content of a file inside a shared folder when sync is disable - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Brian" has disabled the auto-sync share And user "Alice" has created folder "uploadFolder" And user "Alice" has uploaded file with content "some data" to "uploadFolder/textfile.txt" @@ -153,7 +153,7 @@ Feature: accessing files using file id Scenario Outline: user who is member of group gets content of a shared file when sync is disable - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Brian" has disabled the auto-sync share And user "Alice" has uploaded file with content "some data" to "/textfile.txt" And we save it into "FILEID" @@ -175,7 +175,7 @@ Feature: accessing files using file id Scenario Outline: user who is member of group gets content of a shared folder when sync is disable - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Brian" has disabled the auto-sync share And user "Alice" has created folder "uploadFolder" And user "Alice" has uploaded file with content "some data" to "uploadFolder/textfile.txt" @@ -201,7 +201,7 @@ Feature: accessing files using file id Given using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has disabled the auto-sync share And user "Alice" has uploaded a file inside space "new-space" with content "some content" to "textfile.txt" And we save it into "FILEID" @@ -223,7 +223,7 @@ Feature: accessing files using file id Given using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has disabled the auto-sync share And user "Alice" has created a folder "uploadFolder" in space "new-space" And user "Alice" has uploaded a file inside space "new-space" with content "some content" to "uploadFolder/textfile.txt" @@ -246,7 +246,7 @@ Feature: accessing files using file id Given using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has disabled the auto-sync share And user "Alice" has uploaded a file inside space "new-space" with content "some content" to "textfile.txt" And we save it into "FILEID" @@ -270,7 +270,7 @@ Feature: accessing files using file id Given using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has disabled the auto-sync share And user "Alice" has created a folder "uploadFolder" in space "new-space" And user "Alice" has uploaded a file inside space "new-space" with content "some content" to "uploadFolder/textfile.txt" diff --git a/tests/acceptance/features/apiSpacesDavOperation/moveByFileId.feature b/tests/acceptance/features/apiSpacesDavOperation/moveByFileId.feature index a6a7cfad9e..30f1bc2bda 100644 --- a/tests/acceptance/features/apiSpacesDavOperation/moveByFileId.feature +++ b/tests/acceptance/features/apiSpacesDavOperation/moveByFileId.feature @@ -5,7 +5,7 @@ Feature: moving/renaming file using file id Background: Given using spaces DAV path - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario: move a file into a folder inside personal space @@ -68,7 +68,7 @@ Feature: moving/renaming file using file id Scenario Outline: move a file from personal to share space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folder" And user "Alice" has sent the following resource share invitation: | resource | folder | @@ -93,7 +93,7 @@ Feature: moving/renaming file using file id @issue-7618 Scenario Outline: move a file from personal to project space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Brian" has uploaded a file inside space "Personal" with content "some data" to "textfile.txt" @@ -132,7 +132,7 @@ Feature: moving/renaming file using file id Scenario Outline: move a file into a folder inside project space (manager/editor) Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has created a folder "/folder" in space "project-space" And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt" @@ -156,7 +156,7 @@ Feature: moving/renaming file using file id @issue-1976 Scenario Outline: try to move a file within a project space into a folder with same name Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt" And we save it into "FILEID" @@ -178,7 +178,7 @@ Feature: moving/renaming file using file id Scenario: try to move a file into a folder inside project space (viewer) Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has created a folder "/folder" in space "project-space" And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt" @@ -239,7 +239,7 @@ Feature: moving/renaming file using file id @issue-8116 Scenario Outline: move a file between two project spaces - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "first-project-space" with the default quota using the Graph API And user "Alice" has created a space "second-project-space" with the default quota using the Graph API @@ -293,7 +293,7 @@ Feature: moving/renaming file using file id Scenario Outline: move a file from project to shares space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt" @@ -328,7 +328,7 @@ Feature: moving/renaming file using file id @issue-7618 Scenario Outline: move a file from project to personal space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt" @@ -366,7 +366,7 @@ Feature: moving/renaming file using file id @issue-7617 Scenario: move a file into a folder within a shared folder (edit permissions) - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "folder" And user "Alice" has created folder "folder/sub-folder" And user "Alice" has uploaded file with content "some data" to "folder/test.txt" @@ -391,7 +391,7 @@ Feature: moving/renaming file using file id @issue-1976 Scenario: sharee tries to move a file into same shared folder with same name - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "folder" And user "Alice" has uploaded file with content "some data" to "folder/test.txt" And we save it into "FILEID" @@ -410,7 +410,7 @@ Feature: moving/renaming file using file id Scenario: try to move a file into a folder within a shared folder (read permissions) - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "folder" And user "Alice" has created folder "folder/sub-folder" And user "Alice" has uploaded file with content "some data" to "folder/test.txt" @@ -435,7 +435,7 @@ Feature: moving/renaming file using file id Scenario Outline: move a file from one shared folder to another shared folder - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "testshare1" And user "Alice" has created folder "testshare2" And user "Alice" has uploaded file with content "some data" to "testshare1/textfile.txt" @@ -469,7 +469,7 @@ Feature: moving/renaming file using file id @issue-8124 Scenario Outline: move a file from share to personal space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folder" And user "Alice" has uploaded file with content "some data" to "/folder/test.txt" And we save it into "FILEID" @@ -493,7 +493,7 @@ Feature: moving/renaming file using file id @issue-8125 Scenario Outline: move a file from shares to project space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "project-space" with the default quota using the Graph API And user "Alice" has sent the following space share invitation: @@ -589,7 +589,7 @@ Feature: moving/renaming file using file id @issue-7617 Scenario: move a file to a different name into a sub-folder inside share space (editor permissions) - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folder" And user "Alice" has created folder "/folder/sub-folder" And user "Alice" has uploaded file with content "some data" to "/folder/test.txt" @@ -610,7 +610,7 @@ Feature: moving/renaming file using file id Scenario: move a file to a different name into a sub-folder inside share space (read permissions) - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folder" And user "Alice" has created folder "/folder/sub-folder" And user "Alice" has uploaded file with content "some data" to "/folder/test.txt" diff --git a/tests/acceptance/features/apiSpacesDavOperation/propfindByFileId.feature b/tests/acceptance/features/apiSpacesDavOperation/propfindByFileId.feature index 246c1cc03f..5abc55bb59 100644 --- a/tests/acceptance/features/apiSpacesDavOperation/propfindByFileId.feature +++ b/tests/acceptance/features/apiSpacesDavOperation/propfindByFileId.feature @@ -5,7 +5,7 @@ Feature: propfind a file using file id Background: Given using spaces DAV path - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: send a PROPFIND request to a file inside root of personal space @@ -38,7 +38,7 @@ Feature: propfind a file using file id Scenario Outline: send a PROPFIND request to a file in personal space owned by another user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "textfile.txt" And we save it into "FILEID" When user "Brian" sends HTTP method "PROPFIND" to URL "" @@ -82,7 +82,7 @@ Feature: propfind a file using file id Scenario Outline: send a PROPFIND request to a file inside project space owned by another user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "new-space" with content "some content" to "textfile.txt" @@ -95,7 +95,7 @@ Feature: propfind a file using file id Scenario Outline: send a PROPFIND request to a shared file - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile.txt" And we save it into "FILEID" And user "Alice" has sent the following resource share invitation: @@ -117,7 +117,7 @@ Feature: propfind a file using file id Scenario Outline: sharee sends a PROPFIND request to a file inside of a shared folder - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/folder" And user "Alice" has sent the following resource share invitation: | resource | folder | diff --git a/tests/acceptance/features/apiSpacesDavOperation/updateFileByFileId.feature b/tests/acceptance/features/apiSpacesDavOperation/updateFileByFileId.feature index e2b4081c41..e91494feae 100644 --- a/tests/acceptance/features/apiSpacesDavOperation/updateFileByFileId.feature +++ b/tests/acceptance/features/apiSpacesDavOperation/updateFileByFileId.feature @@ -5,7 +5,7 @@ Feature: update files using file id Background: Given using spaces DAV path - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: update content of a file @@ -45,7 +45,7 @@ Feature: update files using file id Scenario Outline: sharee updates content of a shared file - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile.txt" And we save it into "FILEID" And user "Alice" has sent the following resource share invitation: @@ -65,7 +65,7 @@ Feature: update files using file id Scenario Outline: sharee updates content of a file inside a shared folder - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "uploadFolder" And user "Alice" has uploaded file with content "some data" to "uploadFolder/textfile.txt" And we save it into "FILEID" @@ -86,7 +86,7 @@ Feature: update files using file id Scenario Outline: sharee with different role tries to update content of a file inside a shared space - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "new-space" with content "some data" to "/textfile.txt" @@ -106,7 +106,7 @@ Feature: update files using file id Scenario Outline: user tries to update content of a file owned by others - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile.txt" And we save it into "FILEID" When user "Brian" sends HTTP method "PUT" to URL "" with content "updated content" diff --git a/tests/acceptance/features/apiSpacesShares/changingFilesShare.feature b/tests/acceptance/features/apiSpacesShares/changingFilesShare.feature index 4680d68d0e..4ecd24c995 100644 --- a/tests/acceptance/features/apiSpacesShares/changingFilesShare.feature +++ b/tests/acceptance/features/apiSpacesShares/changingFilesShare.feature @@ -5,14 +5,14 @@ Feature: change shared resource Background: Given using spaces DAV path - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | @issue-4421 Scenario: move files between shares by different users - Given user "Carol" has been created with default attributes and without skeleton files + Given user "Carol" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has created folder "/PARENT" And user "Brian" has created folder "/PARENT" diff --git a/tests/acceptance/features/apiSpacesShares/checksum.feature b/tests/acceptance/features/apiSpacesShares/checksum.feature index 6a7b4826c5..c5bad870f8 100644 --- a/tests/acceptance/features/apiSpacesShares/checksum.feature +++ b/tests/acceptance/features/apiSpacesShares/checksum.feature @@ -4,9 +4,9 @@ Feature: checksums So that I can make sure that the files are uploaded with correct checksums Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes @issue-1291 Scenario: sharing a file with checksum should return the checksum in the propfind using new DAV path diff --git a/tests/acceptance/features/apiSpacesShares/copySpaces.feature b/tests/acceptance/features/apiSpacesShares/copySpaces.feature index 36baf2b3c4..314109a11b 100644 --- a/tests/acceptance/features/apiSpacesShares/copySpaces.feature +++ b/tests/acceptance/features/apiSpacesShares/copySpaces.feature @@ -4,7 +4,7 @@ Feature: copy file So that I can manage my files Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature b/tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature index d6ea9ed455..e7de5ca105 100644 --- a/tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature +++ b/tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature @@ -4,7 +4,7 @@ Feature: create file or folder named similar to Shares folder So that I can organise the files in my file system Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/etagPropagation.feature b/tests/acceptance/features/apiSpacesShares/etagPropagation.feature index 3978adad6c..78a2dde0d2 100644 --- a/tests/acceptance/features/apiSpacesShares/etagPropagation.feature +++ b/tests/acceptance/features/apiSpacesShares/etagPropagation.feature @@ -4,7 +4,7 @@ Feature: check etag propagation after different file alterations So that I can make sure that they are correct after different file alterations Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/favorite.feature b/tests/acceptance/features/apiSpacesShares/favorite.feature index 0f2b6a1934..90784350c0 100644 --- a/tests/acceptance/features/apiSpacesShares/favorite.feature +++ b/tests/acceptance/features/apiSpacesShares/favorite.feature @@ -4,7 +4,7 @@ Feature: favorite So that I can access them quickly Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/moveSpaces.feature b/tests/acceptance/features/apiSpacesShares/moveSpaces.feature index 4336e9db5c..38838ac4cf 100644 --- a/tests/acceptance/features/apiSpacesShares/moveSpaces.feature +++ b/tests/acceptance/features/apiSpacesShares/moveSpaces.feature @@ -4,7 +4,7 @@ Feature: move (rename) file So that I can manage my file system Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/publicLinkDownload.feature b/tests/acceptance/features/apiSpacesShares/publicLinkDownload.feature index 0289e110d9..a4e1d9d23a 100644 --- a/tests/acceptance/features/apiSpacesShares/publicLinkDownload.feature +++ b/tests/acceptance/features/apiSpacesShares/publicLinkDownload.feature @@ -4,7 +4,7 @@ Feature: Public can download folders from project space public link So that I can gain access to it's contents Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/shareOperations.feature b/tests/acceptance/features/apiSpacesShares/shareOperations.feature index 59c87960cb..095c399707 100644 --- a/tests/acceptance/features/apiSpacesShares/shareOperations.feature +++ b/tests/acceptance/features/apiSpacesShares/shareOperations.feature @@ -5,7 +5,7 @@ Feature: sharing Background: Given using OCS API version "1" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/shareSpaces.feature b/tests/acceptance/features/apiSpacesShares/shareSpaces.feature index 60eaa4b056..8f7cca3db7 100644 --- a/tests/acceptance/features/apiSpacesShares/shareSpaces.feature +++ b/tests/acceptance/features/apiSpacesShares/shareSpaces.feature @@ -7,7 +7,7 @@ Feature: Share spaces See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/shareSpacesViaLink.feature b/tests/acceptance/features/apiSpacesShares/shareSpacesViaLink.feature index 0277968dd6..3bf483b7f8 100644 --- a/tests/acceptance/features/apiSpacesShares/shareSpacesViaLink.feature +++ b/tests/acceptance/features/apiSpacesShares/shareSpacesViaLink.feature @@ -7,7 +7,7 @@ Feature: Share spaces via link See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpace.feature b/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpace.feature index 93e5605901..7ba6111ed5 100644 --- a/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpace.feature +++ b/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpace.feature @@ -7,7 +7,7 @@ Feature: Share a file or folder that is inside a space See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpaceViaPublicLink.feature b/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpaceViaPublicLink.feature index 66bc6ffaa4..c7b1ba1a49 100644 --- a/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpaceViaPublicLink.feature +++ b/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpaceViaPublicLink.feature @@ -21,7 +21,7 @@ Feature: Share a file or folder that is inside a space via public link See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature b/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature index b353b9504f..e17dcc24e8 100644 --- a/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature +++ b/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature @@ -5,7 +5,7 @@ Feature: upload resources on share using TUS protocol Background: Given using spaces DAV path - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/cliCommands/backupConsistency.feature b/tests/acceptance/features/cliCommands/backupConsistency.feature index 810cb4f829..e061b4fb8b 100644 --- a/tests/acceptance/features/cliCommands/backupConsistency.feature +++ b/tests/acceptance/features/cliCommands/backupConsistency.feature @@ -5,11 +5,11 @@ Feature: backup consistency So that I can backup my data Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: check backup consistency via CLI command - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | | Carol | diff --git a/tests/acceptance/features/cliCommands/removeFileVersions.feature b/tests/acceptance/features/cliCommands/removeFileVersions.feature index fbaba57a7a..c203b2e88c 100644 --- a/tests/acceptance/features/cliCommands/removeFileVersions.feature +++ b/tests/acceptance/features/cliCommands/removeFileVersions.feature @@ -2,7 +2,7 @@ Feature: remove file versions via CLI command Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: remove all file versions diff --git a/tests/acceptance/features/cliCommands/searchReIndex.feature b/tests/acceptance/features/cliCommands/searchReIndex.feature index f20ea50b88..8615135cca 100644 --- a/tests/acceptance/features/cliCommands/searchReIndex.feature +++ b/tests/acceptance/features/cliCommands/searchReIndex.feature @@ -5,7 +5,7 @@ Feature: reindex space via CLI command So that I can improve search performance by ensuring that the index is up-to-date Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And using spaces DAV path And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API diff --git a/tests/acceptance/features/cliCommands/uploadSessions.feature b/tests/acceptance/features/cliCommands/uploadSessions.feature index 9262c954ce..169cd095ac 100644 --- a/tests/acceptance/features/cliCommands/uploadSessions.feature +++ b/tests/acceptance/features/cliCommands/uploadSessions.feature @@ -5,7 +5,7 @@ Feature: List upload sessions via CLI command So that I can manage the upload sessions Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: list all upload sessions diff --git a/tests/acceptance/features/coreApiAuth/ocsGETAuth.feature b/tests/acceptance/features/coreApiAuth/ocsGETAuth.feature index 55d3525270..4ba9c13b8e 100644 --- a/tests/acceptance/features/coreApiAuth/ocsGETAuth.feature +++ b/tests/acceptance/features/coreApiAuth/ocsGETAuth.feature @@ -4,7 +4,7 @@ Feature: auth So that I can make sure the endpoints need proper authentication Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-1337 @smokeTest Scenario: using OCS anonymously diff --git a/tests/acceptance/features/coreApiAuth/ocsPOSTAuth.feature b/tests/acceptance/features/coreApiAuth/ocsPOSTAuth.feature index 6ae0dae04d..351340cfba 100644 --- a/tests/acceptance/features/coreApiAuth/ocsPOSTAuth.feature +++ b/tests/acceptance/features/coreApiAuth/ocsPOSTAuth.feature @@ -4,7 +4,7 @@ Feature: auth So that I can make sure the endpoints need proper authentication Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-1337 @smokeTest Scenario: send POST requests to OCS endpoints as normal user with wrong password diff --git a/tests/acceptance/features/coreApiAuth/webDavAuth.feature b/tests/acceptance/features/coreApiAuth/webDavAuth.feature index 78fb4b9e91..f42bc278d9 100644 --- a/tests/acceptance/features/coreApiAuth/webDavAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavAuth.feature @@ -4,7 +4,7 @@ Feature: auth So that I can make sure it's secure Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @smokeTest @issue-10334 Scenario Outline: using WebDAV anonymously diff --git a/tests/acceptance/features/coreApiAuth/webDavCOPYAuth.feature b/tests/acceptance/features/coreApiAuth/webDavCOPYAuth.feature index 408f539587..1fedc78bb2 100644 --- a/tests/acceptance/features/coreApiAuth/webDavCOPYAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavCOPYAuth.feature @@ -4,7 +4,7 @@ Feature: COPY file/folder So that I can duplicate it Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiAuth/webDavDELETEAuth.feature b/tests/acceptance/features/coreApiAuth/webDavDELETEAuth.feature index 7434072498..24478a30af 100644 --- a/tests/acceptance/features/coreApiAuth/webDavDELETEAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavDELETEAuth.feature @@ -4,7 +4,7 @@ Feature: delete file/folder So that I can remove redundant resources Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiAuth/webDavLOCKAuth.feature b/tests/acceptance/features/coreApiAuth/webDavLOCKAuth.feature index eef322f2ed..98f8320ab1 100644 --- a/tests/acceptance/features/coreApiAuth/webDavLOCKAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavLOCKAuth.feature @@ -4,7 +4,7 @@ Feature: LOCK file/folder So that I can ensure that the resources won't be changed unexpectedly Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiAuth/webDavMKCOLAuth.feature b/tests/acceptance/features/coreApiAuth/webDavMKCOLAuth.feature index 52b141e5d6..b80a1622af 100644 --- a/tests/acceptance/features/coreApiAuth/webDavMKCOLAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavMKCOLAuth.feature @@ -4,7 +4,7 @@ Feature: create folder using MKCOL So that I can organise resources in folders Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has created folder "/PARENT" And user "Alice" has created folder "/FOLDER" @@ -40,7 +40,7 @@ Feature: create folder using MKCOL @issue-5049 @issue-1347 @issue-1292 Scenario: send MKCOL requests to another user's webDav endpoints as normal user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice" | endpoint | | /dav/files/%username%/textfile0.txt | @@ -51,7 +51,7 @@ Feature: create folder using MKCOL @issue-5049 @issue-1347 @issue-1292 Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user" | endpoint | | /dav/files/non-existent-user/textfile0.txt | @@ -62,7 +62,7 @@ Feature: create folder using MKCOL @issue-1347 @issue-1292 Scenario: send MKCOL requests to another user's webDav endpoints as normal user using the spaces WebDAV API - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice" | endpoint | | /dav/spaces/%spaceid%/textfile0.txt | @@ -73,7 +73,7 @@ Feature: create folder using MKCOL @issue-5049 @issue-1347 @issue-1292 Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal user using the spaces WebDAV API - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user" | endpoint | | /dav/spaces/%spaceid%/textfile0.txt | @@ -98,7 +98,7 @@ Feature: create folder using MKCOL Scenario: send MKCOL requests to webDav endpoints using valid password and username of different user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Brian" requests these endpoints with "MKCOL" including body "doesnotmatter" using the password of user "Alice" | endpoint | | /webdav/textfile0.txt | diff --git a/tests/acceptance/features/coreApiAuth/webDavMOVEAuth.feature b/tests/acceptance/features/coreApiAuth/webDavMOVEAuth.feature index 3ea9120aaf..db2a6e14aa 100644 --- a/tests/acceptance/features/coreApiAuth/webDavMOVEAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavMOVEAuth.feature @@ -4,7 +4,7 @@ Feature: MOVE file/folder So that I can organise resources according to my preference Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiAuth/webDavPOSTAuth.feature b/tests/acceptance/features/coreApiAuth/webDavPOSTAuth.feature index bfd35f4f21..2113a4f2ec 100644 --- a/tests/acceptance/features/coreApiAuth/webDavPOSTAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavPOSTAuth.feature @@ -4,7 +4,7 @@ Feature: POST file/folder So that I can ensure the endpoints are well authenticated Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiAuth/webDavPROPFINDAuth.feature b/tests/acceptance/features/coreApiAuth/webDavPROPFINDAuth.feature index 5ffdede30a..1136c8af44 100644 --- a/tests/acceptance/features/coreApiAuth/webDavPROPFINDAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavPROPFINDAuth.feature @@ -4,7 +4,7 @@ Feature: PROPFIND file/folder So that I can ensure the endpoints are well authenticated Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiAuth/webDavPROPPATCHAuth.feature b/tests/acceptance/features/coreApiAuth/webDavPROPPATCHAuth.feature index 16b93b0d3b..cea1206e33 100644 --- a/tests/acceptance/features/coreApiAuth/webDavPROPPATCHAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavPROPPATCHAuth.feature @@ -4,7 +4,7 @@ Feature: PROPPATCH file/folder So that I can ensure the endpoints are well authenticated Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiAuth/webDavPUTAuth.feature b/tests/acceptance/features/coreApiAuth/webDavPUTAuth.feature index 50b60368c1..c76beaadaf 100644 --- a/tests/acceptance/features/coreApiAuth/webDavPUTAuth.feature +++ b/tests/acceptance/features/coreApiAuth/webDavPUTAuth.feature @@ -4,7 +4,7 @@ Feature: PUT file/folder So that I can ensure the endpoints are well authenticated Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiAuth/webDavSpecialURLs.feature b/tests/acceptance/features/coreApiAuth/webDavSpecialURLs.feature index 1e17531905..6b541d1002 100644 --- a/tests/acceptance/features/coreApiAuth/webDavSpecialURLs.feature +++ b/tests/acceptance/features/coreApiAuth/webDavSpecialURLs.feature @@ -4,7 +4,7 @@ Feature: make webdav request with special urls So that I can make sure that they work Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has uploaded file with content "some data" to "/textfile1.txt" And user "Alice" has created folder "/PARENT" diff --git a/tests/acceptance/features/coreApiCapabilities/capabilitiesWithNormalUser.feature b/tests/acceptance/features/coreApiCapabilities/capabilitiesWithNormalUser.feature index b139db6c30..e387b20709 100644 --- a/tests/acceptance/features/coreApiCapabilities/capabilitiesWithNormalUser.feature +++ b/tests/acceptance/features/coreApiCapabilities/capabilitiesWithNormalUser.feature @@ -5,7 +5,7 @@ Feature: default capabilities for normal user Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes # adjust this scenario after fixing tagged issues as its just created to show difference # in the response items in different environment (core & ocis-reva) diff --git a/tests/acceptance/features/coreApiFavorites/favorites.feature b/tests/acceptance/features/coreApiFavorites/favorites.feature index 342a74290e..bf1a1b8fc7 100644 --- a/tests/acceptance/features/coreApiFavorites/favorites.feature +++ b/tests/acceptance/features/coreApiFavorites/favorites.feature @@ -5,7 +5,7 @@ Feature: favorite Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has uploaded file with content "some data" to "/textfile1.txt" And user "Alice" has uploaded file with content "some data" to "/textfile2.txt" diff --git a/tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature b/tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature index 88e0bc70a2..d2c8517c80 100644 --- a/tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature +++ b/tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature @@ -5,14 +5,14 @@ Feature: favorite So that I can access them quickly Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/PARENT" And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt" Scenario Outline: favorite a file inside of a received share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following resource share invitation: | resource | PARENT | | space | Personal | @@ -32,7 +32,7 @@ Feature: favorite Scenario Outline: favorite a folder inside of a received share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/PARENT/sub-folder" And user "Alice" has sent the following resource share invitation: | resource | PARENT | @@ -53,7 +53,7 @@ Feature: favorite Scenario Outline: favorite a received share itself Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following resource share invitation: | resource | PARENT | | space | Personal | @@ -73,7 +73,7 @@ Feature: favorite @issue-1228 Scenario Outline: moving a favorite file out of a share keeps favorite state Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following resource share invitation: | resource | PARENT | | space | Personal | @@ -95,7 +95,7 @@ Feature: favorite Scenario Outline: sharee file favorite state should not change the favorite state of sharer Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has sent the following resource share invitation: | resource | PARENT/parent.txt | | space | Personal | diff --git a/tests/acceptance/features/coreApiMain/checksums.feature b/tests/acceptance/features/coreApiMain/checksums.feature index 0fff86fe0c..29b920b955 100644 --- a/tests/acceptance/features/coreApiMain/checksums.feature +++ b/tests/acceptance/features/coreApiMain/checksums.feature @@ -4,7 +4,7 @@ Feature: checksums So that I can make sure that the files are uploaded with correct checksums Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: uploading a file with checksum should work @@ -142,7 +142,7 @@ Feature: checksums @issue-1291 @skipOnReva Scenario Outline: sharing a file with checksum should return the checksum in the propfind using new DAV path Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" And user "Alice" has sent the following resource share invitation: | resource | myChecksumFile.txt | @@ -163,7 +163,7 @@ Feature: checksums @issue-1291 @skipOnReva Scenario Outline: modifying a shared file should return correct checksum in the propfind using new DAV path Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" And user "Alice" has sent the following resource share invitation: | resource | myChecksumFile.txt | diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareResourceCaseSensitiveName.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareResourceCaseSensitiveName.feature index 8f1fe6f7f1..74b0a28381 100644 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareResourceCaseSensitiveName.feature +++ b/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareResourceCaseSensitiveName.feature @@ -5,7 +5,7 @@ Feature: Sharing resources with different case names with the sharee and checkin So that I can make sure that the shares aren't case sensitive Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature index fc96044721..c8bc01de1c 100644 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature +++ b/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature @@ -6,7 +6,7 @@ Feature: resources shared with the same name are received with unique names Background: Given using OCS API version "1" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature index db6b649895..4247ba6514 100644 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature +++ b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature @@ -5,12 +5,12 @@ Feature: shares are received in the default folder for received shares So that I can make sure it does not work Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: do not allow sharing of the entire share folder Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "FOLDER" When user "Alice" shares folder "/FOLDER" with user "Brian" using the sharing API And user "Brian" declines share "/Shares/FOLDER" offered by user "Alice" using the sharing API diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareGroupAndUserWithSameName.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareGroupAndUserWithSameName.feature index 55e6464aeb..68817a9950 100644 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareGroupAndUserWithSameName.feature +++ b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareGroupAndUserWithSameName.feature @@ -5,11 +5,11 @@ Feature: sharing works when a username and group name are the same So that I can make sure that the sharing works Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: creating a new share with user and a group having same name - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | | Carol | @@ -35,7 +35,7 @@ Feature: sharing works when a username and group name are the same Scenario: creating a new share with group and a user having same name - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | | Carol | @@ -61,7 +61,7 @@ Feature: sharing works when a username and group name are the same Scenario: creating a new share with user and a group having same name but different case - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | | Carol | @@ -87,7 +87,7 @@ Feature: sharing works when a username and group name are the same Scenario: creating a new share with group and a user having same name but different case - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | | Carol | diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature index a4c0589b61..4788d95bcc 100644 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature +++ b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature @@ -5,7 +5,7 @@ Feature: share resources where the sharee receives the share in multiple ways So that I can make sure that the sharing works Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -113,7 +113,7 @@ Feature: share resources where the sharee receives the share in multiple ways @issue-2131 Scenario Outline: multiple users share a file with the same name but different permissions to a user Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Brian" has uploaded file with content "First data" to "/randomfile.txt" And user "Carol" has uploaded file with content "Second data" to "/randomfile.txt" When user "Brian" shares file "randomfile.txt" with user "Alice" with permissions "read" using the sharing API @@ -144,7 +144,7 @@ Feature: share resources where the sharee receives the share in multiple ways @issue-2131 Scenario Outline: multiple users share a folder with the same name to a user Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Brian" has created folder "/zzzfolder" And user "Brian" has created folder "zzzfolder/Brian" And user "Carol" has created folder "/zzzfolder" @@ -177,7 +177,7 @@ Feature: share resources where the sharee receives the share in multiple ways @skipOnReva Scenario Outline: share with a group and then add a user to that group that already has a file with the shared name Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Carol" has disabled auto-accepting And these groups have been created: | groupname | @@ -206,7 +206,7 @@ Feature: share resources where the sharee receives the share in multiple ways @issue-2440 Scenario: sharing parent folder to user with all permissions and its child folder to group with read permission then check create operation Given group "grp1" has been created - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Carol" has created the following folders | path | | /parent | @@ -236,7 +236,7 @@ Feature: share resources where the sharee receives the share in multiple ways @issue-2440 Scenario: sharing parent folder to user with all permissions and its child folder to group with read permission then check rename operation Given group "grp1" has been created - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Carol" has created the following folders | path | | /parent | @@ -267,7 +267,7 @@ Feature: share resources where the sharee receives the share in multiple ways @issue-2440 Scenario: sharing parent folder to user with all permissions and its child folder to group with read permission then check delete operation Given group "grp1" has been created - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Carol" has created the following folders | path | | /parent | @@ -299,7 +299,7 @@ Feature: share resources where the sharee receives the share in multiple ways Scenario: sharing parent folder to group with read permission and its child folder to user with all permissions then check create operation Given group "grp1" has been created - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Carol" has created the following folders | path | | /parent | @@ -331,7 +331,7 @@ Feature: share resources where the sharee receives the share in multiple ways @issue-2440 Scenario: sharing parent folder to group with read permission and its child folder to user with all permissions then check rename operation Given group "grp1" has been created - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Carol" has created the following folders | path | | /parent | @@ -362,7 +362,7 @@ Feature: share resources where the sharee receives the share in multiple ways @issue-2440 Scenario: sharing parent folder to group with read permission and its child folder to user with all permissions then check delete operation Given group "grp1" has been created - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Carol" has created the following folders | path | | /parent | @@ -397,7 +397,7 @@ Feature: share resources where the sharee receives the share in multiple ways | grp1 | | grp2 | | grp3 | - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And user "Carol" has created the following folders | path | | /parent | diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature index bc7ff7e202..1e1d8d4f3b 100644 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature +++ b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature @@ -4,14 +4,14 @@ Feature: cannot share resources with invalid permissions So that I can make sure it doesn't work Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has created folder "/PARENT" Scenario Outline: cannot create a share of a file or folder with invalid permissions Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" creates a share using the sharing API with settings | path | | | shareWith | Brian | @@ -36,7 +36,7 @@ Feature: cannot share resources with invalid permissions Scenario Outline: cannot create a share of a file with a user with only create permission Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" creates a share using the sharing API with settings | path | textfile0.txt | | shareWith | Brian | @@ -55,7 +55,7 @@ Feature: cannot share resources with invalid permissions Scenario Outline: cannot create a share of a file with a user with only (create,delete) permission Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes When user "Alice" creates a share using the sharing API with settings | path | textfile0.txt | | shareWith | Brian | @@ -76,7 +76,7 @@ Feature: cannot share resources with invalid permissions Scenario Outline: cannot create a share of a file with a group with only create permission Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" When user "Alice" creates a share using the sharing API with settings @@ -97,7 +97,7 @@ Feature: cannot share resources with invalid permissions Scenario Outline: cannot create a share of a file with a group with only (create,delete) permission Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" When user "Alice" creates a share using the sharing API with settings diff --git a/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature b/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature index 64e7f083c3..d322e86d17 100644 --- a/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature +++ b/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature @@ -5,12 +5,12 @@ Feature: sharing So that they can have access on them Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @smokeTest Scenario Outline: creating a share of a file with a user, the default permissions are read(1)+update(2) Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API Then the OCS status code should be "" @@ -37,7 +37,7 @@ Feature: sharing @smokeTest @issue-2133 Scenario Outline: creating a share of a file containing commas in the filename, with a user, the default permissions are read(1)+update(2)+can-share(16) Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "file with comma in filename" to "/sample,1.txt" When user "Alice" shares file "sample,1.txt" with user "Brian" using the sharing API Then the OCS status code should be "" @@ -63,7 +63,7 @@ Feature: sharing @issue-2133 @issue-1270 @issue-1271 Scenario Outline: creating a share of a file with a user and asking for various permission combinations Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" When user "Alice" shares file "textfile0.txt" with user "Brian" with permissions using the sharing API Then the OCS status code should be "" @@ -98,7 +98,7 @@ Feature: sharing Scenario Outline: creating a share of a file with no permissions should fail Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "Random data" to "randomfile.txt" When user "Alice" shares file "randomfile.txt" with user "Brian" with permissions "0" using the sharing API Then the OCS status code should be "400" @@ -114,7 +114,7 @@ Feature: sharing Scenario Outline: creating a share of a folder with no permissions should fail Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/afolder" When user "Alice" shares folder "afolder" with user "Brian" with permissions "0" using the sharing API Then the OCS status code should be "400" @@ -130,7 +130,7 @@ Feature: sharing @issue-2133 Scenario Outline: creating a share of a folder with a user, the default permissions are all permissions(15) Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/FOLDER" When user "Alice" shares folder "/FOLDER" with user "Brian" using the sharing API Then the OCS status code should be "" @@ -204,7 +204,7 @@ Feature: sharing @smokeTest Scenario: share of folder to a group - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | | Carol | @@ -234,7 +234,7 @@ Feature: sharing @smokeTest Scenario: user included in multiple groups, shares a folder with a group - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | And group "grp1" has been created @@ -251,7 +251,7 @@ Feature: sharing Scenario: sharing again an own file while belonging to a group - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -269,7 +269,7 @@ Feature: sharing @issue-2201 Scenario Outline: sharing subfolder of already shared folder, GET result is correct Given using OCS API version "" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -321,7 +321,7 @@ Feature: sharing Scenario Outline: user shares a file with file name longer than 64 chars to another user Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" When user "Alice" shares file "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" with user "Brian" using the sharing API @@ -335,7 +335,7 @@ Feature: sharing Scenario Outline: user shares a file with file name longer than 64 chars to a group Given using OCS API version "" And group "grp1" has been created - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has been added to group "grp1" And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" @@ -349,7 +349,7 @@ Feature: sharing Scenario Outline: user shares a folder with folder name longer than 64 chars to another user Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "ownCloud test" to "/textfile0.txt" And user "Alice" has created folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog" And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" @@ -364,7 +364,7 @@ Feature: sharing Scenario Outline: user shares a folder with folder name longer than 64 chars to a group Given using OCS API version "" And group "grp1" has been created - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has been added to group "grp1" And user "Alice" has uploaded file with content "ownCloud test" to "/textfile0.txt" And user "Alice" has created folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog" @@ -378,7 +378,7 @@ Feature: sharing Scenario: share with user when username contains capital letters - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | brian | And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt" @@ -397,7 +397,7 @@ Feature: sharing Scenario: creating a new share with user of a group when group name contains capital letters - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Brian | And group "GROUP" has been created @@ -413,7 +413,7 @@ Feature: sharing Scenario Outline: share of folder to a group with emoji in the name Given using OCS API version "" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -439,7 +439,7 @@ Feature: sharing @skipOnReva Scenario Outline: share with a group and then add a user to that group Given using OCS API version "" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -467,7 +467,7 @@ Feature: sharing @issue-2441 Scenario Outline: shares shared to deleted group should not be available Given using OCS API version "" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -507,7 +507,7 @@ Feature: sharing @issue-764 @issue-7555 Scenario Outline: share a file by multiple channels and download from sub-folder and direct file share Given using DAV path - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -551,7 +551,7 @@ Feature: sharing @smokeTest Scenario Outline: creating a share of a renamed file Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" And user "Alice" has moved file "/textfile0.txt" to "/renamed.txt" When user "Alice" shares file "renamed.txt" with user "Brian" using the sharing API @@ -578,7 +578,7 @@ Feature: sharing @issue-903 Scenario Outline: shares to a deleted user should not be listed as shares for the sharer Given using OCS API version "" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -609,7 +609,7 @@ Feature: sharing @issue-719 Scenario Outline: creating a share of a renamed file when another share exists Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/Folder1" And user "Alice" has created folder "/Folder2" And user "Alice" has sent the following resource share invitation: diff --git a/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature b/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature index 3e941db2c6..05b186dee0 100644 --- a/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature +++ b/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature @@ -5,7 +5,7 @@ Feature: sharing So that I don't have redundant shares Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -131,7 +131,7 @@ Feature: sharing @smokeTest Scenario: unshare from self And group "grp1" has been created - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Carol | And user "Brian" has been added to group "grp1" @@ -223,7 +223,7 @@ Feature: sharing Scenario Outline: group share recipient tries to delete the share Given using OCS API version "" And group "grp1" has been created - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Carol | And user "Brian" has been added to group "grp1" diff --git a/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature b/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature index c7be05996c..216d3f2cf1 100644 --- a/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature +++ b/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature @@ -7,7 +7,7 @@ Feature: accept/decline shares coming from internal users Background: Given using OCS API version "1" And using new DAV path - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | @@ -347,7 +347,7 @@ Feature: accept/decline shares coming from internal users Scenario: user accepts shares received from multiple users with the same name when auto-accept share is disabled Given user "Alice" has disabled auto-accepting - And user "David" has been created with default attributes and without skeleton files + And user "David" has been created with default attributes And user "David" has created folder "PARENT" And user "Brian" has sent the following resource share invitation: | resource | PARENT | @@ -522,7 +522,7 @@ Feature: accept/decline shares coming from internal users Scenario: user shares folder with matching folder name to a user before that user has logged in - Given these users have been created without skeleton files and not initialized: + Given these users have been created without being initialized: | username | | David | And user "David" has disabled auto-accepting diff --git a/tests/acceptance/features/coreApiShareManagementToShares/acceptSharesToSharesFolder.feature b/tests/acceptance/features/coreApiShareManagementToShares/acceptSharesToSharesFolder.feature index 14261a8db7..22f8e99457 100644 --- a/tests/acceptance/features/coreApiShareManagementToShares/acceptSharesToSharesFolder.feature +++ b/tests/acceptance/features/coreApiShareManagementToShares/acceptSharesToSharesFolder.feature @@ -7,7 +7,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder Background: Given using OCS API version "1" And using new DAV path - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature b/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature index d18dd40f39..1ac1ce5ce6 100644 --- a/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature +++ b/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature @@ -3,7 +3,7 @@ Feature: sharing Background: Given using OCS API version "1" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareManagementToShares/moveReceivedShare.feature b/tests/acceptance/features/coreApiShareManagementToShares/moveReceivedShare.feature index b303d27cd3..abbdf5f9cc 100644 --- a/tests/acceptance/features/coreApiShareManagementToShares/moveReceivedShare.feature +++ b/tests/acceptance/features/coreApiShareManagementToShares/moveReceivedShare.feature @@ -3,7 +3,7 @@ Feature: sharing Background: Given using OCS API version "1" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature b/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature index 0ecad3812e..1a7298d4a7 100644 --- a/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature +++ b/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature @@ -6,7 +6,7 @@ Feature: moving a share inside another share Background: Given using OCS API version "1" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature index afa5348684..89f03a38d7 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature @@ -5,7 +5,7 @@ Feature: sharing So that they can have access to the resources Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature index e447c28ed1..c4fa3a9283 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature @@ -5,7 +5,7 @@ Feature: sharing So that I can organise them according to my needs Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature index dce6474d6f..27d1a6f082 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature @@ -5,7 +5,7 @@ Feature: sharing So that I can know I have proper access to them Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | @@ -51,7 +51,7 @@ Feature: sharing @smokeTest Scenario Outline: getting all shares of a file Given using OCS API version "" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Carol | | David | @@ -118,7 +118,7 @@ Feature: sharing @issue-1233 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 + And user "Carol" has been created with default attributes And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" And user "Alice" has sent the following resource share invitation: | resource | textfile0.txt | @@ -139,7 +139,7 @@ Feature: sharing @issue-1289 Scenario: share a folder to a group, and remove user from that group Given using OCS API version "1" - And user "Carol" has been created with default attributes and without skeleton files + And user "Carol" has been created with default attributes And group "group0" has been created And user "Brian" has been added to group "group0" And user "Carol" has been added to group "group0" diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature index 489b8cdcea..895223e12d 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature @@ -5,7 +5,7 @@ Feature: get the pending shares filtered by type (user, group etc) So that I can know about the status of the shares I've received Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFiltered.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFiltered.feature index 1d5afa1e99..42d887c04e 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFiltered.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFiltered.feature @@ -5,7 +5,7 @@ Feature: get the received shares filtered by type (user, group etc) So that I can know about the status of the shares I've received Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature index 86ec586561..0fe4516b12 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature @@ -5,7 +5,7 @@ Feature: get the received shares filtered by type (user, group etc) So that I can know about the status of the shares I've received Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFiltered.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFiltered.feature index 8486032460..ddf6ea699f 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFiltered.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFiltered.feature @@ -5,7 +5,7 @@ Feature: get shares filtered by type (user, group etc) So that I can know about the status of the shares I've received Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature index 3cec3c83cb..989af88123 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature @@ -5,7 +5,7 @@ Feature: get shares filtered by type (user, group etc) So that I can know about the status of the shares I've received Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares2/getWebDAVSharePermissions.feature b/tests/acceptance/features/coreApiShareOperationsToShares2/getWebDAVSharePermissions.feature index bd733457b5..3c80a1dcef 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares2/getWebDAVSharePermissions.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares2/getWebDAVSharePermissions.feature @@ -6,7 +6,7 @@ Feature: sharing Background: Given using OCS API version "1" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature b/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature index 60f9f6234c..18dd59d709 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature @@ -5,7 +5,7 @@ Feature: share access by ID So that the app can more easily manage shares Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature b/tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature index c4b99eeb51..164752969e 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature @@ -5,12 +5,12 @@ Feature: sharing So that other people can access the resource Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: uploading file to a user read-only share folder does not work Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | @@ -30,7 +30,7 @@ Feature: sharing Scenario Outline: uploading file to a group read-only share folder does not work Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Alice" has created folder "FOLDER" @@ -54,7 +54,7 @@ Feature: sharing Scenario Outline: uploading file to a user upload-only share folder works Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | @@ -82,7 +82,7 @@ Feature: sharing Scenario Outline: uploading file to a group upload-only share folder works Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Alice" has created folder "FOLDER" @@ -112,7 +112,7 @@ Feature: sharing @smokeTest Scenario Outline: uploading file to a user read/write share folder works Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | @@ -138,7 +138,7 @@ Feature: sharing Scenario Outline: uploading file to a group read/write share folder works Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Alice" has created folder "FOLDER" @@ -166,7 +166,7 @@ Feature: sharing @smokeTest Scenario Outline: check quota of owners parent directory of a shared file Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Admin" has changed the quota of the personal space of "Brian Murphy" space to "0" And user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/myfile.txt" And user "Alice" has sent the following resource share invitation: @@ -195,7 +195,7 @@ Feature: sharing Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | @@ -217,7 +217,7 @@ Feature: sharing Scenario Outline: uploading to a group shared folder with read/write permission when the sharer has insufficient quota does not work Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Alice" has created folder "FOLDER" @@ -241,7 +241,7 @@ Feature: sharing Scenario Outline: uploading to a user shared folder with upload-only permission when the sharer has insufficient quota does not work Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | @@ -263,7 +263,7 @@ Feature: sharing Scenario Outline: uploading to a group shared folder with upload-only permission when the sharer has insufficient quota does not work Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Alice" has created folder "FOLDER" @@ -287,7 +287,7 @@ Feature: sharing Scenario Outline: sharer can download file uploaded with different 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 "Brian" has been created with default attributes And user "Alice" has created folder "FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | @@ -312,7 +312,7 @@ Feature: sharing Scenario Outline: upload an empty file (size zero byte) to a shared folder Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/folder-to-share" And user "Brian" has sent the following resource share invitation: | resource | folder-to-share | diff --git a/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature index 1a45748c04..5268277e5d 100644 --- a/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature @@ -5,7 +5,7 @@ Feature: changing a public link share So that people who have the public link only have the designated authorization Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | And user "Alice" has created folder "PARENT" diff --git a/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature index 10db74417d..c69ef67889 100644 --- a/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature @@ -6,7 +6,7 @@ Feature: create a public link share So that I can share resources to people who aren't owncloud users Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @smokeTest @skipOnReva Scenario Outline: creating public link share of a file or a folder using the default permissions without password using the public WebDAV API diff --git a/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShareToShares.feature b/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShareToShares.feature index 9944f51ff2..e9920f6ca4 100644 --- a/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShareToShares.feature +++ b/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShareToShares.feature @@ -4,7 +4,7 @@ Feature: create a public link share when share_folder is set to Shares So that I can share resources to people who aren't owncloud users Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: creating a new public link share of a file gives the correct response diff --git a/tests/acceptance/features/coreApiSharePublicLink1/deletePublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink1/deletePublicLinkShare.feature index b5e539a8a0..996ba88bf7 100644 --- a/tests/acceptance/features/coreApiSharePublicLink1/deletePublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink1/deletePublicLinkShare.feature @@ -5,7 +5,7 @@ Feature: delete a public link share So that the public won't have access to the resource inside it Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-1275 Scenario Outline: deleting a public link of a file diff --git a/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature b/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature index 2cef32f5d2..77d17d4d18 100644 --- a/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature +++ b/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature @@ -5,7 +5,7 @@ Feature: copying from public link share So that I can have a backup Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/PARENT" And the config "OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD" has been set to "false" diff --git a/tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature b/tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature index a768a9ac0d..0ad497e8e4 100644 --- a/tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature +++ b/tests/acceptance/features/coreApiSharePublicLink2/multilinkSharing.feature @@ -5,7 +5,7 @@ Feature: multi-link sharing So that I can share them with various permissions and/or different groups of people Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @smokeTest Scenario Outline: creating three public shares of a folder diff --git a/tests/acceptance/features/coreApiSharePublicLink2/updatePublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink2/updatePublicLinkShare.feature index d7bb1c3bd5..e22635a054 100644 --- a/tests/acceptance/features/coreApiSharePublicLink2/updatePublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink2/updatePublicLinkShare.feature @@ -6,7 +6,7 @@ Feature: update a public link share Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: change expiration date of a public link share and get its info diff --git a/tests/acceptance/features/coreApiSharePublicLink2/uploadToPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink2/uploadToPublicLinkShare.feature index 2c9752606f..c1580ecabc 100644 --- a/tests/acceptance/features/coreApiSharePublicLink2/uploadToPublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink2/uploadToPublicLinkShare.feature @@ -6,7 +6,7 @@ Feature: upload to a public link share So that the recipient can upload resources Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "FOLDER" @issue-10331 diff --git a/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature b/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature index a1b463d678..59f1fbd52e 100644 --- a/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature +++ b/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature @@ -6,12 +6,12 @@ Feature: sharing Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes @issue-1289 @issue-7555 Scenario Outline: keep group permissions in sync when the share is renamed by the receiver and then the permissions are updated by sharer Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" @@ -71,7 +71,7 @@ Feature: sharing @issue-2173 Scenario Outline: cannot update a share of a file with a user to have only create and/or delete permission Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has sent the following resource share invitation: | resource | textfile0.txt | @@ -99,7 +99,7 @@ Feature: sharing @issue-2173 Scenario Outline: cannot update a share of a file with a group to have only create and/or delete permission Given using OCS API version "" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" @@ -129,7 +129,7 @@ Feature: sharing @issue-2442 Scenario Outline: share ownership change after moving a shared file to another share Given using DAV path - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | | Brian | | Carol | @@ -161,7 +161,7 @@ Feature: sharing @issue-1253 @issue-1224 @issue-1225 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 "Brian" has been created with default attributes And user "Alice" has created folder "/Alice-folder" And user "Alice" has sent the following resource share invitation: | resource | Alice-folder | @@ -211,8 +211,8 @@ Feature: sharing 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Carol" has been added to group "grp1" @@ -240,7 +240,7 @@ Feature: sharing 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 "Brian" has been created with default attributes And user "Alice" has created folder "/FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | diff --git a/tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature b/tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature index 0534edefba..814d9455c3 100644 --- a/tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature +++ b/tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature @@ -5,7 +5,7 @@ Feature: updating shares to users and groups that have the same name 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: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiSharees/sharees.feature b/tests/acceptance/features/coreApiSharees/sharees.feature index c2ae7ba280..4c7e5c5a94 100644 --- a/tests/acceptance/features/coreApiSharees/sharees.feature +++ b/tests/acceptance/features/coreApiSharees/sharees.feature @@ -4,7 +4,7 @@ Feature: search sharees So that I can find them quickly Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | sharee1 | @@ -162,7 +162,7 @@ Feature: search sharees Scenario Outline: enumerate only group members - only show partial results from member of groups Given using OCS API version "" - And these users have been created with default attributes and without skeleton files: + And these users have been created with default attributes: | username | displayname | | another | Another | And user "Another" has been added to group "ShareeGroup2" @@ -185,7 +185,7 @@ Feature: search sharees Scenario Outline: search without exact match such that the search string matches the user getting the sharees - Given user "sharee2" has been created with default attributes and without skeleton files + Given user "sharee2" has been created with default attributes And using OCS API version "" When user "sharee1" gets the sharees using the sharing API with parameters | search | sharee | @@ -209,7 +209,7 @@ Feature: search sharees @env-config Scenario Outline: search other users when OCIS_SHOW_USER_EMAIL_IN_RESULTS config is enabled - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the config "OCIS_SHOW_USER_EMAIL_IN_RESULTS" has been set to "true" And using OCS API version "" When user "Alice" gets the sharees using the sharing API with parameters @@ -226,7 +226,7 @@ Feature: search sharees @env-config Scenario Outline: search other users when OCIS_SHOW_USER_EMAIL_IN_RESULTS config is disabled - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And the config "OCIS_SHOW_USER_EMAIL_IN_RESULTS" has been set to "false" And using OCS API version "" When user "Alice" gets the sharees using the sharing API with parameters diff --git a/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature b/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature index cec76781bb..31d90a164b 100644 --- a/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature +++ b/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature @@ -5,7 +5,7 @@ Feature: files and folders can be deleted from the trashbin So that I can control my trashbin space and which files are kept in that space Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "to delete" to "/textfile0.txt" And user "Alice" has uploaded file with content "to delete" to "/textfile1.txt" And user "Alice" has created folder "PARENT" @@ -75,7 +75,7 @@ Feature: files and folders can be deleted from the trashbin @issue-3544 @issue-9791 Scenario Outline: user tries to delete another user's trashbin Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has deleted file "/textfile0.txt" And user "Alice" has deleted file "/textfile1.txt" And user "Alice" has deleted file "/PARENT/parent.txt" @@ -94,7 +94,7 @@ Feature: files and folders can be deleted from the trashbin Scenario Outline: user tries to delete trashbin file using invalid password Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has deleted file "/textfile0.txt" And user "Alice" has deleted file "/textfile1.txt" And user "Alice" has deleted file "/PARENT/parent.txt" @@ -113,7 +113,7 @@ Feature: files and folders can be deleted from the trashbin Scenario Outline: user tries to delete trashbin file using no password Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has deleted file "/textfile0.txt" And user "Alice" has deleted file "/textfile1.txt" And user "Alice" has deleted file "/PARENT/parent.txt" diff --git a/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature b/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature index 69f8e3470d..6205d073a4 100644 --- a/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature +++ b/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature @@ -5,7 +5,7 @@ Feature: files and folders exist in the trashbin after being deleted So that I can recover data easily Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "to delete" to "/textfile0.txt" @smokeTest @@ -50,7 +50,7 @@ Feature: files and folders exist in the trashbin after being deleted @skipOnReva Scenario Outline: deleting a file in a shared folder moves it to the trashbin root Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/shared" And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt" And user "Alice" has sent the following resource share invitation: @@ -73,7 +73,7 @@ Feature: files and folders exist in the trashbin after being deleted @skipOnReva Scenario Outline: deleting a shared folder moves it to trashbin Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/shared" And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt" And user "Alice" has sent the following resource share invitation: @@ -144,9 +144,9 @@ Feature: files and folders exist in the trashbin after being deleted @issue-3561 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 + And user "testtrashbin100" has been created with default attributes And user "testtrashbin100" has uploaded file "filesForUpload/textfile.txt" to "/textfile1.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "testtrashbin100" has deleted file "/textfile1.txt" When user "Brian" tries to list the trashbin content for user "testtrashbin100" Then the HTTP status code should be "404" @@ -161,10 +161,10 @@ Feature: files and folders exist in the trashbin after being deleted @issue-3561 @smokeTest 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 + And user "testtrashbin101" has been created with default attributes And user "testtrashbin101" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "testtrashbin101" has uploaded file "filesForUpload/textfile.txt" to "/textfile2.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "testtrashbin101" has deleted file "/textfile0.txt" And user "testtrashbin101" has deleted file "/textfile2.txt" When user "Brian" tries to list the trashbin content for user "testtrashbin101" @@ -181,14 +181,14 @@ Feature: files and folders exist in the trashbin after being deleted @issue-3561 @skipOnReva 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 + And user "testtrashbin102" has been created with default attributes And user "testtrashbin102" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "testtrashbin102" has uploaded file "filesForUpload/textfile.txt" to "/textfile2.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "testtrashbin102" has deleted file "/textfile0.txt" And user "testtrashbin102" has deleted file "/textfile2.txt" And user "testtrashbin102" has been deleted - And user "testtrashbin102" has been created with default attributes and without skeleton files + And user "testtrashbin102" has been created with default attributes And user "testtrashbin102" has uploaded file "filesForUpload/textfile.txt" to "/textfile3.txt" And user "testtrashbin102" has deleted file "/textfile3.txt" When user "Brian" tries to list the trashbin content for user "testtrashbin102" @@ -206,7 +206,7 @@ Feature: files and folders exist in the trashbin after being deleted @issue-3561 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 + And user "testtrashbinempty" has been created with default attributes And user "testtrashbinempty" has uploaded file "filesForUpload/textfile.txt" to "/textfile1.txt" When user "Alice" tries to list the trashbin content for user "testtrashbinempty" Then the HTTP status code should be "404" @@ -258,7 +258,7 @@ Feature: files and folders exist in the trashbin after being deleted Scenario Outline: user with unusual username deletes a file Given using DAV path - And user "" has been created with default attributes and without skeleton files + And user "" has been created with default attributes And user "" has uploaded file with content "to delete" to "/textfile0.txt" When user "" deletes file "/textfile0.txt" using the WebDAV API Then the HTTP status code should be "204" diff --git a/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature b/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature index 8fa69f377b..e7e458cd27 100644 --- a/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature +++ b/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature @@ -5,13 +5,13 @@ Feature: using trashbin together with sharing So that I can restore the resources that were accidentally deleted Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "file to delete" to "/textfile0.txt" @smokeTest @issue-7555 Scenario Outline: deleting a received folder doesn't move it to trashbin Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/shared" And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt" And user "Alice" has sent the following resource share invitation: @@ -34,7 +34,7 @@ Feature: using trashbin together with sharing @issue-1124 @issue-7555 Scenario Outline: sharee deleting a file in a received folder after renaming the shared folder moves it to trashbin of both users Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/shared" And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt" And user "Alice" has sent the following resource share invitation: @@ -58,8 +58,8 @@ Feature: using trashbin together with sharing @issue-1124 Scenario Outline: sharee deleting a file in a group-shared folder moves it to the trashbin of sharee and sharer only Given using DAV path - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Carol" has been added to group "grp1" @@ -87,8 +87,8 @@ Feature: using trashbin together with sharing Scenario Outline: sharer deleting a file in a group-shared folder moves it to the trashbin of sharer only Given using DAV path - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Carol" has been added to group "grp1" @@ -116,8 +116,8 @@ Feature: using trashbin together with sharing @issue-1124 Scenario Outline: sharee deleting a folder in a group-shared folder moves it to the trashbin of sharee and sharer only Given using DAV path - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Carol" has been added to group "grp1" @@ -146,8 +146,8 @@ Feature: using trashbin together with sharing Scenario Outline: sharer deleting a folder in a group-shared folder moves it to the trashbin of sharer only Given using DAV path - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Carol" has been added to group "grp1" @@ -176,7 +176,7 @@ Feature: using trashbin together with sharing @issue-1124 @issue-7555 Scenario Outline: deleting a file in a received folder when restored it comes back to the original path Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/shared" And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt" And user "Alice" has sent the following resource share invitation: @@ -205,7 +205,7 @@ Feature: using trashbin together with sharing Scenario Outline: restoring personal file to a read-only folder Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "shareFolderParent" And user "Brian" has uploaded file with content "file to delete" to "shareFolderParent/textfile0.txt" And user "Brian" has sent the following resource share invitation: @@ -230,7 +230,7 @@ Feature: using trashbin together with sharing Scenario Outline: restoring personal file to a read-only sub-folder Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "shareFolderParent" And user "Brian" has created folder "shareFolderParent/shareFolderChild" And user "Brian" has sent the following resource share invitation: @@ -255,7 +255,7 @@ Feature: using trashbin together with sharing @issue-10356 Scenario Outline: try to restore personal file to a shared folder as an editor Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "shareFolderParent" And user "Brian" has uploaded file with content "file to delete" to "shareFolderParent/textfile0.txt" And user "Brian" has sent the following resource share invitation: diff --git a/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature b/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature index 4452a2767f..05ab77bd5e 100644 --- a/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature +++ b/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature @@ -5,7 +5,7 @@ Feature: restore deleted files/folders So that I can recover accidentally deleted files/folders in ownCloud Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "file to delete" to "/textfile0.txt" @smokeTest @@ -133,7 +133,7 @@ Feature: restore deleted files/folders @smokeTest Scenario Outline: deleted file cannot be restored by a different user Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has deleted file "/textfile0.txt" When user "Brian" tries to restore the file with original path "/textfile0.txt" from the trashbin of user "Alice" using the trashbin API Then the HTTP status code should be "" @@ -148,7 +148,7 @@ Feature: restore deleted files/folders @smokeTest Scenario Outline: deleted file cannot be restored with invalid password Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has deleted file "/textfile0.txt" When user "Alice" tries to restore the file with original path "/textfile0.txt" from the trashbin of user "Alice" using the password "invalid" and the trashbin API Then the HTTP status code should be "401" @@ -163,7 +163,7 @@ Feature: restore deleted files/folders @smokeTest Scenario Outline: deleted file cannot be restored without using a password Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has deleted file "/textfile0.txt" When user "Alice" tries to restore the file with original path "/textfile0.txt" from the trashbin of user "Alice" using the password "" and the trashbin API Then the HTTP status code should be "401" diff --git a/tests/acceptance/features/coreApiVersions/disableFileVersioning.feature b/tests/acceptance/features/coreApiVersions/disableFileVersioning.feature index 9de21b5169..b1dbd01c8a 100644 --- a/tests/acceptance/features/coreApiVersions/disableFileVersioning.feature +++ b/tests/acceptance/features/coreApiVersions/disableFileVersioning.feature @@ -5,7 +5,7 @@ Feature: checking file versions So that I can manage the changes made to the files Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature b/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature index 8d774cf690..3838d34474 100644 --- a/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature +++ b/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature @@ -6,13 +6,13 @@ Feature: file versions remember the author of each version Background: Given using OCS API version "2" - And user "Alice" has been created with default attributes and without skeleton files - 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 + And user "Alice" has been created with default attributes + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes Scenario: enable file versioning and check the history of changes from multiple users - Given user "David" has been created with default attributes and without skeleton files + Given user "David" has been created with default attributes And user "Alice" has created folder "/test" And user "Alice" has sent the following resource share invitation: | resource | test | @@ -272,7 +272,7 @@ Feature: file versions remember the author of each version Scenario: enable file versioning and check the history of changes from multiple users who have a matching folder/file - Given user "David" has been created with default attributes and without skeleton files + Given user "David" has been created with default attributes And user "Brian" has created folder "/test" And user "Brian" has uploaded file with content "duplicate brian" to "/test/textfile0.txt" And user "Brian" has uploaded file with content "overwrite brian" to "/test/textfile0.txt" @@ -354,7 +354,7 @@ Feature: file versions remember the author of each version Scenario: enable file versioning and check the history of changes from multiple users who have a matching file - Given user "David" has been created with default attributes and without skeleton files + Given user "David" has been created with default attributes And user "Brian" has uploaded file with content "duplicate brian" to "/textfile0.txt" And user "Brian" has uploaded file with content "overwrite brian" to "/textfile0.txt" And user "Brian" has sent the following resource share invitation: diff --git a/tests/acceptance/features/coreApiVersions/fileVersions.feature b/tests/acceptance/features/coreApiVersions/fileVersions.feature index 8fca5e1a2c..16be0b5167 100644 --- a/tests/acceptance/features/coreApiVersions/fileVersions.feature +++ b/tests/acceptance/features/coreApiVersions/fileVersions.feature @@ -5,7 +5,7 @@ Feature: dav-versions Background: Given using OCS API version "2" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: upload file and no version is available @@ -119,7 +119,7 @@ Feature: dav-versions Scenario: user cannot access meta folder of a file which is owned by somebody else - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "123" to "/davtest.txt" And we save it into "FILEID" When user "Brian" sends HTTP method "PROPFIND" to URL "/dav/meta/<>" @@ -127,13 +127,13 @@ Feature: dav-versions Scenario: user cannot access meta folder of a file which does not exist - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Brian" sends HTTP method "PROPFIND" to URL "/dav/meta/MTI4NGQyMzgtYWE5Mi00MmNlLWJkYzQtMGIwMDAwMDA5MTU2OjhjY2QyNzUxLTkwYTQtNDBmMi1iOWYzLTYxZWRmODQ0MjFmNA==" Then the HTTP status code should be "400" or "404" Scenario Outline: user cannot access meta folder of a file with invalid fileid - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Brian" sends HTTP method "PROPFIND" to URL "/dav/meta//v" Then the HTTP status code should be "400" or "404" Examples: @@ -241,7 +241,7 @@ Feature: dav-versions Scenario: user cannot retrieve meta information of a file which is owned by somebody else - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "123" to "/davtest.txt " And we save it into "FILEID" When user "Brian" retrieves the meta information of fileId "<>" using the meta API @@ -312,7 +312,7 @@ Feature: dav-versions @skipOnReva Scenario: sharer of a file can see the old version information when the sharee changes the content of the file - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "First content" to "sharefile.txt" And user "Alice" has sent the following resource share invitation: | resource | sharefile.txt | @@ -329,7 +329,7 @@ Feature: dav-versions @skipOnReva Scenario: sharer of a file can restore the original content of a shared file after the file has been modified by the sharee - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "First content" to "sharefile.txt" And user "Alice" has sent the following resource share invitation: | resource | sharefile.txt | @@ -346,7 +346,7 @@ Feature: dav-versions @skipOnReva Scenario: sharer can restore a file inside a shared folder modified by sharee - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/sharingfolder" And user "Alice" has sent the following resource share invitation: | resource | sharingfolder | @@ -364,7 +364,7 @@ Feature: dav-versions @skipOnReva Scenario: sharee cannot see a version of a file inside a shared folder when modified by sharee - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/sharingfolder" And user "Alice" has sent the following resource share invitation: | resource | sharingfolder | @@ -382,7 +382,7 @@ Feature: dav-versions @skipOnReva Scenario: sharer can restore a file inside a shared folder created by sharee and modified by sharer - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/sharingfolder" And user "Alice" has sent the following resource share invitation: | resource | sharingfolder | @@ -400,7 +400,7 @@ Feature: dav-versions @skipOnReva Scenario: sharer can restore a file inside a shared folder created by sharee and modified by sharee - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has created folder "/sharingfolder" And user "Alice" has sent the following resource share invitation: | resource | sharingfolder | @@ -418,8 +418,8 @@ Feature: dav-versions @skipOnReva 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 + Given user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And group "grp1" has been created And user "Brian" has been added to group "grp1" And user "Carol" has been added to group "grp1" @@ -444,7 +444,7 @@ Feature: dav-versions @skipOnReva Scenario Outline: moving a file (with versions) into a shared folder as the sharer Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -477,7 +477,7 @@ Feature: dav-versions @skipOnReva Scenario: sharee tries to get file versions of file not shared by the sharer - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" And user "Alice" has uploaded file with content "textfile1" to "textfile1.txt" And user "Alice" has sent the following resource share invitation: @@ -493,7 +493,7 @@ Feature: dav-versions @skipOnStorage:ceph @skipOnReva Scenario: receiver tries get file versions of shared file from the sharer - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" And user "Alice" has uploaded file with content "version 1" to "textfile0.txt" And user "Alice" has uploaded file with content "version 2" to "textfile0.txt" @@ -510,7 +510,7 @@ Feature: dav-versions @skipOnReva Scenario: receiver tries get file versions of shared file before receiving it - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" And user "Alice" has uploaded file with content "version 1" to "textfile0.txt" And user "Alice" has uploaded file with content "version 2" to "textfile0.txt" diff --git a/tests/acceptance/features/coreApiWebdavDelete/deleteFile.feature b/tests/acceptance/features/coreApiWebdavDelete/deleteFile.feature index 61cab71f3b..60db4d4e0d 100644 --- a/tests/acceptance/features/coreApiWebdavDelete/deleteFile.feature +++ b/tests/acceptance/features/coreApiWebdavDelete/deleteFile.feature @@ -4,7 +4,7 @@ Feature: delete file So that I can remove unwanted data Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @smokeTest Scenario Outline: delete a file diff --git a/tests/acceptance/features/coreApiWebdavDelete/deleteFolder.feature b/tests/acceptance/features/coreApiWebdavDelete/deleteFolder.feature index 6b407cfe80..815025e0f8 100644 --- a/tests/acceptance/features/coreApiWebdavDelete/deleteFolder.feature +++ b/tests/acceptance/features/coreApiWebdavDelete/deleteFolder.feature @@ -4,7 +4,7 @@ Feature: delete folder So that I can quickly remove unwanted data Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" creates folder "/PARENT" using the WebDAV API @smokeTest diff --git a/tests/acceptance/features/coreApiWebdavDelete/deleteFolderContents.feature b/tests/acceptance/features/coreApiWebdavDelete/deleteFolderContents.feature index 1aa85f2738..408f2b3d1b 100644 --- a/tests/acceptance/features/coreApiWebdavDelete/deleteFolderContents.feature +++ b/tests/acceptance/features/coreApiWebdavDelete/deleteFolderContents.feature @@ -4,7 +4,7 @@ Feature: delete folder contents So that I can quickly remove unwanted data Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: removing everything from a folder diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature index 136b4402db..8a039547bf 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature @@ -4,7 +4,7 @@ Feature: propagation of etags when deleting a file or folder So that the client app can know to re-scan and sync the content of the folder(s) Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/upload" @@ -73,7 +73,7 @@ Feature: propagation of etags when deleting a file or folder @skipOnReva Scenario Outline: sharee deleting a file changes the etags of all parents for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/upload/sub" And user "Alice" has uploaded file with content "uploaded content" to "/upload/sub/file.txt" @@ -109,7 +109,7 @@ Feature: propagation of etags when deleting a file or folder @skipOnReva Scenario Outline: sharer deleting a file changes the etags of all parents for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/upload/sub" And user "Alice" has uploaded file with content "uploaded content" to "/upload/sub/file.txt" @@ -145,7 +145,7 @@ Feature: propagation of etags when deleting a file or folder @issue-4251 @skipOnReva Scenario Outline: sharee deleting a folder changes the etags of all parents for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/upload/sub" And user "Alice" has created folder "/upload/sub/toDelete" @@ -181,7 +181,7 @@ Feature: propagation of etags when deleting a file or folder @issue-4251 @skipOnReva Scenario Outline: sharer deleting a folder changes the etags of all parents for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/upload/sub" And user "Alice" has created folder "/upload/sub/toDelete" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature index 2f862bfcc6..b0052d7260 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature @@ -4,7 +4,7 @@ Feature: propagation of etags when moving files or folders So that the client app can know to re-scan and sync the content of the folder(s) Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: renaming a file inside a folder changes its etag @@ -134,7 +134,7 @@ Feature: propagation of etags when moving files or folders @skipOnReva Scenario Outline: sharee renaming a file inside a folder changes its etag for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/upload" And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" @@ -166,7 +166,7 @@ Feature: propagation of etags when moving files or folders @skipOnReva Scenario Outline: sharer renaming a file inside a folder changes its etag for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/upload" And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" @@ -198,7 +198,7 @@ Feature: propagation of etags when moving files or folders @issue-4251 @skipOnReva Scenario Outline: sharer moving a file from one folder to an other changes the etags of both folders for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/src" And user "Alice" has created folder "/dst" @@ -242,7 +242,7 @@ Feature: propagation of etags when moving files or folders @issue-4251 @skipOnReva Scenario Outline: sharer moving a folder from one folder to an other changes the etags of both folders for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/src" And user "Alice" has created folder "/dst" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature index d9f4e20b7e..5cd6160d0b 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature @@ -4,7 +4,7 @@ Feature: propagation of etags when copying files or folders So that the client app can know to re-scan and sync the content of the folder(s) Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-4251 Scenario Outline: copying a file does not change its etag @@ -138,7 +138,7 @@ Feature: propagation of etags when copying files or folders @skipOnReva Scenario Outline: sharee copying a file inside a folder changes its etag for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/upload" And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" @@ -180,7 +180,7 @@ Feature: propagation of etags when copying files or folders @issue-4251 @skipOnReva Scenario Outline: sharer copying a file inside a folder changes its etag for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/upload" And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature index e12aed4004..a4c2d317f8 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature @@ -4,7 +4,7 @@ Feature: propagation of etags when creating folders So that the client app can know to re-scan and sync the content of the folder(s) Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-4251 Scenario Outline: creating a folder inside a folder changes its etag @@ -47,7 +47,7 @@ Feature: propagation of etags when creating folders @issue-4251 @skipOnReva Scenario Outline: sharee creating a folder inside a folder received as a share changes its etag for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/folder" And user "Alice" has sent the following resource share invitation: @@ -78,7 +78,7 @@ Feature: propagation of etags when creating folders @issue-4251 @skipOnReva Scenario Outline: sharer creating a folder inside a shared folder changes etag for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has created folder "/folder" And user "Alice" has sent the following resource share invitation: diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreFromTrash.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreFromTrash.feature index d6b0bc3612..8442551f44 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreFromTrash.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreFromTrash.feature @@ -4,7 +4,7 @@ Feature: propagation of etags when restoring a file or folder from trash So that the client app can know to re-scan and sync the content of the folder(s) Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/upload" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreVersion.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreVersion.feature index 173070f415..7e6ef7526c 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreVersion.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreVersion.feature @@ -6,7 +6,7 @@ Feature: propagation of etags when restoring a version of a file Background: Given using OCS API version "2" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes @skipOnStorage:ceph @skipOnStorage:scality Scenario: restoring a file changes the etags of all parents diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature index e823738b86..a42075e630 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature @@ -4,7 +4,7 @@ Feature: propagation of etags when uploading data So that the client app can know to re-scan and sync the content of the folder(s) Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/upload" @issue-4251 @@ -46,7 +46,7 @@ Feature: propagation of etags when uploading data @issue-4251 @skipOnReva Scenario Outline: sharee uploading a file inside a received shared folder should update etags for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has sent the following resource share invitation: | resource | upload | @@ -76,7 +76,7 @@ Feature: propagation of etags when uploading data @issue-4251 @skipOnReva Scenario Outline: sharer uploading a file inside a shared folder should update etags for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has sent the following resource share invitation: | resource | upload | @@ -106,7 +106,7 @@ Feature: propagation of etags when uploading data @skipOnReva Scenario Outline: sharee overwriting a file inside a received shared folder should update etags for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" And user "Alice" has sent the following resource share invitation: @@ -137,7 +137,7 @@ Feature: propagation of etags when uploading data @skipOnReva Scenario Outline: sharer overwriting a file inside a shared folder should update etags for all collaborators - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes And using DAV path And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" And user "Alice" has sent the following resource share invitation: diff --git a/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature b/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature index 612bd70f6e..ea73465e4c 100644 --- a/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature +++ b/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature @@ -5,7 +5,7 @@ Feature: move (rename) folder Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: rename a folder diff --git a/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature b/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature index a35caac076..194e74f01d 100644 --- a/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature +++ b/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature @@ -5,7 +5,7 @@ Feature: move (rename) file Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes @smokeTest Scenario Outline: moving a file diff --git a/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature b/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature index 52f459874a..c075516d9b 100644 --- a/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature +++ b/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature @@ -6,12 +6,12 @@ Feature: move (rename) file Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: sharer moves a file into a shared folder Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -41,7 +41,7 @@ Feature: move (rename) file Scenario Outline: sharee tries to move a file into a shared folder Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -71,7 +71,7 @@ Feature: move (rename) file Scenario Outline: moving a file out of a shared folder as the sharer Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "test data" to "/testshare/testfile.txt" And user "Brian" has sent the following resource share invitation: @@ -101,7 +101,7 @@ Feature: move (rename) file Scenario Outline: moving a file out of a shared folder as the sharee Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "test data" to "/testshare/testfile.txt" And user "Brian" has sent the following resource share invitation: @@ -130,7 +130,7 @@ Feature: move (rename) file Scenario Outline: moving a folder into a shared folder the sharer Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -161,7 +161,7 @@ Feature: move (rename) file Scenario Outline: moving a folder into a shared folder as the sharee Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -192,7 +192,7 @@ Feature: move (rename) file Scenario Outline: moving a folder out of a shared folder as the sharer Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created the following folders | path | | /testshare | @@ -225,7 +225,7 @@ Feature: move (rename) file Scenario Outline: moving a folder out of a shared folder as the sharee Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created the following folders | path | | /testshare | @@ -257,7 +257,7 @@ Feature: move (rename) file Scenario Outline: sharee moves a file within a shared folder (change/all permissions) Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "testshare" And user "Brian" has created folder "testshare/child" And user "Brian" has uploaded file with content "test data" to "testshare/testfile.txt" @@ -286,7 +286,7 @@ Feature: move (rename) file Scenario Outline: sharee tries to move a file within a shared folder (read permissions) Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "testshare" And user "Brian" has created folder "testshare/child" And user "Brian" has uploaded file with content "test data" to "testshare/testfile.txt" @@ -312,7 +312,7 @@ Feature: move (rename) file @issue-1976 Scenario Outline: sharee tries to move a file into same shared folder with same name Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "testshare" And user "Brian" has uploaded file with content "test data" to "testshare/testfile.txt" And user "Brian" has sent the following resource share invitation: diff --git a/tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature b/tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature index cff07f3205..94ee360ff8 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/downloadFile.feature @@ -4,7 +4,7 @@ Feature: download file So that I can work wih local copies of files on my client system Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" And user "Alice" has uploaded file with content "Welcome this is just an example file for developers." to "/welcome.txt" diff --git a/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature b/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature index 1bc8cd02a3..6ceb6daa56 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature @@ -4,7 +4,7 @@ Feature: list files So that I can understand my file structure in owncloud Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created the following folders | path | | simple-folder | diff --git a/tests/acceptance/features/coreApiWebdavOperations/propfind.feature b/tests/acceptance/features/coreApiWebdavOperations/propfind.feature index 95a46677bf..58e1788bc6 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/propfind.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/propfind.feature @@ -5,7 +5,7 @@ Feature: PROPFIND @issue-751 Scenario Outline: send PROPFIND request to "/dav/(files|spaces)" - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes When user "Alice" requests "" with "PROPFIND" using basic auth Then the HTTP status code should be "405" Examples: @@ -15,7 +15,7 @@ Feature: PROPFIND @issue-10334 Scenario Outline: send PROPFIND request to "/dav/(files|spaces)" with depth header - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes When user "Alice" requests "" with "PROPFIND" using basic auth and with headers | header | value | | depth | | @@ -38,7 +38,7 @@ Feature: PROPFIND @skipOnReva @issue-10071 @issue-10331 Scenario: send PROPFIND request to a public link shared with password - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/PARENT" And using SharingNG And user "Alice" has created the following resource link share: @@ -53,7 +53,7 @@ Feature: PROPFIND @skipOnReva @issue-10071 @issue-10331 Scenario: send PROPFIND request to a public link shared with password (request without password) - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/PARENT" And using SharingNG And user "Alice" has created the following resource link share: @@ -67,7 +67,7 @@ Feature: PROPFIND @skipOnReva @issue-10071 @issue-10331 Scenario: send PROPFIND request to a public link shared with password (request with incorrect password) - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/PARENT" And using SharingNG And user "Alice" has created the following resource link share: diff --git a/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature b/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature index c2240c4656..749aa976dd 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature @@ -24,7 +24,7 @@ Feature: refuse access @issue-2285 Scenario Outline: disabled user cannot use webdav Given using DAV path - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" And user "Alice" has been disabled When user "Alice" downloads file "/textfile0.txt" using the WebDAV API diff --git a/tests/acceptance/features/coreApiWebdavOperations/search.feature b/tests/acceptance/features/coreApiWebdavOperations/search.feature index 8e6f886be9..470899714f 100644 --- a/tests/acceptance/features/coreApiWebdavOperations/search.feature +++ b/tests/acceptance/features/coreApiWebdavOperations/search.feature @@ -5,7 +5,7 @@ Feature: Search So that I can find needed files quickly Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes And user "Alice" has created folder "/just-a-folder" And user "Alice" has created folder "/फनी näme" And user "Alice" has created folder "/upload folder" diff --git a/tests/acceptance/features/coreApiWebdavPreviews/linkSharePreviews.feature b/tests/acceptance/features/coreApiWebdavPreviews/linkSharePreviews.feature index f64268bf37..59a3e2a218 100644 --- a/tests/acceptance/features/coreApiWebdavPreviews/linkSharePreviews.feature +++ b/tests/acceptance/features/coreApiWebdavPreviews/linkSharePreviews.feature @@ -5,7 +5,7 @@ Feature: accessing a public link share So that I can see a small preview of the file before deciding to download it Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | diff --git a/tests/acceptance/features/coreApiWebdavPreviews/previews.feature b/tests/acceptance/features/coreApiWebdavPreviews/previews.feature index 714f09e031..dce7380229 100644 --- a/tests/acceptance/features/coreApiWebdavPreviews/previews.feature +++ b/tests/acceptance/features/coreApiWebdavPreviews/previews.feature @@ -5,7 +5,7 @@ Feature: previews of files downloaded through the webdav API So that I can view the contents of the files Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: download previews with invalid width @@ -137,7 +137,7 @@ Feature: previews of files downloaded through the webdav API Scenario Outline: download previews of shared files (to shares folder) Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file "filesForUpload/" to "/" And user "Alice" has sent the following resource share invitation: | resource | | @@ -161,7 +161,7 @@ Feature: previews of files downloaded through the webdav API Scenario Outline: user tries to download previews of other users files Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt" When user "Brian" downloads the preview of "/parent.txt" of "Alice" with width "32" and height "32" using the WebDAV API Then the HTTP status code should be "404" @@ -217,7 +217,7 @@ Feature: previews of files downloaded through the webdav API @issue-2538 Scenario Outline: when owner updates a shared file, previews for sharee are also updated (to shared folder) Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt" And user "Alice" has sent the following resource share invitation: | resource | parent.txt | @@ -254,7 +254,7 @@ Feature: previews of files downloaded through the webdav API Scenario Outline: updates to a file should change the preview for both sharees and sharers Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "FOLDER" And user "Alice" has uploaded file with content "file to upload" to "/FOLDER/lorem.txt" And user "Alice" has sent the following resource share invitation: @@ -284,8 +284,8 @@ Feature: previews of files downloaded through the webdav API Scenario Outline: updates to a group shared file should change the preview for both sharees and sharers Given using DAV path And group "grp1" has been created - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And user "Brian" has been added to group "grp1" And user "Carol" has been added to group "grp1" And user "Alice" has created folder "FOLDER" diff --git a/tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature b/tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature index 2389049385..85614da0e0 100644 --- a/tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature +++ b/tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature @@ -8,7 +8,7 @@ Feature: sizing of previews of files downloaded through the webdav API but oC10 does not do this auto-fix of the aspect ratio. Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: download different sizes of previews of file diff --git a/tests/acceptance/features/coreApiWebdavProperties/copyFile.feature b/tests/acceptance/features/coreApiWebdavProperties/copyFile.feature index 952b463859..2cbac3fe0d 100644 --- a/tests/acceptance/features/coreApiWebdavProperties/copyFile.feature +++ b/tests/acceptance/features/coreApiWebdavProperties/copyFile.feature @@ -5,7 +5,7 @@ Feature: copy file Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes And 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 1" to "/textfile1.txt" And user "Alice" has created folder "/FOLDER" @@ -52,7 +52,7 @@ Feature: copy file Scenario Outline: copying a file to a folder with no permissions Given using DAV path And the administrator has enabled the permissions role "Secure Viewer" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -76,7 +76,7 @@ Feature: copy file @skipOnReva Scenario Outline: copying a file to overwrite a file into a folder with no permissions Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "ownCloud test text file 1" to "textfile1.txt" And user "Brian" has sent the following resource share invitation: @@ -219,7 +219,7 @@ Feature: copy file @issue-1239 @issue-3874 @issue-9753 @skipOnReva Scenario Outline: copy a file over the top of an existing folder received as a user share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/BRIAN-Folder" And user "Brian" has created folder "BRIAN-Folder/sample-folder" And user "Brian" has sent the following resource share invitation: @@ -245,7 +245,7 @@ Feature: copy file Scenario Outline: copy a file over the top of an existing file received as a share Given using DAV path And user "Alice" has uploaded file with content "file to copy" to "copy.txt" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has uploaded file with content "file to share" to "lorem.txt" And user "Brian" has sent the following resource share invitation: | resource | lorem.txt | @@ -268,7 +268,7 @@ Feature: copy file @issue-1239 @issue-6999 @issue-9753 @skipOnReva Scenario Outline: copy a folder over the top of an existing file received as a user share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has uploaded file with content "file to share" to "/sharedfile1.txt" And user "Brian" has sent the following resource share invitation: | resource | sharedfile1.txt | @@ -293,7 +293,7 @@ Feature: copy file @issue-6999 @issue-9753 @skipOnReva Scenario Outline: copy a folder over the top of an existing folder received as a share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "BRIAN-Folder" And user "Brian" has created folder "BRIAN-Folder/brian-folder" And user "Brian" has sent the following resource share invitation: @@ -319,7 +319,7 @@ Feature: copy file @issue-1239 @skipOnReva Scenario Outline: copy a folder into another folder at different level which is received as a user share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "BRIAN-FOLDER" And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder" And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder/third-level-folder" @@ -349,7 +349,7 @@ Feature: copy file @issue-1239 @skipOnReva Scenario Outline: copy a file into a folder at different level received as a user share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "BRIAN-FOLDER" And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder" And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder/third-level-folder" @@ -381,7 +381,7 @@ Feature: copy file @issue-1239 @skipOnReva Scenario Outline: copy a file into a file at different level received as a user share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "BRIAN-FOLDER" And user "Brian" has uploaded file with content "file at second level" to "BRIAN-FOLDER/second-level-file.txt" And using SharingNG @@ -412,7 +412,7 @@ Feature: copy file @issue-1239 @skipOnReva Scenario Outline: copy a folder into a file at different level received as a user share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "BRIAN-FOLDER" And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder" And user "Brian" has uploaded file with content "file at third level" to "BRIAN-FOLDER/second-level-folder/third-level-file.txt" @@ -443,7 +443,7 @@ Feature: copy file @issue-1239 @issue-9753 @skipOnReva Scenario Outline: copy a file over the top of an existing folder received as a group share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -471,7 +471,7 @@ Feature: copy file @issue-1239 @issue-6999 @issue-9753 @skipOnReva Scenario Outline: copy a folder over the top of an existing file received as a group share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -499,7 +499,7 @@ Feature: copy file @issue-1239 @skipOnReva Scenario Outline: copy a folder into another folder at different level which is received as a group share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -532,7 +532,7 @@ Feature: copy file @issue-1239 @skipOnReva Scenario Outline: copy a file into a folder at different level received as a group share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -567,7 +567,7 @@ Feature: copy file @issue-1239 @skipOnReva Scenario Outline: copy a file into a file at different level received as a group share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -601,7 +601,7 @@ Feature: copy file @issue-1239 @skipOnReva Scenario Outline: copy a folder into a file at different level received as a group share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Alice" has been added to group "grp1" And user "Brian" has been added to group "grp1" @@ -689,7 +689,7 @@ Feature: copy file @skipOnReva Scenario Outline: copying a file into a shared folder as the sharee Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -711,7 +711,7 @@ Feature: copy file @skipOnReva Scenario Outline: copying a file into a shared folder as the sharer Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -734,7 +734,7 @@ Feature: copy file @skipOnReva Scenario Outline: copying a file out of a shared folder as the sharee Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has sent the following resource share invitation: | resource | testshare | @@ -758,7 +758,7 @@ Feature: copy file @skipOnReva Scenario Outline: sharee copies a file from a shared folder, shared with viewer permission Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "hello world" to "testshare/fileInsideShare.txt" And user "Brian" has sent the following resource share invitation: @@ -781,7 +781,7 @@ Feature: copy file Scenario Outline: sharee copies a file from a shared folder, shared with secure viewer permission Given using DAV path And the administrator has enabled the permissions role "Secure Viewer" - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "hello world" to "testshare/fileInsideShare.txt" And user "Brian" has sent the following resource share invitation: @@ -803,7 +803,7 @@ Feature: copy file @skipOnReva Scenario Outline: copying a file out of a shared folder as the sharer Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Brian" has created folder "/testshare" And user "Brian" has uploaded file with content "ownCloud test text file inside share" to "/testshare/fileInsideShare.txt" And user "Brian" has sent the following resource share invitation: @@ -850,8 +850,8 @@ Feature: copy file @skipOnReva Scenario Outline: copying a file between shares received from different users Given using DAV path - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And user "Brian" has created folder "/testshare0" And user "Brian" has uploaded file with content "content inside testshare0" to "/testshare0/testshare0.txt" And user "Carol" has created folder "/testshare1" @@ -885,8 +885,8 @@ Feature: copy file Scenario Outline: copying a file between shares received from different users when one share is shared via Viewer and Secure viewer permission Given using DAV path And the administrator has enabled the permissions role "Secure Viewer" - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And user "Brian" has created folder "/testshare0" And user "Brian" has uploaded file with content "content inside testshare0" to "/testshare0/testshare0.txt" And user "Brian" has created folder "/testshare0/folder_to_copy/" @@ -930,8 +930,8 @@ Feature: copy file @skipOnReva Scenario Outline: copying a folder between shares received from different users Given using DAV path - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And user "Brian" has created folder "/testshare0" And user "Brian" has created folder "/testshare0/folder_to_copy/" And user "Brian" has uploaded file with content "content inside testshare0" to "/testshare0/folder_to_copy/testshare0.txt" @@ -965,8 +965,8 @@ Feature: copy file @skipOnReva Scenario Outline: copying a file to a folder that is shared with multiple users Given using DAV path - 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 + And user "Brian" has been created with default attributes + And user "Carol" has been created with default attributes And user "Alice" has created folder "/testshare" And user "Alice" has sent the following resource share invitation: | resource | testshare | diff --git a/tests/acceptance/features/coreApiWebdavProperties/createFileFolder.feature b/tests/acceptance/features/coreApiWebdavProperties/createFileFolder.feature index 22120ad3b3..98dd4ed697 100644 --- a/tests/acceptance/features/coreApiWebdavProperties/createFileFolder.feature +++ b/tests/acceptance/features/coreApiWebdavProperties/createFileFolder.feature @@ -5,7 +5,7 @@ Feature: create files and folder Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: create a folder diff --git a/tests/acceptance/features/coreApiWebdavProperties/createFileFolderWhenSharesExist.feature b/tests/acceptance/features/coreApiWebdavProperties/createFileFolderWhenSharesExist.feature index f1d88708fa..da61e95d6e 100644 --- a/tests/acceptance/features/coreApiWebdavProperties/createFileFolderWhenSharesExist.feature +++ b/tests/acceptance/features/coreApiWebdavProperties/createFileFolderWhenSharesExist.feature @@ -5,7 +5,7 @@ Feature: create file or folder named similar to Shares folder So that I can organise the files in my file system Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiWebdavProperties/getFileProperties.feature b/tests/acceptance/features/coreApiWebdavProperties/getFileProperties.feature index 6a8aeccfe0..6e81b3b806 100644 --- a/tests/acceptance/features/coreApiWebdavProperties/getFileProperties.feature +++ b/tests/acceptance/features/coreApiWebdavProperties/getFileProperties.feature @@ -5,7 +5,7 @@ Feature: get file properties Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes @smokeTest Scenario Outline: user sends a PROPFIND request on various file names @@ -146,7 +146,7 @@ Feature: get file properties @skipOnReva Scenario Outline: resource that is shared to a user has a share-types property Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/test" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile.txt" And user "Alice" has sent the following resource share invitation: @@ -225,7 +225,7 @@ Feature: get file properties @skipOnReva Scenario Outline: resource that is shared by user,group and link has a share-types property Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And group "grp1" has been created And user "Alice" has created folder "/test" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile.txt" diff --git a/tests/acceptance/features/coreApiWebdavProperties/getQuota.feature b/tests/acceptance/features/coreApiWebdavProperties/getQuota.feature index b9f95fb652..2802588b6d 100644 --- a/tests/acceptance/features/coreApiWebdavProperties/getQuota.feature +++ b/tests/acceptance/features/coreApiWebdavProperties/getQuota.feature @@ -6,7 +6,7 @@ Feature: get quota Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: retrieving folder quota when no quota is set @@ -35,7 +35,7 @@ Feature: get quota @issue-8197 Scenario Outline: retrieving folder quota of shared folder with quota when no quota is set for recipient Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "0" And user "Admin" has changed the quota of the personal space of "Brian Murphy" space to "10000" And user "Brian" has created folder "/testquota" @@ -77,7 +77,7 @@ Feature: get quota Scenario Outline: retrieving folder quota when quota is set and a file was received Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Admin" has changed the quota of the personal space of "Brian Murphy" space to "10000" And user "Alice" has uploaded file "/Alice.txt" of size 93 bytes And user "Alice" has sent the following resource share invitation: diff --git a/tests/acceptance/features/coreApiWebdavProperties/setFileProperties.feature b/tests/acceptance/features/coreApiWebdavProperties/setFileProperties.feature index 26e68c65c4..2ee19a053a 100644 --- a/tests/acceptance/features/coreApiWebdavProperties/setFileProperties.feature +++ b/tests/acceptance/features/coreApiWebdavProperties/setFileProperties.feature @@ -5,7 +5,7 @@ Feature: set file properties Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes @smokeTest @issue-1263 Scenario Outline: setting custom DAV property and reading it @@ -64,7 +64,7 @@ Feature: set file properties @issue-1297 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 + And user "Brian" has been created with default attributes And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustompropshared.txt" And user "Alice" has sent the following resource share invitation: | resource | testcustompropshared.txt | diff --git a/tests/acceptance/features/coreApiWebdavUpload/uploadFile.feature b/tests/acceptance/features/coreApiWebdavUpload/uploadFile.feature index 6491e47bfa..0f84a45296 100644 --- a/tests/acceptance/features/coreApiWebdavUpload/uploadFile.feature +++ b/tests/acceptance/features/coreApiWebdavUpload/uploadFile.feature @@ -5,7 +5,7 @@ Feature: upload file Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes @smokeTest Scenario Outline: upload a file and check etag and download content @@ -326,7 +326,7 @@ Feature: upload file @skipOnReva @issue-7257 Scenario Outline: user updates a shared file with empty content Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has uploaded file with content "file with content" to "/textfile.txt" And user "Alice" has sent the following resource share invitation: | resource | textfile.txt | @@ -358,7 +358,7 @@ Feature: upload file @skipOnReva @issue-7257 Scenario: user updates a file inside a shared space with empty content Given using spaces DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "new-space" with content "file with content" to "textfile.txt" @@ -375,7 +375,7 @@ Feature: upload file @issue-8699 @issue-10331 Scenario: user updates a file inside a link shared space with empty content Given using SharingNG - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API And user "Alice" has created a space "new-space" with the default quota using the Graph API And user "Alice" has created the following space link share: diff --git a/tests/acceptance/features/coreApiWebdavUpload/uploadFileUsingOldChunking.feature b/tests/acceptance/features/coreApiWebdavUpload/uploadFileUsingOldChunking.feature index 484f342b34..9a7c0dd41a 100644 --- a/tests/acceptance/features/coreApiWebdavUpload/uploadFileUsingOldChunking.feature +++ b/tests/acceptance/features/coreApiWebdavUpload/uploadFileUsingOldChunking.feature @@ -6,7 +6,7 @@ Feature: upload file using old chunking Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: upload chunked file in ascending order diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature index 0d9f19fb40..c4c9b7cbbc 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature @@ -4,7 +4,7 @@ Feature: checksums So that the integrity of the uploaded resources is maintained Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: uploading a file with checksum should work diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/creationWithUploadExtension.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/creationWithUploadExtension.feature index 0afb47a6aa..9f91d9e35b 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/creationWithUploadExtension.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/creationWithUploadExtension.feature @@ -4,7 +4,7 @@ Feature: tests of the creation extension see https://tus.io/protocols/resumable- So that I can provide basic information about the resources to the server Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: creating a new upload resource using creation with upload extension diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelCreationExtension.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelCreationExtension.feature index c50f28c124..1eccd274e1 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelCreationExtension.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelCreationExtension.feature @@ -4,7 +4,7 @@ Feature: low level tests of the creation extension see https://tus.io/protocols/ So that I can manage my resources Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: creating a new upload resource diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature index 9b42bbfe8e..d2324791fb 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature @@ -4,7 +4,7 @@ Feature: low level tests for upload of chunks So that I can manage my resources Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario Outline: upload a chunk twice diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature index 54e848204d..3a546a8400 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature @@ -4,7 +4,7 @@ Feature: OPTIONS request So that I can get information about communication options for target resource Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes Scenario: send OPTIONS request to webDav endpoints using the TUS protocol with valid password and username @@ -53,7 +53,7 @@ Feature: OPTIONS request @issue-1012 Scenario: send OPTIONS requests to webDav endpoints using valid password and username of different user - Given user "Brian" has been created with default attributes and without skeleton files + Given user "Brian" has been created with default attributes When user "Brian" requests these endpoints with "OPTIONS" including body "doesnotmatter" using the password of user "Alice" | endpoint | | /webdav/ | diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFile.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFile.feature index 18889c73d0..dfd9c02660 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFile.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFile.feature @@ -4,7 +4,7 @@ Feature: upload file So that I can store and share files between multiple client systems Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-10346 Scenario Outline: upload a file and check download content diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtime.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtime.feature index bba27e80b7..33304efc52 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtime.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtime.feature @@ -4,7 +4,7 @@ Feature: upload file So that I can find files by their real creation date Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-10346 Scenario Outline: upload file with mtime diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtimeShares.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtimeShares.feature index ce7908bd2e..b6f07682b1 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtimeShares.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtimeShares.feature @@ -5,7 +5,7 @@ Feature: upload file So that I can find files by their real creation date Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian | diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToMoveFolder.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToMoveFolder.feature index 163f7706e3..2e2893f011 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToMoveFolder.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToMoveFolder.feature @@ -4,7 +4,7 @@ Feature: move folders So that I can organise my data structure Background: - Given user "Alice" has been created with default attributes and without skeleton files + Given user "Alice" has been created with default attributes @issue-10346 Scenario Outline: uploading file into a moved folder diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToNonExistingFolder.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToNonExistingFolder.feature index acdfd383ca..495f60482b 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToNonExistingFolder.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToNonExistingFolder.feature @@ -5,7 +5,7 @@ Feature: upload file Background: Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files + And user "Alice" has been created with default attributes Scenario Outline: attempt to upload a file into a nonexistent shares @@ -42,7 +42,7 @@ Feature: upload file @skipOnReva Scenario Outline: attempt to upload a file into a nonexistent folder within correctly received share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | @@ -63,7 +63,7 @@ Feature: upload file @skipOnReva Scenario Outline: attempt to upload a file into a nonexistent folder within correctly received read only share Given using DAV path - And user "Brian" has been created with default attributes and without skeleton files + And user "Brian" has been created with default attributes And user "Alice" has created folder "/FOLDER" And user "Alice" has sent the following resource share invitation: | resource | FOLDER | diff --git a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature index f649903a09..3d35870534 100644 --- a/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature +++ b/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature @@ -5,7 +5,7 @@ Feature: upload file to shared folder So that other user with access on the shared folder can access the resource Background: - Given these users have been created with default attributes and without skeleton files: + Given these users have been created with default attributes: | username | | Alice | | Brian |