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

[full-ci][tests-only] renaming step for sending invitation with all allowed permission
owncloud · Jun 19, 2024 · ee295de · ee295de
2 parents a553429 + dbf94ae
commit ee295de
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/tests/acceptance/features/apiSharingNg/listPermissions.feature b/tests/acceptance/features/apiSharingNg/listPermissions.feature
@@ -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     |

diff --git a/tests/acceptance/features/bootstrap/SharingNgContext.php b/tests/acceptance/features/bootstrap/SharingNgContext.php
@@ -1276,7 +1276,7 @@ public function userShouldHaveSyncEnabledOrDisabledForShare(string $user, string
 	}
 
 	/**
-	 * @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