-
Notifications
You must be signed in to change notification settings - Fork 196
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
test:split apiSharingNg suite for checking if CI time gets reduced
- Loading branch information
1 parent
c6e7ea6
commit 51a4c6c
Showing
14 changed files
with
941 additions
and
918 deletions.
There are no files selected for viewing
100 changes: 50 additions & 50 deletions
100
tests/acceptance/expected-failures-localAPI-on-OCIS-storage.md
Large diffs are not rendered by default.
Oops, something went wrong.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
81 changes: 81 additions & 0 deletions
81
tests/acceptance/features/apiSharingNg2/removeAccessToDriveItemInLinkShare.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,81 @@ | ||
| 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: | ||
| | username | | ||
| | Alice | | ||
| | Brian | | ||
| And using spaces DAV path | ||
|
|
||
|
|
||
| Scenario Outline: user removes access to a folder in link share | ||
| Given user "Alice" has created folder "FolderToShare" | ||
| And user "Alice" has created the following resource link share: | ||
| | resource | FolderToShare | | ||
| | space | Personal | | ||
| | permissionsRole | <permissions-role> | | ||
| | password | %public% | | ||
| When user "Alice" removes the link of folder "FolderToShare" from space "Personal" using the Graph API | ||
| Then the HTTP status code should be "204" | ||
| Examples: | ||
| | permissions-role | | ||
| | view | | ||
| | edit | | ||
| | upload | | ||
| | createOnly | | ||
| | blocksDownload | | ||
|
|
||
|
|
||
| Scenario Outline: user removes access to a file in link share | ||
| Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile.txt" | ||
| And user "Alice" has created the following resource link share: | ||
| | resource | textfile.txt | | ||
| | space | Personal | | ||
| | permissionsRole | <permissions-role> | | ||
| | password | %public% | | ||
| When user "Alice" removes the link of file "textfile.txt" from space "Personal" using the Graph API | ||
| Then the HTTP status code should be "204" | ||
| Examples: | ||
| | permissions-role | | ||
| | view | | ||
| | edit | | ||
| | blocksDownload | | ||
|
|
||
|
|
||
| Scenario Outline: user removes access to a folder in project space in link share | ||
| Given 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 created the following resource link share: | ||
| | resource | FolderToShare | | ||
| | space | NewSpace | | ||
| | permissionsRole | <permissions-role> | | ||
| | password | %public% | | ||
| When user "Alice" removes the link of folder "FolderToShare" from space "NewSpace" using the Graph API | ||
| Then the HTTP status code should be "204" | ||
| Examples: | ||
| | permissions-role | | ||
| | view | | ||
| | edit | | ||
| | upload | | ||
| | createOnly | | ||
| | blocksDownload | | ||
|
|
||
|
|
||
| Scenario Outline: user removes access to a file in project space in link share | ||
| Given 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 "some content" to "textfile.txt" | ||
| And user "Alice" has created the following resource link share: | ||
| | resource | textfile.txt | | ||
| | space | NewSpace | | ||
| | permissionsRole | <permissions-role> | | ||
| | password | %public% | | ||
| When user "Alice" removes the link of file "textfile.txt" from space "NewSpace" using the Graph API | ||
| Then the HTTP status code should be "204" | ||
| Examples: | ||
| | permissions-role | | ||
| | view | | ||
| | edit | | ||
| | blocksDownload | |
Oops, something went wrong.