From 05dc4155c238e4e51f0bfed2412431f5e5068e4c Mon Sep 17 00:00:00 2001 From: Prarup Gurung Date: Tue, 19 Mar 2024 14:52:16 +0545 Subject: [PATCH] Used kebab case for example table header name --- .../features/apiLocks/lockFiles.feature | 20 +- .../deprovisioningNotification.feature | 20 +- .../apiReshare/disableReshare.feature | 16 +- .../features/apiReshare/resharing.feature | 82 ++++---- .../apiSearch2/mediaTypeSearch.feature | 4 +- .../apiSharingNg/deletePermissions.feature | 176 ++++++++-------- .../features/apiSharingNg/linkShare.feature | 142 ++++++------- .../apiSharingNg/shareInvitations.feature | 196 +++++++++--------- .../updateShareInvitations.feature | 44 ++-- 9 files changed, 350 insertions(+), 350 deletions(-) diff --git a/tests/acceptance/features/apiLocks/lockFiles.feature b/tests/acceptance/features/apiLocks/lockFiles.feature index 65c181e1e0..ebb776fd01 100644 --- a/tests/acceptance/features/apiLocks/lockFiles.feature +++ b/tests/acceptance/features/apiLocks/lockFiles.feature @@ -94,8 +94,8 @@ Feature: lock files 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 | - | role | | + | shareWith | Brian | + | role | | When user "Brian" locks file "textfile.txt" inside the space "Project" using the WebDAV API setting the following properties | lockscope | exclusive | | timeout | Second-3600 | @@ -109,9 +109,9 @@ Feature: lock files | d:lockdiscovery/d:activelock/d:timeout | Second-3600 | | d:lockdiscovery/d:activelock/oc:ownername | Brian Murphy | Examples: - | role | - | manager | - | editor | + | space-role | + | manager | + | editor | Scenario Outline: lock a file in the project space using file-id @@ -121,8 +121,8 @@ Feature: lock files 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: - | shareWith | Brian | - | role | | + | shareWith | Brian | + | role | | When user "Brian" locks file "textfile.txt" using file-id path "" using the WebDAV API setting the following properties | lockscope | exclusive | | timeout | Second-3600 | @@ -136,9 +136,9 @@ Feature: lock files | d:lockdiscovery/d:activelock/d:timeout | Second-3600 | | d:lockdiscovery/d:activelock/oc:ownername | Brian Murphy | Examples: - | role | dav-path | - | manager | /remote.php/dav/spaces/<> | - | editor | /dav/spaces/<> | + | space-role | dav-path | + | manager | /remote.php/dav/spaces/<> | + | editor | /dav/spaces/<> | Scenario: viewer cannot lock a file in the project space diff --git a/tests/acceptance/features/apiNotification/deprovisioningNotification.feature b/tests/acceptance/features/apiNotification/deprovisioningNotification.feature index 58348093a8..51cc718395 100644 --- a/tests/acceptance/features/apiNotification/deprovisioningNotification.feature +++ b/tests/acceptance/features/apiNotification/deprovisioningNotification.feature @@ -89,12 +89,12 @@ Feature: Deprovisioning notification Scenario Outline: non-admin user tries to create a deprovisioning notification - Given the administrator has assigned the role "" to user "Alice" using the Graph API + Given the administrator has assigned the role "" to user "Alice" using the Graph API When user "Alice" tries to create a deprovisioning notification Then the HTTP status code should be "404" And user "Alice" should not have any notification Examples: - | role | + | user-role | | Space Admin | | User | | User Light | @@ -160,19 +160,19 @@ Feature: Deprovisioning notification Scenario Outline: non-admin user tries to delete the deprovisioning notification - Given the administrator has assigned the role "" to user "Alice" using the Graph API + Given the administrator has assigned the role "" to user "Alice" using the Graph API When user "Alice" tries to delete the deprovisioning notification Then the HTTP status code should be "404" And user "Alice" should not have any notification Examples: - | role | + | user-role | | Space Admin | | User | | User Light | Scenario Outline: administrator creates a deprovisioning notification with different date formats - When the administrator creates a deprovisioning notification for date "" of format "" + When the administrator creates a deprovisioning notification for date "" of format "" And user "Alice" lists all notifications Then the HTTP status code of responses on each endpoint should be "200, 200" respectively And the JSON response should contain a notification message with the subject "Instance will be shut down and deprovisioned" and the message-details should match @@ -186,14 +186,14 @@ Feature: Deprovisioning notification "message": { "type": "string", "enum": [ - "Attention! The instance will be shut down and deprovisioned on . Download all your data before that date as no access past that date is possible." + "Attention! The instance will be shut down and deprovisioned on . Download all your data before that date as no access past that date is possible." ] } } } """ Examples: - | deprovision_date | deprovision_date_format | + | deprovision-date | deprovision-date-format | | 2030-04-09T15:04:05.999999999+07:00 | 2006-01-02T15:04:05.999999999Z07:00 | | 5:15PM | 3:04PM | # with date format like `Jan _2 15:04:05`, `_` gets replaced with a space in the response. @@ -206,7 +206,7 @@ Feature: Deprovisioning notification Scenario Outline: administrator change a deprovisioning notification with different date formats Given the administrator has created a deprovisioning notification - When the administrator creates a deprovisioning notification for date "" of format "" + When the administrator creates a deprovisioning notification for date "" of format "" And user "Alice" lists all notifications Then the HTTP status code of responses on each endpoint should be "200, 200" respectively And the JSON response should contain a notification message with the subject "Instance will be shut down and deprovisioned" and the message-details should match @@ -220,14 +220,14 @@ Feature: Deprovisioning notification "message": { "type": "string", "enum": [ - "Attention! The instance will be shut down and deprovisioned on . Download all your data before that date as no access past that date is possible." + "Attention! The instance will be shut down and deprovisioned on . Download all your data before that date as no access past that date is possible." ] } } } """ Examples: - | deprovision_date | deprovision_date_format | + | deprovision-date | deprovision-date-format | | 01/02 03:04:05PM '23 -0700 | 01/02 03:04:05PM '06 -0700 | | Mon Jan 2 15:04:05 UTC 2023 | Mon Jan _2 15:04:05 UTC 2006 | | Mon Jan 02 15:04:05 -0700 2023 | Mon Jan 02 15:04:05 -0700 2006 | diff --git a/tests/acceptance/features/apiReshare/disableReshare.feature b/tests/acceptance/features/apiReshare/disableReshare.feature index 493153ea28..733999c52b 100644 --- a/tests/acceptance/features/apiReshare/disableReshare.feature +++ b/tests/acceptance/features/apiReshare/disableReshare.feature @@ -22,15 +22,15 @@ Feature: share by disabling re-share Then the HTTP status code should be "200" And the OCS status code should be "200" And the fields of the last response to user "Alice" sharing with user "Brian" should include - | permissions | | + | permissions | | Examples: - | dav-path-version | role | expectedPermissions | - | old | editor | 15 | - | old | viewer | 1 | - | new | editor | 15 | - | new | viewer | 1 | - | spaces | editor | 15 | - | spaces | viewer | 1 | + | dav-path-version | role | expected-permissions | + | old | editor | 15 | + | old | viewer | 1 | + | new | editor | 15 | + | new | viewer | 1 | + | spaces | editor | 15 | + | spaces | viewer | 1 | Scenario Outline: try to re-share folder diff --git a/tests/acceptance/features/apiReshare/resharing.feature b/tests/acceptance/features/apiReshare/resharing.feature index fc4da4b02e..ae19ae26a6 100644 --- a/tests/acceptance/features/apiReshare/resharing.feature +++ b/tests/acceptance/features/apiReshare/resharing.feature @@ -27,17 +27,17 @@ Feature: Resharing When user "" gets all the shares inside the folder "Shares/folder" using the sharing API Then the OCS status code should be "100" And the HTTP status code should be "200" - And the response should contain entries + And the response should contain entries And user "Brian" should not be included in the response - And user "Carol" included in the response - And user "Damian" included in the response - And user "Fred" included in the response + And user "Carol" included in the response + And user "Damian" included in the response + And user "Fred" included in the response Examples: - | user | numVisibleShares | CarolVisible | DamianVisible | FredVisible | - | Brian | 2 | should be | should not be | should be | - | Carol | 1 | should not be | should be | should not be | - | Damian | 0 | should not be | should not be | should not be | - | Fred | 0 | should not be | should not be | should not be | + | user | visible-shares-no | carol-visible | damian-visible | fred-visible | + | Brian | 2 | should be | should not be | should be | + | Carol | 1 | should not be | should be | should not be | + | Damian | 0 | should not be | should not be | should not be | + | Fred | 0 | should not be | should not be | should not be | Scenario: owners can see all the chain @@ -60,61 +60,61 @@ Feature: Resharing Given user "Carol" has shared folder "Shares/folder" with user "Fred" with permissions "17" When user "" updates the last share using the sharing API with | permissions | 31 | - Then the OCS status code should be "" - And user "Fred" able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt" + Then the OCS status code should be "" + And user "Fred" able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt" Examples: - | user | code | canUpload | - | Alice | 100 | should be | - | Brian | 998 | should not be | - | Carol | 100 | should be | + | user | ocs-status-code | can-upload | + | Alice | 100 | should be | + | Brian | 998 | should not be | + | Carol | 100 | should be | Scenario Outline: deleting reshares Given user "Carol" has shared folder "Shares/folder" with user "Gina" with permissions "17" When user "" deletes the last share using the sharing API - Then the OCS status code should be "" + Then the OCS status code should be "" And as "Gina" folder "Shares/folder" And as "Carol" folder "Shares/folder" should exist Examples: - | user | code | exists | - | Alice | 100 | should not exist | - | Brian | 998 | should exist | - | Carol | 100 | should not exist | + | user | ocs-status-code | exists | + | Alice | 100 | should not exist | + | Brian | 998 | should exist | + | Carol | 100 | should not exist | @skipOnRevaMaster Scenario Outline: resharing folder with different permissions - When user "" shares folder "Shares/folder" with user "Ember" with permissions "" using the sharing API - Then the OCS status code should be "" + When user "" shares folder "Shares/folder" with user "Ember" with permissions "" using the sharing API + Then the OCS status code should be "" Examples: - | user | permissions | code | - | Brian | 17 | 100 | - | Carol | 31 | 100 | - | Damian | 17 | 100 | - | Damian | 27 | 403 | - | Damian | 31 | 403 | + | user | sharee-permissions | ocs-status-code | + | Brian | 17 | 100 | + | Carol | 31 | 100 | + | Damian | 17 | 100 | + | Damian | 27 | 403 | + | Damian | 31 | 403 | @skipOnRevaMaster Scenario Outline: Resharing files with different permissions Given user "Alice" has uploaded file with content "Random data" to "/file.txt" - And user "Alice" has shared file "/file.txt" with user "Brian" with permissions "" - When user "Brian" shares file "Shares/file.txt" with user "Fred" with permissions "" using the sharing API - Then the OCS status code should be "" + And user "Alice" has shared file "/file.txt" with user "Brian" with permissions "" + When user "Brian" shares file "Shares/file.txt" with user "Fred" with permissions "" using the sharing API + Then the OCS status code should be "" Examples: - | shareepermissions | granteepermissions | code | - | 17 | 17 | 100 | - | 17 | 19 | 403 | - | 19 | 19 | 100 | + | sharee-permissions | grantee-permissions | ocs-status-code | + | 17 | 17 | 100 | + | 17 | 19 | 403 | + | 19 | 19 | 100 | Scenario Outline: resharing with group with different permissions Given group "security department" has been created And the administrator has added a user "Ember" to the group "security department" using the Graph API And the administrator has added a user "Fred" to the group "security department" using the Graph API - When user "Brian" shares folder "Shares/folder" with group "security department" with permissions "" using the sharing API + When user "Brian" shares folder "Shares/folder" with group "security department" with permissions "" using the sharing API Then the OCS status code should be "100" - And user "Ember" able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt" - And user "Fred" able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt" + And user "Ember" able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt" + And user "Fred" able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt" Examples: - | permissions | canUpload | - | 17 | should not be | - | 31 | should be | + | sharee-permissions | can-upload | + | 17 | should not be | + | 31 | should be | diff --git a/tests/acceptance/features/apiSearch2/mediaTypeSearch.feature b/tests/acceptance/features/apiSearch2/mediaTypeSearch.feature index 48a8ebfd45..7f5d33d362 100644 --- a/tests/acceptance/features/apiSearch2/mediaTypeSearch.feature +++ b/tests/acceptance/features/apiSearch2/mediaTypeSearch.feature @@ -178,8 +178,8 @@ Feature: media type search Then the HTTP status code should be "207" And the search result should contain "2" entries And the search result of user "Alice" should contain these entries: - | %spaceid% | - | testFolder | + | %spaceid% | + | testFolder | When user "Alice" searches for "mediatype:document" using the WebDAV API Then the HTTP status code should be "207" And the search result should contain "2" entries diff --git a/tests/acceptance/features/apiSharingNg/deletePermissions.feature b/tests/acceptance/features/apiSharingNg/deletePermissions.feature index ffc90cb127..2cac0783bc 100644 --- a/tests/acceptance/features/apiSharingNg/deletePermissions.feature +++ b/tests/acceptance/features/apiSharingNg/deletePermissions.feature @@ -13,22 +13,22 @@ Feature: Remove access to a drive item Given user "Alice" has created folder "FolderToShare" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile.txt" And user "Alice" has sent the following share invitation: - | resource | | - | space | Personal | - | sharee | Brian | - | shareType | user | - | permissionsRole | | - When user "Alice" removes the share permission of user "Brian" from resource "" of space "Personal" using the Graph API + | resource | | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | | + When user "Alice" removes the share permission of user "Brian" from resource "" of space "Personal" using the Graph API Then the HTTP status code should be "204" And for user "Brian" the space "Shares" should not contain these entries: - | | + | | Examples: - | permissionsRole | path | - | Viewer | textfile.txt | - | File Editor | textfile.txt | - | Viewer | FolderToShare | - | Editor | FolderToShare | - | Uploader | FolderToShare | + | permissions-role | resource | + | Viewer | textfile.txt | + | File Editor | textfile.txt | + | Viewer | FolderToShare | + | Editor | FolderToShare | + | Uploader | FolderToShare | Scenario Outline: user removes access to resource inside of a project space in the user share @@ -37,22 +37,22 @@ Feature: Remove access to a drive item And user "Alice" has created a folder "FolderToShare" in space "NewSpace" And user "Alice" has uploaded a file inside space "NewSpace" with content "some content" to "textfile.txt" And user "Alice" has sent the following share invitation: - | resource | | - | space | NewSpace | - | sharee | Brian | - | shareType | user | - | permissionsRole | | - When user "Alice" removes the share permission of user "Brian" from resource "" of space "NewSpace" using the Graph API + | resource | | + | space | NewSpace | + | sharee | Brian | + | shareType | user | + | permissionsRole | | + When user "Alice" removes the share permission of user "Brian" from resource "" of space "NewSpace" using the Graph API Then the HTTP status code should be "204" And for user "Brian" the space "Shares" should not contain these entries: - | | + | | Examples: - | permissionsRole | path | - | Viewer | textfile.txt | - | File Editor | textfile.txt | - | Viewer | FolderToShare | - | Editor | FolderToShare | - | Uploader | FolderToShare | + | permissions-role | resource | + | Viewer | textfile.txt | + | File Editor | textfile.txt | + | Viewer | FolderToShare | + | Editor | FolderToShare | + | Uploader | FolderToShare | Scenario Outline: user removes access to a resource in a group share @@ -62,22 +62,22 @@ Feature: Remove access to a drive item And user "Alice" has created folder "FolderToShare" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile.txt" And user "Alice" has sent the following share invitation: - | resource | | - | space | Personal | - | sharee | group1 | - | shareType | group | - | permissionsRole | | - When user "Alice" removes the share permission of group "group1" from resource "" of space "Personal" using the Graph API + | resource | | + | space | Personal | + | sharee | group1 | + | shareType | group | + | permissionsRole | | + When user "Alice" removes the share permission of group "group1" from resource "" of space "Personal" using the Graph API Then the HTTP status code should be "204" And for user "Brian" the space "Shares" should not contain these entries: - | | + | | Examples: - | permissionsRole | path | - | Viewer | textfile.txt | - | File Editor | textfile.txt | - | Viewer | FolderToShare | - | Editor | FolderToShare | - | Uploader | FolderToShare | + | permissions-role | resource | + | Viewer | textfile.txt | + | File Editor | textfile.txt | + | Viewer | FolderToShare | + | Editor | FolderToShare | + | Uploader | FolderToShare | Scenario Outline: user removes access to a resource inside of a project space in group share @@ -89,56 +89,56 @@ Feature: Remove access to a drive item And user "Brian" has been added to group "group1" And user "Alice" has been added to group "group1" And user "Alice" has sent the following share invitation: - | resource | | - | space | NewSpace | - | sharee | group1 | - | shareType | group | - | permissionsRole | | - When user "Alice" removes the share permission of group "group1" from resource "" of space "NewSpace" using the Graph API + | resource | | + | space | NewSpace | + | sharee | group1 | + | shareType | group | + | permissionsRole | | + When user "Alice" removes the share permission of group "group1" from resource "" of space "NewSpace" using the Graph API Then the HTTP status code should be "204" And for user "Brian" the space "Shares" should not contain these entries: - | | + | | Examples: - | permissionsRole | path | - | Viewer | textfile.txt | - | File Editor | textfile.txt | - | Viewer | FolderToShare | - | Editor | FolderToShare | - | Uploader | FolderToShare | + | permissions-role | resource | + | Viewer | textfile.txt | + | File Editor | textfile.txt | + | Viewer | FolderToShare | + | Editor | FolderToShare | + | Uploader | FolderToShare | Scenario Outline: user removes access to a folder in link share Given user "Alice" has created folder "FolderToShare" And user "Alice" has created the following link share: - | resource | FolderToShare | - | space | Personal | - | permissionsRole | | - | password | %public% | + | resource | FolderToShare | + | space | Personal | + | permissionsRole | | + | password | %public% | When user "Alice" removes the share permission of link from folder "FolderToShare" of space "Personal" using the Graph API Then the HTTP status code should be "204" Examples: - | role | - | view | - | edit | - | upload | - | createOnly | - | blocksDownload | + | permissions-role | + | view | + | edit | + | upload | + | createOnly | + | blocksDownload | Scenario Outline: user removes access to a file in link share Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile.txt" And user "Alice" has created the following link share: - | resource | textfile.txt | - | space | Personal | - | permissionsRole | | - | password | %public% | + | resource | textfile.txt | + | space | Personal | + | permissionsRole | | + | password | %public% | When user "Alice" removes the share permission of link from file "textfile.txt" of space "Personal" using the Graph API Then the HTTP status code should be "204" Examples: - | permissionsRole | - | view | - | edit | - | blocksDownload | + | permissions-role | + | view | + | edit | + | blocksDownload | Scenario Outline: user removes access to a folder in project space in link share @@ -146,19 +146,19 @@ Feature: Remove access to a drive item And user "Alice" has created a space "NewSpace" with the default quota using the Graph API And user "Alice" has created a folder "FolderToShare" in space "NewSpace" And user "Alice" has created the following link share: - | resource | FolderToShare | - | space | NewSpace | - | permissionsRole | | - | password | %public% | + | resource | FolderToShare | + | space | NewSpace | + | permissionsRole | | + | password | %public% | When user "Alice" removes the share permission of link from folder "FolderToShare" of space "NewSpace" using the Graph API Then the HTTP status code should be "204" Examples: - | role | - | view | - | edit | - | upload | - | createOnly | - | blocksDownload | + | permissions-role | + | view | + | edit | + | upload | + | createOnly | + | blocksDownload | Scenario Outline: user removes access to a file in project space in link share @@ -166,14 +166,14 @@ Feature: Remove access to a drive item And user "Alice" has created a space "NewSpace" with the default quota using the Graph API And user "Alice" has uploaded a file inside space "NewSpace" with content "some content" to "textfile.txt" And user "Alice" has created the following link share: - | resource | textfile.txt | - | space | NewSpace | - | permissionsRole | | - | password | %public% | + | resource | textfile.txt | + | space | NewSpace | + | permissionsRole | | + | password | %public% | When user "Alice" removes the share permission of link from file "textfile.txt" of space "NewSpace" using the Graph API Then the HTTP status code should be "204" Examples: - | permissionsRole | - | view | - | edit | - | blocksDownload | + | permissions-role | + | view | + | edit | + | blocksDownload | diff --git a/tests/acceptance/features/apiSharingNg/linkShare.feature b/tests/acceptance/features/apiSharingNg/linkShare.feature index 8293d40110..c8eb3e80ac 100644 --- a/tests/acceptance/features/apiSharingNg/linkShare.feature +++ b/tests/acceptance/features/apiSharingNg/linkShare.feature @@ -10,10 +10,10 @@ Feature: Create a share link for a resource Scenario Outline: create a link share of a folder Given user "Alice" has created folder "folder" When user "Alice" creates the following link share using the Graph API: - | resource | folder | - | space | Personal | - | permissionsRole | | - | password | %public% | + | resource | folder | + | space | Personal | + | permissionsRole | | + | password | %public% | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -57,7 +57,7 @@ Feature: Create a share link for a resource }, "type": { "type": "string", - "const": "" + "const": "" }, "webUrl": { "type": "string", @@ -69,12 +69,12 @@ Feature: Create a share link for a resource } """ Examples: - | permissionsRole | - | view | - | edit | - | upload | - | createOnly | - | blocksDownload | + | permissions-role | + | view | + | edit | + | upload | + | createOnly | + | blocksDownload | @issue-8619 Scenario: create an internal link share of a folder @@ -152,10 +152,10 @@ Feature: Create a share link for a resource Scenario Outline: create a link share of a file Given user "Alice" has uploaded file with content "other data" to "textfile1.txt" When user "Alice" creates the following link share using the Graph API: - | resource | textfile1.txt | - | space | Personal | - | permissionsRole | | - | password | %public% | + | resource | textfile1.txt | + | space | Personal | + | permissionsRole | | + | password | %public% | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -199,7 +199,7 @@ Feature: Create a share link for a resource }, "type": { "type": "string", - "const": "" + "const": "" }, "webUrl": { "type": "string", @@ -211,10 +211,10 @@ Feature: Create a share link for a resource } """ Examples: - | permissionsRole | - | view | - | edit | - | blocksDownload | + | permissions-role | + | view | + | edit | + | blocksDownload | @issue-8619 Scenario: create an internal link share of a file @@ -294,7 +294,7 @@ Feature: Create a share link for a resource When user "Alice" creates the following link share using the Graph API: | resource | folder | | space | Personal | - | permissionsRole | | + | permissionsRole | | | password | %public% | | displayName | Homework | | expirationDateTime | 2200-07-15T14:00:00.000Z | @@ -346,7 +346,7 @@ Feature: Create a share link for a resource }, "type": { "type": "string", - "const": "" + "const": "" }, "webUrl": { "type": "string", @@ -358,12 +358,12 @@ Feature: Create a share link for a resource } """ Examples: - | permissionsRole | - | view | - | edit | - | upload | - | createOnly | - | blocksDownload | + | permissions-role | + | view | + | edit | + | upload | + | createOnly | + | blocksDownload | @issue-7879 Scenario Outline: create a link share of a file with display name and expiry date @@ -371,7 +371,7 @@ Feature: Create a share link for a resource When user "Alice" creates the following link share using the Graph API: | resource | textfile1.txt | | space | Personal | - | permissionsRole | | + | permissionsRole | | | password | %public% | | displayName | Homework | | expirationDateTime | 2200-07-15T14:00:00.000Z | @@ -423,7 +423,7 @@ Feature: Create a share link for a resource }, "type": { "type": "string", - "const": "" + "const": "" }, "webUrl": { "type": "string", @@ -435,10 +435,10 @@ Feature: Create a share link for a resource } """ Examples: - | permissionsRole | - | view | - | edit | - | blocksDownload | + | permissions-role | + | view | + | edit | + | blocksDownload | @env-config @issue-7879 Scenario Outline: create a link share of a file without password @@ -447,9 +447,9 @@ Feature: Create a share link for a resource | OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD | false | And user "Alice" has uploaded file with content "other data" to "textfile1.txt" When user "Alice" creates the following link share using the Graph API: - | resource | textfile1.txt | - | space | Personal | - | permissionsRole | | + | resource | textfile1.txt | + | space | Personal | + | permissionsRole | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -493,7 +493,7 @@ Feature: Create a share link for a resource }, "type": { "type": "string", - "const": "" + "const": "" }, "webUrl": { "type": "string", @@ -505,24 +505,24 @@ Feature: Create a share link for a resource } """ Examples: - | permissionsRole | - | view | - | edit | - | internal | - | blocksDownload | + | permissions-role | + | view | + | edit | + | internal | + | blocksDownload | @issue-7879 Scenario Outline: update role of a file's link share Given user "Alice" has uploaded file with content "other data" to "textfile1.txt" And user "Alice" has created the following link share: - | resource | textfile1.txt | - | space | Personal | - | permissionsRole | | - | password | %public% | + | resource | textfile1.txt | + | space | Personal | + | permissionsRole | | + | password | %public% | When user "Alice" updates the last public link share using the Graph API with - | resource | textfile1.txt | - | space | Personal | - | permissionsRole | | + | resource | textfile1.txt | + | space | Personal | + | permissionsRole | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -566,7 +566,7 @@ Feature: Create a share link for a resource }, "type": { "type": "string", - "const": "" + "const": "" }, "webUrl": { "type": "string", @@ -578,22 +578,22 @@ Feature: Create a share link for a resource } """ Examples: - | previousPermissionsRole | newPermissionsRole | - | view | edit | - | view | blocksDownload | - | edit | view | - | edit | blocksDownload | - | blocksDownload | edit | - | blocksDownload | blocksDownload | + | permissions-role | new-permissions-role | + | view | edit | + | view | blocksDownload | + | edit | view | + | edit | blocksDownload | + | blocksDownload | edit | + | blocksDownload | blocksDownload | @issue-8619 Scenario Outline: update role of a file's to internal link share Given user "Alice" has uploaded file with content "other data" to "textfile1.txt" And user "Alice" has created the following link share: - | resource | textfile1.txt | - | space | Personal | - | permissionsRole | | - | password | %public% | + | resource | textfile1.txt | + | space | Personal | + | permissionsRole | | + | password | %public% | When user "Alice" updates the last public link share using the Graph API with | resource | textfile1.txt | | space | Personal | @@ -653,10 +653,10 @@ Feature: Create a share link for a resource } """ Examples: - | previousPermissionsRole | - | view | - | edit | - | blocksDownload | + | permissions-role | + | view | + | edit | + | blocksDownload | Scenario: update expiration date of a file's link share @@ -732,15 +732,15 @@ Feature: Create a share link for a resource Given user "Alice" has uploaded file with content "other data" to "textfile1.txt" And user "Alice" has created folder "folder" And user "Alice" has created the following link share: - | resource | | + | resource | | | space | Personal | | permissionsRole | view | | password | %public% | | expirationDateTime | 2200-07-15T14:00:00.000Z | When user "Alice" updates the last public link share using the Graph API with - | resource | | - | space | Personal | - | expirationDateTime | | + | resource | | + | space | Personal | + | expirationDateTime | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -792,7 +792,7 @@ Feature: Create a share link for a resource } """ Examples: - | path | + | resource | | textfile1.txt | | folder | diff --git a/tests/acceptance/features/apiSharingNg/shareInvitations.feature b/tests/acceptance/features/apiSharingNg/shareInvitations.feature index 214a1834dc..5630bb4212 100644 --- a/tests/acceptance/features/apiSharingNg/shareInvitations.feature +++ b/tests/acceptance/features/apiSharingNg/shareInvitations.feature @@ -16,14 +16,14 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | Brian | | shareType | user | | permissionsRole | | Then the HTTP status code should be "200" And for user "Brian" the space Shares should contain these entries: - | | + | | And the JSON data of the response should match """ { @@ -91,7 +91,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -109,16 +109,16 @@ Feature: Send a sharing invitations And user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | grp1 | | shareType | group | | permissionsRole | | Then the HTTP status code should be "200" And for user "Brian" the space Shares should contain these entries: - | | + | | And for user "Carol" the space Shares should contain these entries: - | | + | | And the JSON data of the response should match """ { @@ -186,7 +186,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -197,11 +197,11 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation for a file to user with different permissions Given user "Alice" has uploaded file with content "to share" to "textfile1.txt" When user "Alice" sends the following share invitation using the Graph API: - | resource | textfile1.txt | - | space | Personal | - | sharee | Brian | - | shareType | user | - | permissionsAction | | + | resource | textfile1.txt | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsAction | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -233,7 +233,7 @@ Feature: Send a sharing invitations "minItems": 1, "items": { "type": "string", - "pattern": "^libre\\.graph\\/driveItem\\/$" + "pattern": "^libre\\.graph\\/driveItem\\/$" } }, "grantedToV2": { @@ -270,7 +270,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissionsAction | + | permissions-action | | permissions/create | | upload/create | | path/read | @@ -292,11 +292,11 @@ Feature: Send a sharing invitations Scenario Outline: send share invitation for a folder to user with different permissions Given user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | FolderToShare | - | space | Personal | - | sharee | Brian | - | shareType | user | - | permissionsAction | | + | resource | FolderToShare | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsAction | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -328,7 +328,7 @@ Feature: Send a sharing invitations "maxItems": 1, "items": { "type": "string", - "pattern": "^libre\\.graph\\/driveItem\\/$" + "pattern": "^libre\\.graph\\/driveItem\\/$" } }, "grantedToV2": { @@ -365,7 +365,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissionsAction | + | permissions-action | | permissions/create | | children/create | | upload/create | @@ -396,11 +396,11 @@ Feature: Send a sharing invitations | Carol | grp1 | And user "Alice" has uploaded file with content "to share" to "textfile1.txt" When user "Alice" sends the following share invitation using the Graph API: - | resource | textfile1.txt | - | space | Personal | - | sharee | grp1 | - | shareType | group | - | permissionsAction | | + | resource | textfile1.txt | + | space | Personal | + | sharee | grp1 | + | shareType | group | + | permissionsAction | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -432,7 +432,7 @@ Feature: Send a sharing invitations "maxItems": 1, "items": { "type": "string", - "pattern": "^libre\\.graph\\/driveItem\\/$" + "pattern": "^libre\\.graph\\/driveItem\\/$" } }, "grantedToV2": { @@ -469,7 +469,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissionsAction | + | permissions-action | | permissions/create | | upload/create | | path/read | @@ -497,11 +497,11 @@ Feature: Send a sharing invitations | Carol | grp1 | And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | FolderToShare | - | space | Personal | - | sharee | grp1 | - | shareType | group | - | permissionsAction | | + | resource | FolderToShare | + | space | Personal | + | sharee | grp1 | + | shareType | group | + | permissionsAction | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -533,7 +533,7 @@ Feature: Send a sharing invitations "maxItems": 1, "items": { "type": "string", - "pattern": "^libre\\.graph\\/driveItem\\/$" + "pattern": "^libre\\.graph\\/driveItem\\/$" } }, "grantedToV2": { @@ -570,7 +570,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissionsAction | + | permissions-action | | permissions/create | | children/create | | upload/create | @@ -596,7 +596,7 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | Brian | | shareType | user | @@ -677,7 +677,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -695,7 +695,7 @@ Feature: Send a sharing invitations And user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | grp1 | | shareType | group | @@ -776,7 +776,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -789,7 +789,7 @@ Feature: Send a sharing invitations And user "Alice" has created folder "FolderToShare" And the user "Admin" has disabled user "Brian" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | Brian | | shareType | user | @@ -862,7 +862,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -881,7 +881,7 @@ Feature: Send a sharing invitations And user "Alice" has created folder "FolderToShare" And the administrator has deleted group "grp1" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | grp1 | | shareType | group | @@ -920,7 +920,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -933,7 +933,7 @@ Feature: Send a sharing invitations And user "Alice" has created folder "FolderToShare" And the user "Admin" has deleted a user "Brian" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | Brian | | shareType | user | @@ -970,7 +970,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -993,7 +993,7 @@ Feature: Send a sharing invitations And user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | grp1, grp2 | | shareType | group, group | @@ -1032,7 +1032,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -1054,7 +1054,7 @@ Feature: Send a sharing invitations And user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | grp1, Bob | | shareType | group, user | @@ -1093,7 +1093,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -1105,7 +1105,7 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | nonExistentGroup | | shareType | group | @@ -1144,7 +1144,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -1162,13 +1162,13 @@ Feature: Send a sharing invitations And user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" And user "Alice" has sent the following share invitation: - | resource | | + | resource | | | space | Personal | | sharee | grp1 | | shareType | group | | permissionsRole | | When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | grp1 | | shareType | group | @@ -1205,7 +1205,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | /textfile1.txt | | File Editor | /textfile1.txt | | Viewer | FolderToShare | @@ -1217,7 +1217,7 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" tries to send the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | shareeId | a4c0c83e-ae24-4870-93c3-fcaf2a2228f7 | | shareType | user | @@ -1254,7 +1254,7 @@ Feature: Send a sharing invitations } """ Examples: - | path | + | resource | | /textfile1.txt | | FolderToShare | @@ -1263,11 +1263,11 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" tries to send the following share invitation using the Graph API: - | resource | | - | space | Personal | - | shareeId | | - | shareType | user | - | permissionsRole | Viewer | + | resource | | + | space | Personal | + | shareeId | | + | shareType | user | + | permissionsRole | Viewer | Then the HTTP status code should be "400" And the JSON data of the response should match """ @@ -1300,7 +1300,7 @@ Feature: Send a sharing invitations } """ Examples: - | path | + | resource | | /textfile1.txt | | FolderToShare | @@ -1309,7 +1309,7 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" tries to send the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | Brian | | shareType | wrongShareType | @@ -1346,7 +1346,7 @@ Feature: Send a sharing invitations } """ Examples: - | path | + | resource | | /textfile1.txt | | FolderToShare | @@ -1361,7 +1361,7 @@ Feature: Send a sharing invitations | Brian | grp1 | | Carol | grp1 | When user "Alice" tries to send the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | grp1 | | shareType | wrongShareType | @@ -1398,7 +1398,7 @@ Feature: Send a sharing invitations } """ Examples: - | path | + | resource | | /textfile1.txt | | FolderToShare | @@ -1407,11 +1407,11 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" tries to send the following share invitation using the Graph API: - | resource | | - | space | Personal | - | sharee | Brian | - | shareType | | - | permissionsRole | Viewer | + | resource | | + | space | Personal | + | sharee | Brian | + | shareType | | + | permissionsRole | Viewer | Then the HTTP status code should be "400" And the JSON data of the response should match """ @@ -1444,7 +1444,7 @@ Feature: Send a sharing invitations } """ Examples: - | path | + | resource | | /textfile1.txt | | FolderToShare | @@ -1459,11 +1459,11 @@ Feature: Send a sharing invitations | Brian | grp1 | | Carol | grp1 | When user "Alice" tries to send the following share invitation using the Graph API: - | resource | | - | space | Personal | - | sharee | grp1 | - | shareType | | - | permissionsRole | Viewer | + | resource | | + | space | Personal | + | sharee | grp1 | + | shareType | | + | permissionsRole | Viewer | Then the HTTP status code should be "400" And the JSON data of the response should match """ @@ -1496,7 +1496,7 @@ Feature: Send a sharing invitations } """ Examples: - | path | + | resource | | /textfile1.txt | | FolderToShare | @@ -1505,7 +1505,7 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" When user "Alice" sends the following share invitation using the Graph API: - | resource | | + | resource | | | space | Personal | | sharee | Brian | | shareType | user | @@ -1544,7 +1544,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Manager | /textfile1.txt | | Space Viewer | /textfile1.txt | | Space Editor | /textfile1.txt | @@ -1604,17 +1604,17 @@ Feature: Send a sharing invitations Given user "Alice" has uploaded file with content "to share" to "textfile1.txt" And user "Alice" has created folder "FolderToShare" And user "Alice" has sent the following share invitation: - | resource | | - | space | Personal | - | sharee | Brian | - | shareType | user | - | permissionsRole | Viewer | + | resource | | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Viewer | When user "Alice" tries to send the following share invitation using the Graph API: - | resource | | - | space | Personal | - | sharee | Brian | - | shareType | user | - | permissionsRole | Viewer | + | resource | | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Viewer | Then the HTTP status code should be "409" And the JSON data of the response should match """ @@ -1645,7 +1645,7 @@ Feature: Send a sharing invitations } """ Examples: - | path | + | resource | | /textfile1.txt | | FolderToShare | @@ -2109,14 +2109,14 @@ Feature: Send a sharing invitations And user "Alice" has uploaded a file inside space "NewSpace" with content "share space items" to "textfile1.txt" And user "Alice" has created a folder "FolderToShare" in space "NewSpace" When user "Alice" sends the following share invitation for space using the Graph API: - | resource | | + | resource | | | space | NewSpace | | sharee | Brian | | shareType | user | | permissionsRole | | Then the HTTP status code should be "200" And for user "Brian" the space Shares should contain these entries: - | | + | | And the JSON data of the response should match """ { @@ -2179,7 +2179,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | textfile1.txt | | File Editor | textfile1.txt | | Viewer | FolderToShare | @@ -2200,16 +2200,16 @@ Feature: Send a sharing invitations And user "Alice" has uploaded a file inside space "NewSpace" with content "share space items" to "textfile1.txt" And user "Alice" has created a folder "FolderToShare" in space "NewSpace" When user "Alice" sends the following share invitation for space using the Graph API: - | resource | | + | resource | | | space | NewSpace | | sharee | grp1 | | shareType | group | | permissionsRole | | Then the HTTP status code should be "200" And for user "Brian" the space Shares should contain these entries: - | | + | | And for user "Carol" the space Shares should contain these entries: - | | + | | And the JSON data of the response should match """ { @@ -2277,7 +2277,7 @@ Feature: Send a sharing invitations } """ Examples: - | permissions-role | path | + | permissions-role | resource | | Viewer | textfile1.txt | | File Editor | textfile1.txt | | Viewer | FolderToShare | diff --git a/tests/acceptance/features/apiSharingNg/updateShareInvitations.feature b/tests/acceptance/features/apiSharingNg/updateShareInvitations.feature index 610d13f031..fa929151ac 100644 --- a/tests/acceptance/features/apiSharingNg/updateShareInvitations.feature +++ b/tests/acceptance/features/apiSharingNg/updateShareInvitations.feature @@ -87,16 +87,16 @@ Feature: Update permission of a share Given user "Alice" has uploaded file with content "hello world" to "testfile.txt" And user "Alice" has created folder "folder" And user "Alice" has sent the following share invitation: - | resource | | + | resource | | | space | Personal | | sharee | Brian | | shareType | user | | permissionsRole | Viewer | | expirationDateTime | 2025-07-15T14:00:00Z | When user "Alice" updates the last share with the following using the Graph API: - | space | Personal | - | resource | | - | expirationDateTime | | + | space | Personal | + | resource | | + | expirationDateTime | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -150,7 +150,7 @@ Feature: Update permission of a share } """ Examples: - | path | + | resource | | testfile.txt | | folder | @@ -159,15 +159,15 @@ Feature: Update permission of a share Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt" And user "Alice" has created folder "FolderToShare" And user "Alice" has sent the following share invitation: - | resource | | - | space | Personal | - | sharee | Brian | - | shareType | user | - | permissionsRole | | + | resource | | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | | When user "Alice" updates the last share with the following using the Graph API: - | permissionsRole | | - | space | Personal | - | resource | | + | permissionsRole | | + | space | Personal | + | resource | | Then the HTTP status code should be "200" And the JSON data of the response should match """ @@ -221,12 +221,12 @@ Feature: Update permission of a share } """ Examples: - | previous-permissions-role | path | new-permissions-role | - | Viewer | textfile1.txt | File Editor | - | File Editor | textfile1.txt | Viewer | - | Viewer | FolderToShare | Uploader | - | Viewer | FolderToShare | Editor | - | Editor | FolderToShare | Viewer | - | Editor | FolderToShare | Uploader | - | Uploader | FolderToShare | Editor | - | Uploader | FolderToShare | Viewer | + | permissions-role | resource | new-permissions-role | + | Viewer | textfile1.txt | File Editor | + | File Editor | textfile1.txt | Viewer | + | Viewer | FolderToShare | Uploader | + | Viewer | FolderToShare | Editor | + | Editor | FolderToShare | Viewer | + | Editor | FolderToShare | Uploader | + | Uploader | FolderToShare | Editor | + | Uploader | FolderToShare | Viewer |