renaming step for sending invitation with all allowed permission

This commit is contained in:
Niraj Acharya
2024-06-19 14:50:38 +05:45
parent 122bb0f1d9
commit dbf94aefdd
2 changed files with 6 additions and 6 deletions

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 |

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