fix typo in then steps

Signed-off-by: prashant-gurung899 <[email protected]>
owncloud · Dec 17, 2024 · f5f30f0 · f5f30f0
1 parent 0832c9b
commit f5f30f0
Show file tree

Hide file tree

Showing 5 changed files with 12 additions and 12 deletions.
diff --git a/tests/acceptance/bootstrap/SpacesContext.php b/tests/acceptance/bootstrap/SpacesContext.php
@@ -1026,7 +1026,7 @@ public function checkPermissionsInResponse(
 	}
 
 	/**
-	 * @Then /^the json responded should not contain a space with name "([^"]*)"$/
+	 * @Then /^the json response should not contain a space with name "([^"]*)"$/
 	 *
 	 * @param string $spaceName
 	 *
@@ -1103,7 +1103,7 @@ public function theUserShouldHaveASpaceInTheDisableState(
 	}
 
 	/**
-	 * @Then /^the json responded should (not|only|)\s?contain spaces of type "([^"]*)"$/
+	 * @Then /^the json response should (not|only|)\s?contain spaces of type "([^"]*)"$/
 	 *
 	 * @param string $onlyOrNot (not|only|)
 	 * @param string $type

diff --git a/tests/acceptance/features/apiGraphUserGroup/deleteUser.feature b/tests/acceptance/features/apiGraphUserGroup/deleteUser.feature
@@ -150,7 +150,7 @@ Feature: delete user
     When the user "Alice" deletes a user "Brian" using the Graph API
     Then the HTTP status code should be "204"
     When user "Alice" lists all spaces via the Graph API with query "$filter=driveType eq 'personal'"
-    Then the json responded should not contain a space with name "Brian Murphy"
+    Then the json response should not contain a space with name "Brian Murphy"
 
 
   Scenario: accepted share is deleted automatically when the user is deleted

diff --git a/tests/acceptance/features/apiOcm/share.feature b/tests/acceptance/features/apiOcm/share.feature
@@ -1272,7 +1272,7 @@ Feature: an user shares resources using ScienceMesh application
     And using server "REMOTE"
     When user "Brian" lists all available spaces via the Graph API
     Then the HTTP status code should be "200"
-    And the json responded should not contain a space with name "folderToShare"
+    And the json response should not contain a space with name "folderToShare"
 
   @issue-10213
   Scenario Outline: local user removes access of federated user from a resource

diff --git a/tests/acceptance/features/apiSpaces/listSpaces.feature b/tests/acceptance/features/apiSpaces/listSpaces.feature
@@ -149,8 +149,8 @@ Feature: List and create spaces
         }
       }
       """
-    And the json responded should not contain a space with name "Shares"
-    And the json responded should only contain spaces of type "personal"
+    And the json response should not contain a space with name "Shares"
+    And the json response should only contain spaces of type "personal"
 
 
   Scenario: ordinary user will not see any space when using a filter for project
@@ -183,7 +183,7 @@ Feature: List and create spaces
         }
       }
       """
-    And the json responded should not contain a space with name "Alice Hansen"
+    And the json response should not contain a space with name "Alice Hansen"
 
 
   Scenario: ordinary user can access their space via the webDav API
@@ -435,7 +435,7 @@ Feature: List and create spaces
     And user "Admin" has created a space "Project Venus" with the default quota using the Graph API
     When user "Alice" tries to look up the single space "Project Venus" owned by the user "Admin" by using its id
     Then the HTTP status code should be "404"
-    And the json responded should not contain a space with name "Project Venus"
+    And the json response should not contain a space with name "Project Venus"
     Examples:
       | user-role  |
       | User       |

diff --git a/tests/acceptance/features/apiSpaces/spaceManagement.feature b/tests/acceptance/features/apiSpaces/spaceManagement.feature
@@ -49,7 +49,7 @@ Feature: Space management
         }
       }
       """
-    And the json responded should not contain a space with name "Alice Hansen"
+    And the json response should not contain a space with name "Alice Hansen"
 
 
   Scenario: space admin user can see another personal spaces
@@ -80,14 +80,14 @@ Feature: Space management
         }
       }
       """
-    And the json responded should not contain a space with name "Project"
+    And the json response should not contain a space with name "Project"
 
 
   Scenario: user without space admin permission cannot see another spaces
     When user "Carol" tries to list all spaces via the Graph API
     Then the HTTP status code should be "200"
-    And the json responded should not contain a space with name "Project"
-    And the json responded should not contain a space with name "Alice Hansen"
+    And the json response should not contain a space with name "Project"
+    And the json response should not contain a space with name "Alice Hansen"
 
 
   Scenario: space admin user changes the name of the project space