mirror/opencloud
1
0 Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-10-21 22:04:41 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #9410 from owncloud/ref-naming-list-perm

Browse Source 
[full-ci][tests-only] renaming step for sending invitation with all allowed permission
This commit is contained in:
Sawjan Gurung authored and GitHub committed 2024-06-19 15:51:42 +05:45
2 parents a553429f22 dbf94aefdd
commit ee295de4c3
2 files changed
+6 -6
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

tests/acceptance/features/apiSharingNg/listPermissions.feature
+5 -5
View File
@@ -1051,7 +1051,7 @@ Feature: List a sharing permissions
And user "Brian" has been created with default attributes and without skeleton files
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 share the following invitation with all allowed permission roles
And user "Alice" should be able to send the following resource share invitation with all allowed permission roles
| resource | textfile.txt |
| space | Personal |
| sharee | Brian |
@@ -1063,7 +1063,7 @@ Feature: List a sharing permissions
And user "Brian" has been created with default attributes and without skeleton files
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 share the following invitation with all allowed permission roles
And user "Alice" should be able to send the following resource share invitation with all allowed permission roles
| resource | folder |
| space | Personal |
| sharee | Brian |
@@ -1266,7 +1266,7 @@ Feature: List a sharing permissions
And user "Brian" has been created with default attributes and without skeleton files
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 share the following invitation with all allowed permission roles
And user "Alice" should be able to send the following resource share invitation with all allowed permission roles
| space | new-space |
| sharee | Brian |
| shareType | user |
@@ -1280,7 +1280,7 @@ Feature: List a sharing permissions
And user "Brian" has been created with default attributes and without skeleton files
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 share the following invitation with all allowed permission roles
And user "Alice" should be able to send the following resource share invitation with all allowed permission roles
| resource | textfile.txt |
| space | new-space |
| sharee | Brian |
@@ -1337,7 +1337,7 @@ Feature: List a sharing permissions
And user "Brian" has been created with default attributes and without skeleton files
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 share the following invitation with all allowed permission roles
And user "Alice" should be able to send the following resource share invitation with all allowed permission roles
| resource | folder |
| space | new-space |
| sharee | Brian |
tests/acceptance/features/bootstrap/SharingNgContext.php
+1 -1
View File
@@ -1276,7 +1276,7 @@ class SharingNgContext implements Context {
}
/**
* @Then user :user should be able to send share the following invitation with all allowed permission roles
* @Then user :user should be able to send the following resource share invitation with all allowed permission roles
*
* @param string $user
* @param TableNode $table