mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-05-25 06:29:15 -05:00
Code Issues Packages Projects Releases Wiki Activity

remove tests related to resharing (#8338)

Browse Source
This commit is contained in:
Prajwol Amatya
2024-02-01 16:41:31 +05:45
committed by GitHub
parent fbe1b4288b
commit d05a5b4334
2 changed files with 0 additions and 240 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiSharingNg/reshare.feature
-231
View File
@@ -1,231 +0,0 @@
Feature: Reshare a share invitation
As a user
I want to be able to reshare the share invitations to other users
So that they can have access to it
https://owncloud.dev/libre-graph-api/#/drives.permissions/Invite
Background:
Given these users have been created with default attributes and without skeleton files:
| username |
| Alice |
| Brian |
| Carol |
Scenario Outline: reshare a file to a user with different roles
Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt"
And user "Alice" has sent the following share invitation:
| resourceType | file |
| resource | textfile1.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | <permissions-role> |
When user "Brian" sends the following share invitation using the Graph API:
| resourceType | file |
| resource | textfile1.txt |
| space | Shares |
| sharee | Carol |
| shareType | user |
| permissionsRole | <reshare-permissions-role> |
Then the HTTP status code should be "200"
And for user "Carol" the space Shares should contain these entries:
| textfile1.txt |
Examples:
| permissions-role | reshare-permissions-role |
| Viewer | Viewer |
| File Editor | Viewer |
| File Editor | File Editor |
Scenario Outline: reshare a folder to a user with different roles
Given user "Alice" has created folder "FolderToShare"
And user "Alice" has sent the following share invitation:
| resourceType | folder |
| resource | FolderToShare |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | <permissions-role> |
When user "Brian" sends the following share invitation using the Graph API:
| resourceType | folder |
| resource | FolderToShare |
| space | Shares |
| sharee | Carol |
| shareType | user |
| permissionsRole | <reshare-permissions-role> |
Then the HTTP status code should be "200"
And for user "Carol" the space Shares should contain these entries:
| FolderToShare |
Examples:
| permissions-role | reshare-permissions-role |
| Viewer | Viewer |
| Editor | Viewer |
| Editor | Editor |
| Editor | Uploader |
Scenario Outline: reshare a file inside project space to a user with different roles
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 "NewSpace" with the default quota using the Graph API
And user "Alice" has uploaded a file inside space "NewSpace" with content "to share" to "textfile1.txt"
And user "Alice" has sent the following share invitation:
| resourceType | file |
| resource | textfile1.txt |
| space | NewSpace |
| sharee | Brian |
| shareType | user |
| permissionsRole | <permissions-role> |
When user "Brian" sends the following share invitation using the Graph API:
| resourceType | file |
| resource | textfile1.txt |
| space | Shares |
| sharee | Carol |
| shareType | user |
| permissionsRole | <reshare-permissions-role> |
Then the HTTP status code should be "200"
And for user "Carol" the space Shares should contain these entries:
| textfile1.txt |
Examples:
| permissions-role | reshare-permissions-role |
| Viewer | Viewer |
| File Editor | Viewer |
| File Editor | File Editor |
Scenario Outline: reshare a folder inside project space to a user with different roles
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 "NewSpace" with the default quota using the Graph API
And user "Alice" has created a folder "FolderToShare" in space "NewSpace"
And user "Alice" has sent the following share invitation:
| resourceType | folder |
| resource | FolderToShare |
| space | NewSpace |
| sharee | Brian |
| shareType | user |
| permissionsRole | <permissions-role> |
When user "Brian" sends the following share invitation using the Graph API:
| resourceType | folder |
| resource | FolderToShare |
| space | Shares |
| sharee | Carol |
| shareType | user |
| permissionsRole | <reshare-permissions-role> |
Then the HTTP status code should be "200"
And for user "Carol" the space Shares should contain these entries:
| FolderToShare |
Examples:
| permissions-role | reshare-permissions-role |
| Viewer | Viewer |
| Editor | Viewer |
| Editor | Editor |
| Editor | Uploader |
Scenario: try to reshare a resource to higher roles
Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt"
And user "Alice" has sent the following share invitation:
| resourceType | file |
| resource | textfile1.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
When user "Brian" sends the following share invitation using the Graph API:
| resourceType | file |
| resource | textfile1.txt |
| space | Shares |
| sharee | Carol |
| shareType | user |
| permissionsRole | File Editor |
Then the HTTP status code should be "403"
And the JSON data of the response should match
"""
{
"type": "object",
"required": [
"error"
],
"properties": {
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "string",
"enum": [
"accessDenied"
]
},
"message": {
"type": "string",
"enum": [
"insufficient permissions to create that kind of share"
]
}
}
}
}
}
"""
And for user "Carol" the space Shares should not contain these entries:
| textfile1.txt |
Scenario: user with role Uploader tries to reshare a folder
Given user "Alice" has created folder "FolderToShare"
And user "Alice" has sent the following share invitation:
| resourceType | folder |
| resource | FolderToShare |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Uploader |
When user "Brian" sends the following share invitation using the Graph API:
| resourceType | folder |
| resource | FolderToShare |
| space | Shares |
| sharee | Carol |
| shareType | user |
| permissionsRole | Viewer |
Then the HTTP status code should be "403"
And the JSON data of the response should match
"""
{
"type": "object",
"required": [
"error"
],
"properties": {
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "string",
"enum": [
"accessDenied"
]
},
"message": {
"type": "string",
"enum": [
"no permission to add grants on shared resource"
]
}
}
}
}
}
"""
And for user "Carol" the space Shares should not contain these entries:
| textfile1.txt |
tests/acceptance/features/bootstrap/SharingNgContext.php
-9
View File
@@ -148,17 +148,8 @@ class SharingNgContext implements Context {
$spaceId = $space['id'];
// $fileId is used for trying to share deleted files
// for resharing a resource, "item-id" in API endpoint takes shareMountId
if ($fileId) {
$itemId = $fileId;
} elseif ($rows['space'] === 'Shares') {
$itemId = GraphHelper::getShareMountId(
$this->featureContext->getBaseUrl(),
$this->featureContext->getStepLineRef(),
$user,
$this->featureContext->getPasswordForUser($user),
$rows['resource']
);
} else {
$resource = $rows['resource'] ?? '';