style: fix gherkin format

LukasHirt · LukasHirt · commit c226e4af3d96 · 2025-09-19T17:19:34.000+02:00
diff --git a/tests/acceptance/features/apiAntivirus/antivirus.feature b/tests/acceptance/features/apiAntivirus/antivirus.feature
@@ -92,6 +92,7 @@ Feature: antivirus
       | new              |
       | spaces           |
 
+
   Scenario Outline: public uploads a file with the virus to a public share
     Given using <dav-path-version> DAV path
     And the config "OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD" has been set to "false" for "sharing" service
@@ -117,6 +118,7 @@ Feature: antivirus
       | spaces           | eicar.com     | virusFile1.txt |
       | spaces           | eicar_com.zip | virusFile2.zip |
 
+
   Scenario Outline: public uploads a file with the virus to a password-protected public share
     Given using <dav-path-version> DAV path
     And using SharingNG
diff --git a/tests/acceptance/features/apiCollaboration/wopi.feature b/tests/acceptance/features/apiCollaboration/wopi.feature
@@ -925,6 +925,7 @@ Feature: collaboration (wopi)
     And as "Alice" file "testFolder/simple.odt" should not exist
     And as "Brian" file "Shares/testFolder/simple.odt" should not exist
 
+
   Scenario Outline: public user with permission edit/upload/createOnly creates odt file inside public folder using wopi endpoint
     Given user "Alice" has created folder "publicFolder"
     And user "Alice" has created the following resource link share:
diff --git a/tests/acceptance/features/apiDepthInfinity/propfind.feature b/tests/acceptance/features/apiDepthInfinity/propfind.feature
@@ -70,6 +70,7 @@ Feature: PROPFIND with depth:infinity
       | new              |
       | spaces           |
 
+
   Scenario: get the list of resources in a folder shared through public link with depth infinity
     Given using SharingNG
     And the following configs have been set:
@@ -119,6 +120,7 @@ Feature: PROPFIND with depth:infinity
       | new              |
       | spaces           |
 
+
   Scenario: get the list of resources in a folder shared through public link with depth infinity when depth infinity is not allowed
     Given the following configs have been set:
       | service | config                                       | value |
diff --git a/tests/acceptance/features/apiLocks/lockFiles.feature b/tests/acceptance/features/apiLocks/lockFiles.feature
@@ -466,6 +466,7 @@ Feature: lock files
       | spaces           | shared     |
       | spaces           | exclusive  |
 
+
   Scenario Outline: lock a file inside a folder shared by a link as anonymous user with edit permission
     Given using <dav-path-version> DAV path
     And using SharingNG
@@ -488,6 +489,7 @@ Feature: lock files
       | spaces           | shared     |
       | spaces           | exclusive  |
 
+
   Scenario Outline: try to lock a file inside a folder shared by a link as anonymous user with read permission
     Given using <dav-path-version> DAV path
     And using SharingNG
@@ -510,6 +512,7 @@ Feature: lock files
       | spaces           | shared     |
       | spaces           | exclusive  |
 
+
   Scenario Outline: lock a file shared by a link as anonymous user with edit permission
     Given using <dav-path-version> DAV path
     And using SharingNG
diff --git a/tests/acceptance/features/apiLocks/unlockFiles.feature b/tests/acceptance/features/apiLocks/unlockFiles.feature
@@ -298,6 +298,7 @@ Feature: unlock locked items
     And using new DAV path
     And user "Brian" should be able to upload file "filesForUpload/lorem.txt" to "Shares/textfile.txt"
 
+
   Scenario Outline: unlock a file as an anonymous user
     Given using <dav-path-version> DAV path
     And using SharingNG
diff --git a/tests/acceptance/features/apiSharingNgDriveLinkShare/updateDriveLinkShare.feature b/tests/acceptance/features/apiSharingNgDriveLinkShare/updateDriveLinkShare.feature
@@ -38,6 +38,7 @@ Feature: Update a link share for a resource
       """
     And the public should be able to download file "textfile.txt" from the last link share with password "%public%" and the content should be "to share"
 
+
   Scenario: update password on a existing link share of a project-space drive using root endpoint
     And using spaces DAV path
     And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
diff --git a/tests/acceptance/features/apiSharingNgItemLinkShare/createLinkShareWithoutPasswordEnforce.feature b/tests/acceptance/features/apiSharingNgItemLinkShare/createLinkShareWithoutPasswordEnforce.feature
@@ -84,6 +84,7 @@ Feature: Link share without enforcing password
       | Edit             | edit                   |
       | Secure View      | blocksDownload         |
 
+
   Scenario: set password on existing file link share
     Given user "Alice" has uploaded file with content "other data" to "textfile1.txt"
     And user "Alice" has created the following resource link share:
@@ -186,6 +187,7 @@ Feature: Link share without enforcing password
       | Edit             | edit                   |
       | Secure View      | blocksDownload         |
 
+
   Scenario: set password on a existing file link share inside project-space
     Given using spaces DAV path
     And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
diff --git a/tests/acceptance/features/apiSharingNgLinkShareManagement/updateItemLinkShare.feature b/tests/acceptance/features/apiSharingNgLinkShareManagement/updateItemLinkShare.feature
@@ -205,6 +205,7 @@ Feature: Update a link share for a resource
       }
       """
 
+
   Scenario: update password of a file's link share using permissions endpoint
     Given user "Alice" has uploaded file with content "other data" to "textfile1.txt"
     And user "Alice" has created the following resource link share:
diff --git a/tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature b/tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature
@@ -21,6 +21,7 @@ Feature: A manager of the space can edit public link
     And user "Alice" has uploaded a file inside space "edit space" with content "some content" to "test.txt"
     And using SharingNG
 
+
   Scenario Outline: manager of the space can edit public link.
     Given using OCS API version "2"
     When user "Alice" updates the last public link share using the sharing API with
diff --git a/tests/acceptance/features/apiSpaces/publicLink.feature b/tests/acceptance/features/apiSpaces/publicLink.feature
@@ -14,24 +14,29 @@ Feature: public link for a space
       | permissionsRole | View         |
     And using SharingNG
 
+
   Scenario: public tries to upload a file in the public space
     When the public uploads file "test.txt" with content "test" using the public WebDAV API
     And the HTTP status code should be "403"
 
+
   Scenario: public tries to create a folder in the public space
     When the public creates folder "created-by-public" using the public WebDAV API
     And the HTTP status code should be "403"
 
+
   Scenario: public tries to delete a file in the public space
     Given user "Alice" has uploaded a file inside space "public space" with content "some content" to "test.txt"
     When the public deletes file "test.txt" from the last public link share using the public WebDAV API
     And the HTTP status code should be "403"
 
+
   Scenario: public tries to delete a folder in the public space
     And user "Alice" has created a folder "/public-folder" in space "public space"
     When the public deletes folder "public-folder" from the last public link share using the public WebDAV API
     And the HTTP status code should be "403"
 
+
   Scenario: public tries to change content of a resources in the public space
     Given user "Alice" has uploaded a file inside space "public space" with content "some content" to "test.txt"
     When the public overwrites file "test.txt" with content "public content" using the public WebDAV API
diff --git a/tests/acceptance/features/apiSpacesShares/shareSpacesViaLink.feature b/tests/acceptance/features/apiSpacesShares/shareSpacesViaLink.feature
@@ -13,6 +13,7 @@ Feature: Share spaces via link
     And user "Alice" has created a space "share space" with the default quota using the Graph API
     And user "Alice" has uploaded a file inside space "share space" with content "some content" to "test.txt"
 
+
   Scenario Outline: manager can share a space to public via link with different permissions
     When user "Alice" creates a public link share of the space "share space" with settings:
       | permissions | <permissions> |
@@ -53,6 +54,7 @@ Feature: Share spaces via link
       | permissions | 0           |
       | share_type  | public_link |
 
+
   Scenario: uploader should be able to upload a file
     When user "Alice" creates a public link share of the space "share space" with settings:
       | permissions | 4                        |
diff --git a/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpaceViaPublicLink.feature b/tests/acceptance/features/apiSpacesShares/shareSubItemOfSpaceViaPublicLink.feature
@@ -118,6 +118,7 @@ Feature: Share a file or folder that is inside a space via public link
       | folder/file.txt | Space Editor |
       | folder/file.txt | Space Viewer |
 
+
   Scenario Outline: user creates a new public link share of a file inside the personal space with edit permissions
     Given using OCS API version "<ocs-api-version>"
     And user "Alice" has uploaded file with content "Random data" to "/file.txt"
diff --git a/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature
@@ -11,6 +11,7 @@ Feature: changing a public link share
     And user "Alice" has created folder "PARENT"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt"
 
+
   Scenario Outline: public can or cannot delete file through publicly shared link depending on having delete permissions using the public WebDAV API
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -28,6 +29,7 @@ Feature: changing a public link share
       | File Drop        | 403              | should        |
       | Edit             | 204              | should not    |
 
+
   Scenario: public link share permissions work correctly for renaming and share permissions edit using the public WebDAV API
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -40,6 +42,7 @@ Feature: changing a public link share
     And as "Alice" file "/PARENT/parent.txt" should not exist
     And as "Alice" file "/PARENT/newparent.txt" should exist
 
+
   Scenario: public link share permissions work correctly for upload with share permissions edit with the public WebDAV API
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -63,6 +66,7 @@ Feature: changing a public link share
     Then the HTTP status code should be "401"
     And as "Alice" file "PARENT/parent.txt" should exist
 
+
   Scenario: public can delete file through publicly shared link with password using the valid password with the public WebDAV API
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -87,6 +91,7 @@ Feature: changing a public link share
     And as "Alice" file "/PARENT/newparent.txt" should not exist
     And as "Alice" file "/PARENT/parent.txt" should exist
 
+
   Scenario: public tries to rename a file in a password protected share using the valid password with the public WebDAV API
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -111,6 +116,7 @@ Feature: changing a public link share
     Then the HTTP status code should be "401"
     And as "Alice" file "/PARENT/lorem.txt" should not exist
 
+
   Scenario: public tries to upload to a password protected public share using the valid password with the public WebDAV API
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -122,6 +128,7 @@ Feature: changing a public link share
     Then the HTTP status code should be "201"
     And as "Alice" file "/PARENT/lorem.txt" should exist
 
+
   Scenario: public cannot rename a file in upload-write-only public link share with the public WebDAV API
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -134,6 +141,7 @@ Feature: changing a public link share
     And as "Alice" file "/PARENT/parent.txt" should exist
     And as "Alice" file "/PARENT/newparent.txt" should not exist
 
+
   Scenario: public cannot delete a file in upload-write-only public link share with the public WebDAV API
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -188,6 +196,7 @@ Feature: changing a public link share
       | 1               | 200              |
       | 2               | 403              |
 
+
   Scenario Outline: administrator removes password of a read-only public link
     Given using OCS API version "<ocs-api-version>"
     And admin has created folder "/PARENT"
diff --git a/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature
@@ -59,6 +59,7 @@ Feature: create a public link share
       | 1               | 100             |
       | 2               | 200             |
 
+
   Scenario Outline: create a new public link share of a file with edit permissions
     Given using OCS API version "<ocs-api-version>"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
@@ -87,6 +88,7 @@ Feature: create a public link share
       | 1               | 100             |
       | 2               | 200             |
 
+
   Scenario Outline: creating a new public link share of a folder, with a password and accessing using the public WebDAV API
     Given using OCS API version "<ocs-api-version>"
     And user "Alice" has created folder "/PARENT"
@@ -167,6 +169,7 @@ Feature: create a public link share
       | 1               | 100             |
       | 2               | 200             |
 
+
   Scenario Outline: creating a link share with no specified permissions defaults to read permissions when public upload is disabled globally and accessing using the public WebDAV API
     Given using OCS API version "<ocs-api-version>"
     And user "Alice" has created folder "/afolder"
@@ -186,6 +189,7 @@ Feature: create a public link share
       | 1               | 100             |
       | 2               | 200             |
 
+
   Scenario Outline: creating a link share with edit permissions keeps it using the public WebDAV API
     Given using OCS API version "<ocs-api-version>"
     And user "Alice" has created folder "/afolder"
@@ -205,6 +209,7 @@ Feature: create a public link share
       | 1               | 100             |
       | 2               | 200             |
 
+
   Scenario Outline: creating a link share with upload permissions keeps it using the public WebDAV API
     Given using OCS API version "<ocs-api-version>"
     And user "Alice" has created folder "/afolder"
@@ -237,6 +242,7 @@ Feature: create a public link share
       | 1               | 200              |
       | 2               | 400              |
 
+
   Scenario Outline: user creates a public link share of a file with file name longer than 64 chars using the public WebDAV API
     Given using OCS API version "<ocs-api-version>"
     And user "Alice" has uploaded file with content "long file" to "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt"
@@ -251,6 +257,7 @@ Feature: create a public link share
       | 1               | 100             |
       | 2               | 200             |
 
+
   Scenario Outline: user creates a public link share of a folder with folder name longer than 64 chars and access using the public WebDAV API
     Given using OCS API version "<ocs-api-version>"
     And user "Alice" has created folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog"
diff --git a/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature b/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature
@@ -9,6 +9,7 @@ Feature: copying from public link share
     And user "Alice" has created folder "/PARENT"
     And the config "OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD" has been set to "false" for "sharing" service
 
+
   Scenario: copy file within a public link folder
     Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
     And using SharingNG
@@ -23,6 +24,7 @@ Feature: copying from public link share
     And the content of file "/PARENT/testfile.txt" for user "Alice" should be "some data"
     And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data"
 
+
   Scenario: copy folder within a public link folder
     Given user "Alice" has created folder "/PARENT/testFolder"
     And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"
@@ -38,6 +40,7 @@ Feature: copying from public link share
     And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data"
     And the content of file "/PARENT/testFolder-copy/testfile.txt" for user "Alice" should be "some data"
 
+
   Scenario: copy file within a public link folder to a new folder
     Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
     And user "Alice" has created folder "/PARENT/testFolder"
@@ -53,6 +56,7 @@ Feature: copying from public link share
     And the content of file "/PARENT/testfile.txt" for user "Alice" should be "some data"
     And the content of file "/PARENT/testFolder/copy1.txt" for user "Alice" should be "some data"
 
+
   Scenario: copy file within a public link folder to existing file
     Given user "Alice" has uploaded file with content "some data 0" to "/PARENT/testfile.txt"
     And user "Alice" has uploaded file with content "some data 1" to "/PARENT/copy1.txt"
@@ -84,6 +88,7 @@ Feature: copying from public link share
     But as "Alice" file "/PARENT/copy1.txt" should not exist
     And as "Alice" file "/copy1.txt" should exist in the trashbin
 
+
   Scenario: copy file within a public link folder and delete file
     Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
     And using SharingNG
@@ -113,6 +118,7 @@ Feature: copying from public link share
     And as "Alice" folder "/PARENT/new-folder" should not exist
     And as "Alice" folder "new-folder" should exist in the trashbin
 
+
   Scenario Outline: copy file with special characters in it's name within a public link folder
     Given user "Alice" has uploaded file with content "some data" to "/PARENT/<file-name>"
     And using SharingNG
@@ -133,6 +139,7 @@ Feature: copying from public link share
       | C++ file.cpp     |
       | sample,1.txt     |
 
+
   Scenario Outline: copy file within a public link folder to a file with special characters in it's name
     Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
     And using SharingNG
@@ -153,6 +160,7 @@ Feature: copying from public link share
       | C++ file.cpp          |
       | sample,1.txt          |
 
+
   Scenario Outline: copy file within a public link folder into a folder with special characters
     Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
     And user "Alice" has created folder "/PARENT/<destination-folder-name>"
diff --git a/tests/acceptance/features/coreApiSharePublicLink2/enforcePasswordPublicLink.feature b/tests/acceptance/features/coreApiSharePublicLink2/enforcePasswordPublicLink.feature
@@ -51,6 +51,7 @@ Feature: enforce password on public link
       | 1               | 100             |
       | 2               | 200             |
 
+
   Scenario Outline: updates a public link to edit permission with a password
     Given the following configs have been set:
       | service  | config                                                 | value |
@@ -78,6 +79,7 @@ Feature: enforce password on public link
       | 1               | 100             |
       | 2               | 200             |
 
+
   Scenario Outline: create a public link with a password in accordance with the password policy
     Given the following configs have been set:
       | service | config                                            | value |
@@ -141,6 +143,7 @@ Feature: enforce password on public link
       | 1               | 200              |
       | 2               | 400              |
 
+
   Scenario Outline: update a public link with a password in accordance with the password policy
     Given the following configs have been set:
       | service | config                                            | value |
@@ -210,6 +213,7 @@ Feature: enforce password on public link
       | 1               | 200              |
       | 2               | 400              |
 
+
   Scenario Outline: create a public link with a password in accordance with the password policy (valid cases)
     Given the config "<config>" has been set to "<config-value>" for "<service>" service
     And using OCS API version "2"
diff --git a/tests/acceptance/features/coreApiSharePublicLink2/updatePublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink2/updatePublicLinkShare.feature
diff --git a/tests/acceptance/features/coreApiSharePublicLink2/uploadToPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink2/uploadToPublicLinkShare.feature

Original file line number	Diff line number	Diff line change
`@@ -205,6 +205,7 @@ Feature: Update a link share for a resource`
`205`	`205`	`}`
`206`	`206`	`"""`
`207`	`207`
	`208`	`+`
`208`	`209`	`Scenario: update password of a file's link share using permissions endpoint`
`209`	`210`	`Given user "Alice" has uploaded file with content "other data" to "textfile1.txt"`
`210`	`211`	`And user "Alice" has created the following resource link share:`