backporting from main

owncloud · Nov 6, 2023 · 17374a2 · 17374a2
1 parent a0ed841
commit 17374a2
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 10 deletions.
diff --git a/tests/acceptance/features/apiSpaces/changeSpaces.feature b/tests/acceptance/features/apiSpaces/changeSpaces.feature
@@ -339,7 +339,7 @@ Feature: Change data of space
     When user "<user>" uploads a file inside space "Project Jupiter" owned by the user "Alice" with content "new content" to ".space/readme.md" using the WebDAV API
     Then the HTTP status code should be "<code>"
     And for user "<user>" the content of the file ".space/readme.md" of the space "Project Jupiter" should be "<expectedContent>"
-    When user "<user>" lists all available spaces via the GraphApi
+    When user "<user>" lists all available spaces via the Graph API
     And the JSON response should contain space called "Project Jupiter" owned by "Alice" with description file ".space/readme.md" and match
     """
     {

diff --git a/tests/acceptance/features/apiSpaces/listSpaces.feature b/tests/acceptance/features/apiSpaces/listSpaces.feature
@@ -82,7 +82,7 @@ Feature: List and create spaces
     And user "Brian" has created folder "folder"
     And user "Brian" has shared folder "folder" with user "Alice" with permissions "31"
     And user "Alice" has accepted share "/folder" offered by user "Brian"
-    When user "Alice" lists all available spaces via the GraphApi with query "$filter=driveType eq 'personal'"
+    When user "Alice" lists all available spaces via the Graph API with query "$filter=driveType eq 'personal'"
     Then the HTTP status code should be "200"
     And the JSON response should contain space called "Alice Hansen" and match
     """

diff --git a/tests/acceptance/features/apiSpaces/lockFiles.feature b/tests/acceptance/features/apiSpaces/lockFiles.feature
@@ -91,7 +91,7 @@ Feature: lock files
   Scenario Outline: lock a file in the project space
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And using spaces DAV path
-    And user "Alice" has created a space "Project" with the default quota using the GraphApi
+    And user "Alice" has created a space "Project" with the default quota using the Graph API
     And user "Alice" has uploaded a file inside space "Project" with content "some content" to "textfile.txt"
     And user "Alice" has shared a space "Project" with settings:
       | shareWith | Brian  |
@@ -117,7 +117,7 @@ Feature: lock files
   Scenario Outline: lock a file in the project space using file-id
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And using spaces DAV path
-    And user "Alice" has created a space "Project" with the default quota using the GraphApi
+    And user "Alice" has created a space "Project" with the default quota using the Graph API
     And user "Alice" has uploaded a file inside space "Project" with content "some content" to "textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared a space "Project" with settings:
@@ -144,7 +144,7 @@ Feature: lock files
   Scenario: viewer cannot lock a file in the project space
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And using spaces DAV path
-    And user "Alice" has created a space "Project" with the default quota using the GraphApi
+    And user "Alice" has created a space "Project" with the default quota using the Graph API
     And user "Alice" has uploaded a file inside space "Project" with content "some content" to "textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared a space "Project" with settings:

diff --git a/tests/acceptance/features/apiSpaces/tag.feature b/tests/acceptance/features/apiSpaces/tag.feature
@@ -117,7 +117,7 @@ Feature: Tag
       | folderTag |
       | marketing |
     When user "Brian" accepts share "/folderMain" offered by user "Alice" using the sharing API
-    And user "Brian" lists all available tags via the GraphApi
+    And user "Brian" lists all available tags via the Graph API
     Then the HTTP status code should be "200"
     And the response should contain following tags:
       | folderTag |

diff --git a/tests/acceptance/features/apiSpacesDavOperation/copyByFileId.feature b/tests/acceptance/features/apiSpacesDavOperation/copyByFileId.feature
@@ -75,8 +75,6 @@ Feature: copying file using file id
 
 
   Scenario Outline: copy a file into a folder in project space
-    Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
-    And user "Alice" has created a space "project-space" with the default quota using the Graph API
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And user "Alice" has created a space "project-space" with the default quota using the Graph API
     And user "Alice" has created a folder "/folder" in space "project-space"
@@ -97,8 +95,6 @@ Feature: copying file using file id
   Scenario Outline: copy a file into a sub-folder in project space
     Given the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
     And user "Alice" has created a space "project-space" with the default quota using the Graph API
-    And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
-    And user "Alice" has created a space "project-space" with the default quota using the Graph API
     And user "Alice" has created a folder "folder/sub-folder" in space "project-space"
     And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt"
     And we save it into "FILEID"