added description on feature files

owncloud · May 2, 2023 · 34ecdec · 34ecdec
1 parent 8b5ce5f
commit 34ecdec
Show file tree

Hide file tree

Showing 13 changed files with 138 additions and 97 deletions.
diff --git a/tests/acceptance/expected-failures-API-on-OCIS-storage.md b/tests/acceptance/expected-failures-API-on-OCIS-storage.md
diff --git a/tests/acceptance/features/coreApiShareManagementToShares/acceptSharesToSharesFolder.feature b/tests/acceptance/features/coreApiShareManagementToShares/acceptSharesToSharesFolder.feature
@@ -13,7 +13,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder
       | Brian    |
 
 
-  Scenario: When accepting a share of a file, the received file is accessible
+  Scenario: when accepting a share of a file, the received file is accessible
     Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
     When user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
@@ -22,15 +22,15 @@ Feature: accept/decline shares coming from internal users to the Shares folder
     And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
 
 
-  Scenario: When accepting a share of a folder, the received folder is accessible
+  Scenario: when accepting a share of a folder, the received folder is accessible
     Given user "Alice" has created folder "/PARENT"
     And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt"
     And user "Alice" has shared file "/PARENT" with user "Brian"
     When user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API
     Then the content of file "/Shares/PARENT/parent.txt" for user "Brian" should be "ownCloud test text file parent"
 
 
-  Scenario: When accepting a share of a file, the response is valid
+  Scenario: when accepting a share of a file, the response is valid
     Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
     When user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
@@ -51,7 +51,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder
     And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
 
 
-  Scenario: When accepting a share of a folder, the response is valid
+  Scenario: when accepting a share of a folder, the response is valid
     Given user "Alice" has created folder "/PARENT"
     And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt"
     And user "Alice" has shared file "/PARENT" with user "Brian"

diff --git a/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature b/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature
@@ -1,5 +1,8 @@
 @api @files_sharing-app-required
 Feature: share access by ID
+  As a user
+  I want to get share with share ID
+  So that I can access resources with valid share ID
 
   Background:
     Given auto-accept shares has been disabled
@@ -9,7 +12,7 @@ Feature: share access by ID
       | Brian    |
 
 
-  Scenario Outline: Get a share with a valid share ID
+  Scenario Outline: get a share with a valid share ID
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
@@ -36,7 +39,7 @@ Feature: share access by ID
       | 2               | 200             |
 
 
-  Scenario Outline: Get a share with an invalid share id
+  Scenario Outline: get a share with an invalid share id
     Given using OCS API version "<ocs_api_version>"
     When user "Alice" gets share with id "<share_id>" using the sharing API
     Then the OCS status code should be "404"

diff --git a/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature
@@ -1,12 +1,15 @@
 @api @files_sharing-app-required @public_link_share-feature-required @issue-1276 @issue-1277
 
 Feature: create a public link share
+  As a user
+  I want to create a publik link share
+  So that I can share resources with different access permissions
 
   Background:
     Given user "Alice" has been created with default attributes and without skeleton files
 
   @smokeTest
-  Scenario Outline: A new public link share of a file using the default permissions only grants read access using the public WebDAV API
+  Scenario Outline: a new public link share of a file using the default permissions only grants read access using the public WebDAV API
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -37,7 +40,7 @@ Feature: create a public link share
       | 2               | 200             |
 
   @smokeTest @issue-1293
-  Scenario Outline: Creating a new public link share of a file with password using the new public WebDAV API
+  Scenario Outline: creating a new public link share of a file with password using the new public WebDAV API
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -69,7 +72,7 @@ Feature: create a public link share
       | 2               | 200             |
 
 
-  Scenario Outline: Create a new public link share of a file with edit permissions
+  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"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -101,7 +104,7 @@ Feature: create a public link share
       | 2               | 200             |
 
 
-  Scenario Outline: Creating a new public link share of a folder using the default permissions only grants read access and can be accessed with no password or any password using the public WebDAV API
+  Scenario Outline: creating a new public link share of a folder using the default permissions only grants read access and can be accessed with no password or any password using the public WebDAV API
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/PARENT"
     And user "Alice" has uploaded file with content "Random data" to "/PARENT/randomfile.txt"
@@ -133,7 +136,7 @@ Feature: create a public link share
       | 2               | 200             |
 
 
-  Scenario Outline: Creating a new public link share of a folder, with a password and accessing using the public WebDAV API
+  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"
     And user "Alice" has uploaded file with content "Random data" to "/PARENT/randomfile.txt"
@@ -168,7 +171,7 @@ Feature: create a public link share
       | 2               | 200             |
 
   @smokeTest
-  Scenario Outline: Getting the share information of public link share from the OCS API does not expose sensitive information
+  Scenario Outline: getting the share information of public link share from the OCS API does not expose sensitive information
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -191,7 +194,7 @@ Feature: create a public link share
       | 2               | 200             |
 
 
-  Scenario Outline: Getting the share information of passwordless public-links hides credential placeholders
+  Scenario Outline: getting the share information of passwordless public-links hides credential placeholders
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -214,7 +217,7 @@ Feature: create a public link share
       | 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
+  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"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -235,7 +238,7 @@ Feature: create a public link share
       | 2               | 200             |
 
 
-  Scenario Outline: Creating a link share with edit permissions keeps it using the public WebDAV API
+  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"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -257,7 +260,7 @@ Feature: create a public link share
       | 2               | 200             |
 
 
-  Scenario Outline: Creating a link share with upload permissions keeps it using the public WebDAV API
+  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"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -279,7 +282,7 @@ Feature: create a public link share
       | 2               | 200             |
 
   @issue-1265 @issue-2079
-  Scenario Outline: Allow public sharing of the root on OCIS when the default permission is read and access using the public WebDAV API
+  Scenario Outline: allow public sharing of the root on OCIS when the default permission is read and access using the public WebDAV API
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     When user "Alice" creates a public link share using the sharing API with settings
@@ -339,7 +342,7 @@ Feature: create a public link share
       | 2               | 200             |
 
   @issue-1293
-  Scenario: Delete a folder that has been publicly shared and try to access using the public WebDAV API
+  Scenario: delete a folder that has been publicly shared and try to access using the public WebDAV API
     Given user "Alice" has created folder "PARENT"
     And user "Alice" has uploaded file with content "Random data" to "/PARENT/parent.txt"
     And user "Alice" has created a public link share with settings
@@ -360,7 +363,7 @@ Feature: create a public link share
     And the HTTP status code should be "404"
 
 
-  Scenario: Get the size of a file shared by public link
+  Scenario: get the size of a file shared by public link
     Given user "Alice" has uploaded file with content "This is a test file" to "test-file.txt"
     And user "Alice" has created a public link share with settings
       | path        | test-file.txt |
@@ -370,7 +373,7 @@ Feature: create a public link share
     And the size of the file should be "19"
 
 
-  Scenario Outline: Get the mtime of a file shared by public link
+  Scenario Outline: get the mtime of a file shared by public link
     Given using <dav_version> DAV path
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API
     When user "Alice" creates a public link share using the sharing API with settings
@@ -384,7 +387,7 @@ Feature: create a public link share
       | new         |
 
 
-  Scenario Outline: Get the mtime of a file inside a folder shared by public link
+  Scenario Outline: get the mtime of a file inside a folder shared by public link
     Given using <dav_version> DAV path
     And user "Alice" has created folder "testFolder"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "testFolder/file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API
@@ -399,7 +402,7 @@ Feature: create a public link share
       | new         |
 
 
-  Scenario: Get the mtime of a file inside a folder shared by public link using new webDAV version
+  Scenario: get the mtime of a file inside a folder shared by public link using new webDAV version
     Given user "Alice" has created folder "testFolder"
     And user "Alice" has created a public link share with settings
       | path        | /testFolder               |

diff --git a/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature
@@ -1,13 +1,16 @@
 @api @files_sharing-app-required @public_link_share-feature-required @issue-1276 @issue-1277 @issue-2079
 
 Feature: upload to a public link share
+  As a user
+  I want to create a public link share with different file permission
+  So that I can manage different file permissions on shared resource
 
   Background:
     Given user "Alice" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "FOLDER"
 
   @smokeTest @issue-1267
-  Scenario: Uploading same file to a public upload-only share multiple times via new API
+  Scenario: uploading same file to a public upload-only share multiple times via new API
     # The new API does the autorename automatically in upload-only folders
     Given user "Alice" has created a public link share with settings
       | path        | FOLDER |
@@ -21,7 +24,7 @@ Feature: upload to a public link share
     And the content of file "/FOLDER/test (2).txt" for user "Alice" should be "test2"
 
 
-  Scenario Outline: Uploading file to a public upload-only share using public API that was deleted does not work
+  Scenario Outline: uploading file to a public upload-only share using public API that was deleted does not work
     Given using <dav-path> DAV path
     And user "Alice" has created a public link share with settings
       | path        | FOLDER |
@@ -42,15 +45,15 @@ Feature: upload to a public link share
       | spaces   |
 
   @issue-1269
-  Scenario: Uploading file to a public read-only share folder with public API does not work
+  Scenario: uploading file to a public read-only share folder with public API does not work
     Given user "Alice" has created a public link share with settings
       | path        | FOLDER |
       | permissions | read   |
     When the public uploads file "test.txt" with content "test" using the new public WebDAV API
     And the HTTP status code should be "403"
 
 
-  Scenario: Uploading to a public upload-only share with public API
+  Scenario: uploading to a public upload-only share with public API
     Given user "Alice" has created a public link share with settings
       | path        | FOLDER |
       | permissions | create |
@@ -61,7 +64,7 @@ Feature: upload to a public link share
       | ETag | /^"[a-f0-9:\.]{1,32}"$/ |
 
 
-  Scenario: Uploading to a public upload-only share with password with public API
+  Scenario: uploading to a public upload-only share with password with public API
     Given user "Alice" has created a public link share with settings
       | path        | FOLDER   |
       | password    | %public% |
@@ -71,7 +74,7 @@ Feature: upload to a public link share
     And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
 
 
-  Scenario: Uploading to a public read/write share with password with public API
+  Scenario: uploading to a public read/write share with password with public API
     Given user "Alice" has created a public link share with settings
       | path        | FOLDER   |
       | password    | %public% |
@@ -81,7 +84,7 @@ Feature: upload to a public link share
     And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
 
 
-  Scenario: Uploading file to a public shared folder with read/write permission when the sharer has insufficient quota does not work with public API
+  Scenario: uploading file to a public shared folder with read/write permission when the sharer has insufficient quota does not work with public API
     When user "Alice" creates a public link share using the sharing API with settings
       | path        | FOLDER |
       | permissions | change |
@@ -90,7 +93,7 @@ Feature: upload to a public link share
     Then the HTTP status code should be "507"
 
   @issue-1290
-  Scenario: Uploading file to a public shared folder with upload-only permission when the sharer has insufficient quota does not work with public API
+  Scenario: uploading file to a public shared folder with upload-only permission when the sharer has insufficient quota does not work with public API
     When user "Alice" creates a public link share using the sharing API with settings
       | path        | FOLDER |
       | permissions | create |
@@ -99,7 +102,7 @@ Feature: upload to a public link share
     Then the HTTP status code should be "507"
 
   @smokeTest
-  Scenario: Uploading to a public upload-write and no edit and no overwrite share with public API
+  Scenario: uploading to a public upload-write and no edit and no overwrite share with public API
     Given user "Alice" has created a public link share with settings
       | path        | FOLDER          |
       | permissions | uploadwriteonly |
@@ -108,7 +111,7 @@ Feature: upload to a public link share
     And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
 
   @smokeTest @issue-1267
-  Scenario: Uploading same file to a public upload-write and no edit and no overwrite share multiple times with new public API
+  Scenario: uploading same file to a public upload-write and no edit and no overwrite share multiple times with new public API
     Given user "Alice" has created a public link share with settings
       | path        | FOLDER          |
       | permissions | uploadwriteonly |

diff --git a/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature b/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature
@@ -1,5 +1,8 @@
 @api @files_sharing-app-required @issue-1328
 Feature: resharing can be disabled
+  As a user
+  I want to disable resharing resources
+  So that I can manage the resharing of resources
 
   Background:
     Given auto-accept shares has been disabled

diff --git a/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature b/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature
@@ -1,5 +1,8 @@
 @api @files_sharing-app-required @issue-1328
 Feature: resharing a resource with an expiration date
+  As a user
+  I want to share resource with an expiration date
+  So that I can share resource for limited time period
 
   Background:
     Given auto-accept shares has been disabled
@@ -10,7 +13,7 @@ Feature: resharing a resource with an expiration date
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
 
 
-  Scenario Outline: User should be able to set expiration while resharing a file with user
+  Scenario Outline: user should be able to set expiration while resharing a file with user
     Given using OCS API version "<ocs_api_version>"
     And user "Carol" has been created with default attributes and without skeleton files
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
@@ -34,7 +37,7 @@ Feature: resharing a resource with an expiration date
       | 2               | 200             |
 
   @issue-1289
-  Scenario Outline: User should be able to set expiration while resharing a file with group
+  Scenario Outline: user should be able to set expiration while resharing a file with group
     Given using OCS API version "<ocs_api_version>"
     And user "Carol" has been created with default attributes and without skeleton files
     And group "grp1" has been created