mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-05-02 00:44:53 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #10682 from owncloud/remove-skeleton-files-line

Browse Source 
[tests-only][full-ci] removing `without skeleton files` string from the user creation steps
This commit is contained in:
Sawjan Gurung
2024-12-02 15:41:48 +05:45
committed by GitHub
parent 2d26ab4007 c98841904d
commit f58f348466
219 changed files with 663 additions and 804 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/TestHelpers/OcisHelper.php
-73
View File
@@ -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
*/
tests/acceptance/TestHelpers/SetupHelper.php
-49
View File
@@ -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);
}
}
tests/acceptance/bootstrap/Provisioning.php
+3 -3
View File
@@ -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|"
*
tests/acceptance/bootstrap/WebDav.php
-19
View File
@@ -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
*
tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature
+4 -4
View File
@@ -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 "<user-role>" using the settings api
When user "Alice" tries to get all existing roles
Then the HTTP status code should be "<http-status-code>"
@@ -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 "<user-role>" using the settings api
When user "Alice" tries to get list of assignment
Then the HTTP status code should be "<http-status-code>"
@@ -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 "<user-role>" using the settings api
When user "Alice" changes his own role to "<desired-role>"
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 |
tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature
+2 -2
View File
@@ -10,9 +10,9 @@ Feature: sharing
Scenario Outline: creating a share of a file with a user
Given using OCS API version "<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:
tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature
+1 -1
View File
@@ -10,7 +10,7 @@ Feature: upload file
Scenario Outline: upload a file and check download content
Given using OCS API version "<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-version> 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"
tests/acceptance/features/apiAccountsHashDifficulty/webDavPUTAuthInvalid.feature
+1 -1
View File
@@ -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"
tests/acceptance/features/apiActivities/activities.feature
+2 -2
View File
@@ -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
tests/acceptance/features/apiActivities/activitiesByFileId.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiActivities/shareActivities.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiAntivirus/antivirus.feature
+8 -8
View File
@@ -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-version> 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-version> 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-version> 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-version> 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 |
tests/acceptance/features/apiArchiver/downloadById.feature
+4 -4
View File
@@ -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"
tests/acceptance/features/apiArchiver/downloadByPath.feature
+3 -3
View File
@@ -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"
tests/acceptance/features/apiAsyncUpload/delayPostprocessing.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiCollaboration/checkFileInfo.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiCollaboration/wopi.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiContract/copy.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiContract/propfind.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiContract/sharesReport.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiContract/spacesReport.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiContract/spacesSharesReport.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiCors/cors.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiDepthInfinity/propfind.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiDownloads/download.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiDownloads/spaceDownload.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiGraph/changeRole.feature
+4 -4
View File
@@ -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 "<user-role>" to user "Brian" using the Graph API
When user "Alice" changes the role of user "Brian" to role "<new-user-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 "<user-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 "<user-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:
tests/acceptance/features/apiGraph/enforcePasswordPublicLink.feature
+11 -11
View File
@@ -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 "<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 "<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 "<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 "<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 "<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 "<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 "<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 "<config>" has been set to "<config-value>"
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 |
tests/acceptance/features/apiGraph/getApplications.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiGraph/getAssignedRole.feature
+3 -3
View File
@@ -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"
tests/acceptance/features/apiGraph/roleManagementEndpoint.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiGraph/unassignRole.feature
+3 -3
View File
@@ -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 "<user-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
tests/acceptance/features/apiGraph/userGDPRExport.feature
+5 -5
View File
@@ -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 "<user-role>" to user "Alice" using the Graph API
And the administrator has assigned the role "<new-user-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:
tests/acceptance/features/apiGraphUserGroup/addUserToGroup.feature
+14 -14
View File
@@ -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 "<user-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 "<user-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
tests/acceptance/features/apiGraphUserGroup/changeOwnPassword.feature
+1 -1
View File
@@ -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 "<current-password>" to "<new-password>" using the Graph API
Then the HTTP status code should be "<http-status-code>"
Examples:
tests/acceptance/features/apiGraphUserGroup/createGroup.feature
+2 -2
View File
@@ -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 "<user-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"
tests/acceptance/features/apiGraphUserGroup/createUser.feature
+3 -3
View File
@@ -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:
tests/acceptance/features/apiGraphUserGroup/deleteGroup.feature
+3 -3
View File
@@ -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 "<user-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:
tests/acceptance/features/apiGraphUserGroup/deleteUser.feature
+9 -9
View File
@@ -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 "<user-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 "<user-role-2>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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 "<user-role-2>" to user "Brian" using the Graph API
And the administrator has assigned the role "<user-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 |
tests/acceptance/features/apiGraphUserGroup/editGroup.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiGraphUserGroup/editUser.feature
+4 -4
View File
@@ -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 "<user>" using the Graph API
Then the HTTP status code should be "<http-status-code>"
And the user information of "<new-user>" 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 "<user-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 "<user-role>" to user "Brian" using the Graph API
When the user "Brian" tries to enable user "Carol" using the Graph API
tests/acceptance/features/apiGraphUserGroup/getGroup.feature
+12 -12
View File
@@ -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 "<user-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 "<user-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 "<user-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 "<user-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 "<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 "<group>" has been created
tests/acceptance/features/apiGraphUserGroup/getUser.feature
+5 -5
View File
@@ -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 "<user>" has been created with default attributes and without skeleton files
Given user "<user>" has been created with default attributes
When user "Brian" tries to search for user "<user>" using Graph API
Then the HTTP status code should be "400"
And the JSON data of the response should match
tests/acceptance/features/apiGraphUserGroup/getUserOwnInformation.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiGraphUserGroup/removeUserFromGroup.feature
+3 -3
View File
@@ -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 "<user-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 "<user-role>" to user "Brian" using the Graph API
And group "grp1" has been created
And user "Alice" has been added to group "grp1"
tests/acceptance/features/apiGraphUserGroup/searchUserIncludingEmail.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiLocks/lockFiles.feature
+2 -2
View File
@@ -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-version> 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"
tests/acceptance/features/apiLocks/unlockFiles.feature
+7 -7
View File
@@ -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-version> 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-version> 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-version> 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-version> 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-version> 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"
tests/acceptance/features/apiNotification/deleteNotification.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiNotification/deprovisioningNotification.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiNotification/emailNotification.feature
+6 -6
View File
@@ -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"
tests/acceptance/features/apiNotification/notification.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiNotification/spaceNotification.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiOcm/acceptInvitation.feature
+2 -2
View File
@@ -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 |
tests/acceptance/features/apiOcm/createInvitation.feature
+2 -2
View File
@@ -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
tests/acceptance/features/apiOcm/deleteFederatedConnections.feature
+2 -2
View File
@@ -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
tests/acceptance/features/apiOcm/searchFederationUsers.feature
+2 -2
View File
@@ -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
tests/acceptance/features/apiOcm/share.feature
+2 -2
View File
@@ -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
tests/acceptance/features/apiReshare/resharing.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSearch1/dateSearch.feature
+2 -2
View File
@@ -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
tests/acceptance/features/apiSearch1/search.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSearch2/mediaTypeSearch.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSearch2/tagSearch.feature
+3 -3
View File
@@ -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-version> 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:
tests/acceptance/features/apiSearchContent/contentSearch.feature
+3 -3
View File
@@ -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-version> 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:
tests/acceptance/features/apiSearchContent/extractedProps.feature
+4 -4
View File
@@ -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 |
tests/acceptance/features/apiSharingNg1/enableDisableShareSync.feature
+5 -5
View File
@@ -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"
tests/acceptance/features/apiSharingNg1/listPermissions.feature
+17 -17
View File
@@ -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"
tests/acceptance/features/apiSharingNg1/propfindShares.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSharingNg1/removeAccessToDrive.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSharingNg1/removeAccessToDriveItem.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSharingNg1/sharedByMe.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSharingNg1/sharedWithMe.feature
+4 -4
View File
@@ -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"
tests/acceptance/features/apiSharingNg1/sharedWithMeSyncDisabled.feature
+5 -5
View File
@@ -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
tests/acceptance/features/apiSharingNg2/removeAccessToDriveItemInLinkShare.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSharingNgLinkSharePermission/createLinkShare.feature
+7 -7
View File
@@ -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 |
tests/acceptance/features/apiSharingNgLinkSharePermission/updateLinkShare.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSharingNgLinkShareRoot/createLinkShare.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSharingNgLinkShareRoot/updateLinkShare.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSharingNgShareInvitation/shareInvitations.feature
+21 -21
View File
@@ -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"
tests/acceptance/features/apiSharingNgShareInvitation/updateShareInvitations.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/changeSpaces.feature
+3 -3
View File
@@ -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:
tests/acceptance/features/apiSpaces/createSpace.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiSpaces/disableAndDeleteSpaces.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/filePreviews.feature
+4 -4
View File
@@ -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 "<source>" to "<destination>" 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 | <destination> |
@@ -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 "<source>" to "<destination>" 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:
tests/acceptance/features/apiSpaces/listSpaces.feature
+3 -3
View File
@@ -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 "<user-role>" to user "Alice" using the Graph API
tests/acceptance/features/apiSpaces/publicLink.feature
+1 -1
View File
@@ -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
tests/acceptance/features/apiSpaces/quota.feature
+3 -3
View File
@@ -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"
tests/acceptance/features/apiSpaces/removeSpaceObjects.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/restoreSpaces.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/setQuota.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/spaceManagement.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/tag.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/trashBin.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpaces/tusUpload.feature
+6 -6
View File
@@ -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-version> 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-version> 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"
tests/acceptance/features/apiSpaces/uploadSpaces.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpacesDavOperation/copyByFileId.feature
+14 -14
View File
@@ -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
tests/acceptance/features/apiSpacesDavOperation/fileVersionByFileID.feature
+1 -1
View File
@@ -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 |
tests/acceptance/features/apiSpacesDavOperation/getFileByFileId.feature
+13 -13
View File
@@ -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 "<dav-path>"
@@ -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"
tests/acceptance/features/apiSpacesDavOperation/moveByFileId.feature
+17 -17
View File
@@ -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"

Some files were not shown because too many files have changed in this diff Show More