From 8b6df0d7291617fde0cace05e121c0adaa59d17a Mon Sep 17 00:00:00 2001 From: Prarup Gurung Date: Tue, 7 Feb 2023 11:38:44 +0545 Subject: [PATCH] Removed scenarios tagged with @skipOnOcis tag --- .../coreApiCapabilities/capabilities.feature | 823 ------------------ .../createShareExpirationDate.feature | 0 .../createShareUniqueReceivedNames.feature | 12 +- ...createShareWhenExcludedFromSharing.feature | 83 -- .../createShareReceivedInMultipleWays.feature | 21 +- ...eWhenShareWithOnlyMembershipGroups.feature | 127 --- .../createShareToSharesFolder.feature | 15 +- .../mergeShare.feature | 5 - .../gettingShares.feature | 35 +- .../updatePublicLinkShare.feature | 34 +- .../reShareDisabled.feature | 17 - ...eWhenShareWithOnlyMembershipGroups.feature | 48 - .../updateShare.feature | 7 +- .../coreApiTrashbin/trashbinDelete.feature | 6 +- .../trashbinFilesFolders.feature | 24 +- .../trashbinRestore.feature | 6 - .../previewsAutoAdustedSizing.feature | 2 +- .../previewsExactSizing.feature | 25 - .../getFileProperties.feature | 9 +- 19 files changed, 19 insertions(+), 1280 deletions(-) create mode 100644 tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareExpirationDate.feature delete mode 100644 tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature delete mode 100644 tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature delete mode 100644 tests/acceptance/features/coreApiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature delete mode 100644 tests/acceptance/features/coreApiWebdavPreviews/previewsExactSizing.feature diff --git a/tests/acceptance/features/coreApiCapabilities/capabilities.feature b/tests/acceptance/features/coreApiCapabilities/capabilities.feature index c34004a822..420afe564f 100644 --- a/tests/acceptance/features/coreApiCapabilities/capabilities.feature +++ b/tests/acceptance/features/coreApiCapabilities/capabilities.feature @@ -4,106 +4,6 @@ Feature: capabilities Background: Given using OCS API version "1" - @smokeTest @skipOnOcis - Scenario: Check that the sharing API can be enabled - Given parameter "shareapi_enabled" of app "core" has been set to "no" - And the capabilities setting of "files_sharing" path "api_enabled" has been confirmed to be "" - When the administrator sets parameter "shareapi_enabled" of app "core" to "yes" - Then the capabilities setting of "files_sharing" path "api_enabled" should be "1" - - @smokeTest @skipOnOcis - Scenario: Check that the sharing API can be disabled - Given parameter "shareapi_enabled" of app "core" has been set to "yes" - And the capabilities setting of "files_sharing" path "api_enabled" has been confirmed to be "1" - When the administrator sets parameter "shareapi_enabled" of app "core" to "no" - Then the capabilities setting of "files_sharing" path "api_enabled" should be "" - - @skipOnOcis - Scenario: Check that group sharing can be enabled - Given parameter "shareapi_allow_group_sharing" of app "core" has been set to "no" - And the capabilities setting of "files_sharing" path "group_sharing" has been confirmed to be "" - When the administrator sets parameter "shareapi_allow_group_sharing" of app "core" to "yes" - Then the capabilities setting of "files_sharing" path "group_sharing" should be "1" - - @skipOnOcis - Scenario: Check that group sharing can be disabled - Given parameter "shareapi_allow_group_sharing" of app "core" has been set to "yes" - And the capabilities setting of "files_sharing" path "group_sharing" has been confirmed to be "1" - When the administrator sets parameter "shareapi_allow_group_sharing" of app "core" to "no" - Then the capabilities setting of "files_sharing" path "group_sharing" should be "" - - @smokeTest @skipOnOcis - Scenario: getting default capabilities with admin user - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | core | status@@@edition | %edition% | - | core | status@@@productname | %productname% | - | core | status@@@version | %version% | - | core | status@@@versionstring | %versionstring% | - | files_sharing | api_enabled | 1 | - | files_sharing | default_permissions | 31 | - | files_sharing | search_min_length | 2 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@multiple | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@supports_upload_only | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | public@@@enforced | EMPTY | - | files_sharing | public@@@enforced_for@@@read_only | EMPTY | - | files_sharing | public@@@enforced_for@@@read_write | EMPTY | - | files_sharing | public@@@enforced_for@@@upload_only | EMPTY | - | files_sharing | public@@@enforced_for@@@read_write_delete | EMPTY | - | files_sharing | public@@@expire_date@@@enabled | EMPTY | - | files_sharing | public@@@defaultPublicLinkShareName | Public link | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | share_with_membership_groups_only | EMPTY | - | files_sharing | auto_accept_share | 1 | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files_sharing | user@@@send_mail | EMPTY | - | files | bigfilechunking | 1 | - | files | privateLinks | 1 | - | files | privateLinksDetailsParam | 1 | - - @smokeTest @skipOnOcis - Scenario: getting default capabilities with admin user with new values - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | user@@@expire_date@@@enabled | EMPTY | - | files_sharing | group@@@expire_date@@@enabled | EMPTY | - | files_sharing | providers_capabilities@@@ocinternal@@@user@@@element[0] | shareExpiration | - | files_sharing | providers_capabilities@@@ocinternal@@@group@@@element[0] | shareExpiration | - | files_sharing | providers_capabilities@@@ocinternal@@@link@@@element[0] | shareExpiration | - | files_sharing | providers_capabilities@@@ocinternal@@@link@@@element[1] | passwordProtected | - - @smokeTest @skipOnOcis - Scenario: the default capabilities should include share expiration for all of user, group, link and remote (federated) - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | user@@@expire_date@@@enabled | EMPTY | - | files_sharing | group@@@expire_date@@@enabled | EMPTY | - | files_sharing | remote@@@expire_date@@@enabled | EMPTY | - | files_sharing | providers_capabilities@@@ocinternal@@@user@@@element[0] | shareExpiration | - | files_sharing | providers_capabilities@@@ocinternal@@@group@@@element[0] | shareExpiration | - | files_sharing | providers_capabilities@@@ocinternal@@@link@@@element[0] | shareExpiration | - | files_sharing | providers_capabilities@@@ocFederatedSharing@@@remote@@@element[0] | shareExpiration | - @smokeTest @skipOnOcis Scenario: getting new default capabilities in versions after 10.5.0 with admin user When the administrator retrieves the capabilities using the capabilities API @@ -162,16 +62,6 @@ Feature: capabilities | capability | path_to_element | value | | files_sharing | default_permissions | 31 | - @skipOnOcis - Scenario: default_permissions capability can be changed - Given parameter "shareapi_default_permissions" of app "core" has been set to "7" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | default_permissions | 7 | - @skipOnOcis Scenario: .htaccess is reported as a blacklisted file by default When the administrator retrieves the capabilities using the capabilities API @@ -192,82 +82,6 @@ Feature: capabilities | files | blacklisted_files@@@element[0] | test.txt | | files | blacklisted_files@@@element[1] | .htaccess | - @skipOnOcis - Scenario: user expire date can be enabled - Given parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | user@@@expire_date@@@enabled | 1 | - | files_sharing | user@@@expire_date@@@days | 7 | - | files_sharing | user@@@expire_date@@@enforced | EMPTY | - - @skipOnOcis - Scenario: user expire date can be enforced - Given parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "yes" - And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | user@@@expire_date@@@enabled | 1 | - | files_sharing | user@@@expire_date@@@days | 7 | - | files_sharing | user@@@expire_date@@@enforced | 1 | - - @skipOnOcis - Scenario: user expire date days can be set - Given parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "yes" - And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "14" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | user@@@expire_date@@@enabled | 1 | - | files_sharing | user@@@expire_date@@@days | 14 | - | files_sharing | user@@@expire_date@@@enforced | EMPTY | - - @skipOnOcis - Scenario: group expire date can be enabled - Given parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | group@@@expire_date@@@enabled | 1 | - | files_sharing | group@@@expire_date@@@days | 7 | - | files_sharing | group@@@expire_date@@@enforced | EMPTY | - - @skipOnOcis - Scenario: group expire date can be enforced - Given parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "yes" - And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | group@@@expire_date@@@enabled | 1 | - | files_sharing | group@@@expire_date@@@days | 7 | - | files_sharing | group@@@expire_date@@@enforced | 1 | - - @skipOnOcis - Scenario: group expire date days can be set - Given parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "yes" - And parameter "shareapi_expire_after_n_days_group_share" of app "core" has been set to "14" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | files_sharing | group@@@expire_date@@@enabled | 1 | - | files_sharing | group@@@expire_date@@@days | 14 | - | files_sharing | group@@@expire_date@@@enforced | EMPTY | - #feature added in #31824 released in 10.0.10 @smokeTest @skipOnOcis Scenario: getting capabilities with admin user @@ -297,643 +111,6 @@ Feature: capabilities | capability | path_to_element | value | | async | | EMPTY | - @skipOnOcis - Scenario: Changing public upload - Given parameter "shareapi_allow_public_upload" of app "core" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@multiple | 1 | - | files_sharing | public@@@upload | EMPTY | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Disabling share api - Given parameter "shareapi_enabled" of app "core" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | EMPTY | - | files_sharing | can_share | EMPTY | - | files_sharing | public@@@enabled | EMPTY | - | files_sharing | public@@@multiple | EMPTY | - | files_sharing | public@@@upload | EMPTY | - | files_sharing | resharing | EMPTY | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Disabling public links - Given parameter "shareapi_allow_links" of app "core" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | EMPTY | - | files_sharing | public@@@multiple | EMPTY | - | files_sharing | public@@@upload | EMPTY | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing resharing - Given parameter "shareapi_allow_resharing" of app "core" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | EMPTY | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing federation outgoing - Given parameter "outgoing_server2server_share_enabled" of app "files_sharing" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | EMPTY | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing federation incoming - Given parameter "incoming_server2server_share_enabled" of app "files_sharing" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | EMPTY | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing "password enforced for read-only public link shares" - Given parameter "shareapi_enforce_links_password_read_only" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | public@@@password@@@enforced_for@@@read_only | 1 | - | files_sharing | public@@@password@@@enforced_for@@@read_write | EMPTY | - | files_sharing | public@@@password@@@enforced_for@@@upload_only | EMPTY | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing "password enforced for read-write public link shares" - Given parameter "shareapi_enforce_links_password_read_write" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | public@@@password@@@enforced_for@@@read_only | EMPTY | - | files_sharing | public@@@password@@@enforced_for@@@read_write | 1 | - | files_sharing | public@@@password@@@enforced_for@@@upload_only | EMPTY | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing "password enforced for write-only public link shares" - Given parameter "shareapi_enforce_links_password_write_only" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | public@@@password@@@enforced_for@@@read_only | EMPTY | - | files_sharing | public@@@password@@@enforced_for@@@read_write | EMPTY | - | files_sharing | public@@@password@@@enforced_for@@@upload_only | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing public notifications - Given parameter "shareapi_allow_public_notification" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | 1 | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing public social share - Given parameter "shareapi_allow_social_share" of app "core" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | EMPTY | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing expire date - Given parameter "shareapi_default_expire_date" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | public@@@expire_date@@@enabled | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing expire date enforcing - Given parameter "shareapi_default_expire_date" of app "core" has been set to "yes" - And parameter "shareapi_enforce_expire_date" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | public@@@expire_date@@@enabled | 1 | - | files_sharing | public@@@expire_date@@@enforced | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing group sharing allowed - Given parameter "shareapi_allow_group_sharing" of app "core" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | EMPTY | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing only share with group member - Given parameter "shareapi_only_share_with_group_members" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | 1 | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing only share with membership groups - Given parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | share_with_membership_groups_only | 1 | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing auto accept share - Given parameter "shareapi_auto_accept_share" of app "core" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | share_with_membership_groups_only | EMPTY | - | files_sharing | auto_accept_share | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing allow share dialog user enumeration - Given parameter "shareapi_allow_share_dialog_user_enumeration" of app "core" has been set to "no" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing allow share dialog user enumeration for group members only - Given parameter "shareapi_share_dialog_user_enumeration_group_members" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | 1 | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing allow mail notification - Given parameter "shareapi_allow_mail_notification" of app "core" has been set to "yes" - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files_sharing | user@@@send_mail | 1 | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: Changing exclude groups from sharing - Given parameter "shareapi_exclude_groups" of app "core" has been set to "yes" - And group "group1" has been created - And group "hash#group" has been created - And group "group-3" has been created - And parameter "shareapi_exclude_groups_list" of app "core" has been set to '["group1","hash#group","group-3"]' - When the administrator retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: When in a group that is excluded from sharing, can_share is off - Given parameter "shareapi_exclude_groups" of app "core" has been set to "yes" - And user "Alice" has been created with default attributes and without skeleton files - And group "group1" has been created - And group "hash#group" has been created - And group "group-3" has been created - And group "ordinary-group" has been created - And user "Alice" has been added to group "hash#group" - And parameter "shareapi_exclude_groups_list" of app "core" has been set to '["group1","hash#group","group-3"]' - When user "Alice" retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | EMPTY | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: When not in any group that is excluded from sharing, can_share is on - Given parameter "shareapi_exclude_groups" of app "core" has been set to "yes" - And user "Alice" has been created with default attributes and without skeleton files - And group "group1" has been created - And group "hash#group" has been created - And group "group-3" has been created - And group "ordinary-group" has been created - And user "Alice" has been added to group "ordinary-group" - And parameter "shareapi_exclude_groups_list" of app "core" has been set to '["group1","hash#group","group-3"]' - When user "Alice" retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | 1 | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - - @skipOnOcis - Scenario: When in a group that is excluded from sharing and in another group, can_share is off - Given parameter "shareapi_exclude_groups" of app "core" has been set to "yes" - And user "Alice" has been created with default attributes and without skeleton files - And group "group1" has been created - And group "hash#group" has been created - And group "group-3" has been created - And group "ordinary-group" has been created - And user "Alice" has been added to group "hash#group" - And user "Alice" has been added to group "ordinary-group" - And parameter "shareapi_exclude_groups_list" of app "core" has been set to '["group1","hash#group","group-3"]' - When user "Alice" retrieves the capabilities using the capabilities API - Then the OCS status code should be "100" - And the HTTP status code should be "200" - And the capabilities should contain - | capability | path_to_element | value | - | core | pollinterval | 30000 | - | core | webdav-root | remote.php/webdav | - | files_sharing | api_enabled | 1 | - | files_sharing | can_share | EMPTY | - | files_sharing | public@@@enabled | 1 | - | files_sharing | public@@@upload | 1 | - | files_sharing | public@@@send_mail | EMPTY | - | files_sharing | public@@@social_share | 1 | - | files_sharing | resharing | 1 | - | files_sharing | federation@@@outgoing | 1 | - | files_sharing | federation@@@incoming | 1 | - | files_sharing | group_sharing | 1 | - | files_sharing | share_with_group_members_only | EMPTY | - | files_sharing | user_enumeration@@@enabled | 1 | - | files_sharing | user_enumeration@@@group_members_only | EMPTY | - | files | bigfilechunking | 1 | - @skipOnOcis Scenario: blacklisted_files_regex is reported in capabilities When the administrator retrieves the capabilities using the capabilities API diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareExpirationDate.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareExpirationDate.feature new file mode 100644 index 0000000000..e69de29bb2 diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature index 15739b7042..b2efa2f54a 100644 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature +++ b/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature @@ -12,7 +12,7 @@ Feature: resources shared with the same name are received with unique names | Carol | @smokeTest @issue-ocis-2131 - Scenario Outline: unique target names for incoming shares + Scenario: unique target names for incoming shares Given user "Alice" has created folder "/foo" And user "Brian" has created folder "/foo" When user "Alice" shares folder "/foo" with user "Carol" using the sharing API @@ -23,12 +23,4 @@ Feature: resources shared with the same name are received with unique names And the HTTP status code of responses on all endpoints should be "200" And user "Carol" should see the following elements | Shares/foo/ | - | | - @skipOnOcis - Examples: - | share | - | /Shares/foo (2)/ | - @skipOnOcV10 - Examples: - | share | - | /Shares/foo (1)/ | \ No newline at end of file + | /Shares/foo (1)/ | diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature deleted file mode 100644 index 3b8da45500..0000000000 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature +++ /dev/null @@ -1,83 +0,0 @@ -@api @files_sharing-app-required @issue-ocis-reva-41 @skipOnOcis -Feature: cannot share resources when in a group that is excluded from sharing - - Background: - Given the administrator has set the default folder for received shares to "Shares" - And auto-accept shares has been disabled - And user "Alice" has been created with default attributes and without skeleton files - And user "Brian" has been created with default attributes and without skeleton files - And group "grp1" has been created - And user "Brian" has been added to group "grp1" - - - Scenario Outline: user who is excluded from sharing tries to share a file with another user - Given using OCS API version "" - And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" - And parameter "shareapi_exclude_groups_list" of app "core" has been set to '["grp1"]' - And user "Brian" has uploaded file "filesForUpload/textfile.txt" to "/fileToShare.txt" - When user "Brian" shares file "fileToShare.txt" with user "Alice" using the sharing API - Then the OCS status code should be "403" - And the HTTP status code should be "" - And the sharing API should report to user "Alice" that no shares are in the pending state - And as "Alice" file "Shares/fileToShare.txt" should not exist - And as "Alice" file "fileToShare.txt" should not exist - Examples: - | ocs_api_version | http_status_code | - | 1 | 200 | - | 2 | 403 | - - - Scenario Outline: user who is excluded from sharing tries to share a file with a group - Given using OCS API version "" - And user "Carol" has been created with default attributes and without skeleton files - And group "grp2" has been created - And user "Carol" has been added to group "grp2" - And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" - And parameter "shareapi_exclude_groups_list" of app "core" has been set to '["grp1"]' - And user "Brian" has uploaded file "filesForUpload/textfile.txt" to "/fileToShare.txt" - When user "Brian" shares file "fileToShare.txt" with group "grp2" using the sharing API - Then the OCS status code should be "403" - And the HTTP status code should be "" - And the sharing API should report to user "Carol" that no shares are in the pending state - And as "Carol" file "Shares/fileToShare.txt" should not exist - And as "Carol" file "fileToShare.txt" should not exist - Examples: - | ocs_api_version | http_status_code | - | 1 | 200 | - | 2 | 403 | - - - Scenario Outline: user who is excluded from sharing tries to share a folder with another user - Given using OCS API version "" - And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" - And parameter "shareapi_exclude_groups_list" of app "core" has been set to '["grp1"]' - And user "Brian" has created folder "folderToShare" - When user "Brian" shares folder "folderToShare" with user "Alice" using the sharing API - Then the OCS status code should be "403" - And the HTTP status code should be "" - And the sharing API should report to user "Alice" that no shares are in the pending state - And as "Alice" folder "Shares/folderToShare" should not exist - And as "Alice" folder "folderToShare" should not exist - Examples: - | ocs_api_version | http_status_code | - | 1 | 200 | - | 2 | 403 | - - - Scenario Outline: user who is excluded from sharing tries to share a folder with a group - Given using OCS API version "" - And group "grp0" has been created - And user "Alice" has been added to group "grp0" - And parameter "shareapi_exclude_groups" of app "core" has been set to "yes" - And parameter "shareapi_exclude_groups_list" of app "core" has been set to '["grp0"]' - And user "Alice" has created folder "folderToShare" - When user "Alice" shares folder "folderToShare" with group "grp1" using the sharing API - Then the OCS status code should be "403" - And the HTTP status code should be "" - And the sharing API should report to user "Brian" that no shares are in the pending state - And as "Brian" folder "Shares/folderToShare" should not exist - And as "Brian" folder "folderToShare" should not exist - Examples: - | ocs_api_version | http_status_code | - | 1 | 200 | - | 2 | 403 | diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature index 4a2eb03007..ef445d8668 100644 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature +++ b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature @@ -33,13 +33,6 @@ Feature: share resources where the sharee receives the share in multiple ways | mimetype | text/plain | | storage_id | ANY_VALUE | | share_type | user | - @skipOnOcis - Examples: - | ocs_api_version | ocs_status_code | file_target | - | 1 | 100 | /Shares/textfile0 (2).txt | - | 2 | 200 | /Shares/textfile0 (2).txt | - - @skipOnOcV10 @issue-2131 Examples: | ocs_api_version | ocs_status_code | file_target | | 1 | 100 | /textfile0 (2).txt | @@ -129,13 +122,8 @@ Feature: share resources where the sharee receives the share in multiple ways | permissions | read,update | And the content of file "/Shares/randomfile.txt" for user "Alice" should be "First data" And the content of file "/Shares/randomfile (2).txt" for user "Alice" should be "Second data" - @skipOnOcis - Examples: - | ocs_api_version | file_target_1 | file_target_2 | - | 1 | /Shares/randomfile.txt | /Shares/randomfile (2).txt | - | 2 | /Shares/randomfile.txt | /Shares/randomfile (2).txt | - @skipOnOcV10 @issue-ocis-2131 + @issue-ocis-2131 Examples: | ocs_api_version | file_target_1 | file_target_2 | | 1 | /randomfile.txt | /randomfile (2).txt | @@ -169,13 +157,8 @@ Feature: share resources where the sharee receives the share in multiple ways | permissions | read,share | And as "Alice" folder "/Shares/zzzfolder/Brian" should exist And as "Alice" folder "/Shares/zzzfolder (2)/Carol" should exist - @skipOnOcis - Examples: - | ocs_api_version | file_target_1 | file_target_2 | ocs_status_code | - | 1 | /Shares/zzzfolder | /Shares/zzzfolder (2) | 100 | - | 2 | /Shares/zzzfolder | /Shares/zzzfolder (2) | 200 | - @skipOnOcV10 @issue-ocis-2131 + @issue-ocis-2131 Examples: | ocs_api_version | file_target_1 | file_target_2 | ocs_status_code | | 1 | /zzzfolder | /zzzfolder (2) | 100 | diff --git a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature b/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature deleted file mode 100644 index 0ddcd246af..0000000000 --- a/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature +++ /dev/null @@ -1,127 +0,0 @@ -@api @files_sharing-app-required @issue-ocis-1328 -Feature: cannot share resources outside the group when share with membership groups is enabled - - Background: - Given the administrator has set the default folder for received shares to "Shares" - And auto-accept shares has been disabled - And user "Alice" has been created with default attributes and without skeleton files - - @issue-ocis-1328 @skipOnOcis - Scenario Outline: sharer should not be able to share a folder to a group which he/she is not member of when share with only member group is enabled - Given using OCS API version "" - And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - And user "Brian" has been created with default attributes and without skeleton files - And group "grp0" has been created - And group "grp1" has been created - And user "Alice" has been added to group "grp0" - And user "Brian" has been added to group "grp1" - And user "Alice" has created folder "PARENT" - When user "Alice" shares folder "/PARENT" with group "grp1" using the sharing API - Then the OCS status code should be "" - And the HTTP status code should be "" - And as "Brian" folder "/PARENT" should not exist - And as "Brian" folder "/Shares/PARENT" should not exist - And the sharing API should report to user "Brian" that no shares are in the pending state - Examples: - | ocs_api_version | ocs_status_code | http_status_code | - | 1 | 403 | 200 | - | 2 | 403 | 403 | - - - Scenario Outline: sharer should be able to share a folder to a user who is not member of sharer group when share with only member group is enabled - Given using OCS API version "" - And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - And user "Brian" has been created with default attributes and without skeleton files - And group "grp0" has been created - And user "Alice" has been added to group "grp0" - And user "Alice" has created folder "PARENT" - When user "Alice" shares folder "/PARENT" with user "Brian" using the sharing API - And user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API - Then the OCS status code of responses on all endpoints should be "" - And the HTTP status code of responses on all endpoints should be "200" - And as "Brian" folder "/Shares/PARENT" should exist - But as "Brian" folder "/PARENT" should not exist - Examples: - | ocs_api_version | ocs_status_code | - | 1 | 100 | - | 2 | 200 | - - - Scenario Outline: sharer should be able to share a folder to a group which he/she is member of when share with only member group is enabled - Given using OCS API version "" - And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - And user "Brian" has been created with default attributes and without skeleton files - And group "grp0" has been created - And user "Alice" has been added to group "grp0" - And user "Brian" has been added to group "grp0" - And user "Alice" has created folder "PARENT" - When user "Alice" shares folder "/PARENT" with group "grp0" using the sharing API - And user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API - Then the OCS status code of responses on all endpoints should be "" - And the HTTP status code of responses on all endpoints should be "200" - And as "Brian" folder "/Shares/PARENT" should exist - But as "Brian" folder "/PARENT" should not exist - Examples: - | ocs_api_version | ocs_status_code | - | 1 | 100 | - | 2 | 200 | - - @issue-ocis-1328 @skipOnOcis - Scenario Outline: sharer should not be able to share a file to a group which he/she is not member of when share with only member group is enabled - Given using OCS API version "" - And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - And user "Brian" has been created with default attributes and without skeleton files - And group "grp0" has been created - And group "grp1" has been created - And user "Alice" has been added to group "grp0" - And user "Brian" has been added to group "grp1" - And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" - When user "Alice" shares file "/textfile0.txt" with group "grp1" using the sharing API - Then the OCS status code should be "" - And the HTTP status code should be "" - And as "Brian" file "/textfile0.txt" should not exist - And as "Brian" file "/Shares/textfile0.txt" should not exist - And the sharing API should report to user "Brian" that no shares are in the pending state - Examples: - | ocs_api_version | ocs_status_code | http_status_code | - | 1 | 403 | 200 | - | 2 | 403 | 403 | - - - Scenario Outline: sharer should be able to share a file to a group which he/she is member of when share with only member group is enabled - Given using OCS API version "" - And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - And user "Brian" has been created with default attributes and without skeleton files - And group "grp0" has been created - And user "Alice" has been added to group "grp0" - And user "Brian" has been added to group "grp0" - And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" - When user "Alice" shares folder "/textfile0.txt" with group "grp0" using the sharing API - And user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API - Then the OCS status code of responses on all endpoints should be "" - And the HTTP status code of responses on all endpoints should be "200" - And as "Brian" file "/Shares/textfile0.txt" should exist - But as "Brian" file "/textfile0.txt" should not exist - Examples: - | ocs_api_version | ocs_status_code | - | 1 | 100 | - | 2 | 200 | - - - Scenario Outline: sharer should be able to share a file to a user who is not a member of sharer group when share with only member group is enabled - Given using OCS API version "" - And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - And user "Brian" has been created with default attributes and without skeleton files - And group "grp0" has been created - And user "Alice" has been added to group "grp0" - And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" - When user "Alice" shares folder "/textfile0.txt" with user "Brian" using the sharing API - And user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API - Then the OCS status code of responses on all endpoints should be "" - And the HTTP status code of responses on all endpoints should be "200" - And as "Brian" file "/Shares/textfile0.txt" should exist - But as "Brian" file "/textfile0.txt" should not exist - Examples: - | ocs_api_version | ocs_status_code | - | 1 | 100 | - | 2 | 200 | diff --git a/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature b/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature index a7931f60b7..abacfbc6f1 100644 --- a/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature +++ b/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature @@ -274,7 +274,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - + Scenario Outline: sharing again an own file while belonging to a group Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -326,7 +326,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - + Scenario Outline: user shares a file with file name longer than 64 chars to another user Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -342,7 +342,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - + Scenario Outline: user shares a file with file name longer than 64 chars to a group Given using OCS API version "" And group "grp1" has been created @@ -360,7 +360,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - + Scenario Outline: user shares a folder with folder name longer than 64 chars to another user Given using OCS API version "" And user "Brian" has been created with default attributes and without skeleton files @@ -377,7 +377,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - + Scenario Outline: user shares a folder with folder name longer than 64 chars to a group Given using OCS API version "" And group "grp1" has been created @@ -523,11 +523,6 @@ Feature: sharing And file "/textfile0.txt" should not be included as path in the response And as "Brian" file "/Shares/textfile0.txt" should not exist And as "Carol" file "/Shares/textfile0.txt" should not exist - @skipOnOcis - Examples: - | ocs_api_version | ocs_status_code | path | - | 1 | 100 | /Shares/textfile0.txt | - | 2 | 200 | /Shares/textfile0.txt | @skipOnOcV10 @issue-ocis-2441 Examples: | ocs_api_version | ocs_status_code | path | diff --git a/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature b/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature index a28b21edd2..0d195ba9af 100644 --- a/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature +++ b/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature @@ -108,14 +108,9 @@ Feature: sharing And as user "Brian" folder "/merge-test-inside-twogroups-perms" should contain a property "oc:permissions" with value "" or with value "" And as "Brian" folder "/Shares/merge-test-inside-twogroups-perms" should not exist And as "Brian" folder "/Shares/merge-test-inside-twogroups-perms (2)" should not exist - @skipOnOcV10 Examples: | expected_permission_1 | expected_permission_2 | | RDNVCKZ | RMDNVCKZ | - @skipOnOcis - Examples: - | expected_permission_1 | expected_permission_2 | - | RDNVCK | RMDNVCK | Scenario: Merging shares for recipient when shared from outside with group then user and recipient renames in between diff --git a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature index 0018e5b277..7a6c9859f4 100644 --- a/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature +++ b/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature @@ -106,8 +106,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @toFixOnOCIS @issue-ocis-reva-357 @issue-ocis-reva-301 @issue-ocis-reva-302 - #after fixing all the issues merge this scenario with the one below + @smokeTest @issue-ocis-reva-357 @issue-ocis-reva-301 @issue-ocis-reva-302 Scenario Outline: getting share info of a share Given using OCS API version "" And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt" @@ -138,38 +137,6 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @toFixOnOCIS @issue-ocis-reva-357 @issue-ocis-reva-301 @issue-ocis-reva-302 - #after fixing all the issues merge this scenario with the one above - Scenario Outline: getting share info of a share (Bug demonstration for ocis) - Given using OCS API version "" - And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt" - And user "Alice" has shared file "file_to_share.txt" with user "Brian" - And user "Brian" has accepted share "/file_to_share.txt" offered by user "Alice" - When user "Alice" gets the info of the last share using the sharing API - Then the OCS status code should be "" - And the HTTP status code should be "200" - And the fields of the last response to user "Alice" sharing with user "Brian" should include - | id | A_STRING | - | item_type | file | - | item_source | A_STRING | - | share_type | user | - | share_with | %username% | - | file_source | A_STRING | - | file_target | /Shares/file_to_share.txt | - | path | /file_to_share.txt | - | permissions | share,read,update | - | stime | A_NUMBER | - | storage | A_STRING | - | mail_send | 0 | - | uid_owner | %username% | -# | share_with_displayname | %displayname% | -# | displayname_owner | %displayname% | -# | mimetype | text/plain | - Examples: - | ocs_api_version | ocs_status_code | - | 1 | 100 | - | 2 | 200 | - @issue-ocis-reva-374 Scenario Outline: Get a share with a user that didn't receive the share Given using OCS API version "" diff --git a/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature index 9eba9b1d4e..299961af9a 100644 --- a/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature @@ -119,39 +119,6 @@ Feature: update a public link share | 1 | 100 | | 2 | 200 | - @issue-ocis-reva-336 - Scenario Outline: Creating a new public link share, updating its expiration date and getting its info (ocis Bug demonstration) - Given using OCS API version "" - And user "Alice" has created folder "FOLDER" - And user "Alice" has created a public link share with settings - | path | FOLDER | - And user "Alice" has updated the last public link share with - | expireDate | 2040-01-01T23:59:59+0100 | - When user "Alice" gets the info of the last public link share using the sharing API - Then the OCS status code should be "" - And the HTTP status code should be "200" - And the fields of the last response to user "Alice" should include - | id | A_STRING | - | item_type | folder | - | item_source | A_STRING | - | share_type | public_link | - | file_source | A_STRING | - | file_target | /FOLDER | - | permissions | read | - | stime | A_NUMBER | - | expiration | 2040-01-01 | - | token | A_TOKEN | - | storage | A_STRING | - | mail_send | 0 | - | uid_owner | %username% | - | displayname_owner | %displayname% | - | url | AN_URL | - | mimetype | httpd/unix-directory | - Examples: - | ocs_api_version | ocs_status_code | - | 1 | 100 | - | 2 | 200 | - @issue-ocis-reva-336 Scenario Outline: Creating a new public link share, updating its password and getting its info Given using OCS API version "" @@ -305,6 +272,7 @@ Feature: update a public link share | 1 | 200 | | 2 | 404 | + Scenario Outline: Adding public upload to a shared folder as recipient is allowed with permissions using the public API Given the administrator has set the default folder for received shares to "Shares" And auto-accept shares has been disabled diff --git a/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature b/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature index 1749f5f2b8..54e43bc2e3 100644 --- a/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature +++ b/tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature @@ -10,23 +10,6 @@ Feature: resharing can be disabled | Brian | And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" - @smokeTest @skipOnOcis - Scenario Outline: resharing a file is not allowed when allow resharing has been disabled - Given using 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 "share,update,read" - And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice" - And parameter "shareapi_allow_resharing" of app "core" has been set to "no" - When user "Brian" shares file "/Shares/textfile0.txt" with user "Carol" with permissions "share,update,read" using the sharing API - Then the OCS status code should be "404" - And the HTTP status code should be "" - And as "Carol" file "/Shares/textfile0.txt" should not exist - And the sharing API should report to user "Carol" that no shares are in the pending state - Examples: - | ocs_api_version | http_status_code | - | 1 | 200 | - | 2 | 404 | - Scenario Outline: ordinary sharing is allowed when allow resharing has been disabled Given using OCS API version "" diff --git a/tests/acceptance/features/coreApiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature b/tests/acceptance/features/coreApiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature deleted file mode 100644 index 0e4b2410fa..0000000000 --- a/tests/acceptance/features/coreApiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature +++ /dev/null @@ -1,48 +0,0 @@ -@api @files_sharing-app-required @issue-ocis-1289 @issue-ocis-reva-194 @issue-ocis-1328 @skipOnOcis -Feature: resharing a resource with an expiration date - - Background: - Given the administrator has set the default folder for received shares to "Shares" - And auto-accept shares has been disabled - And these users have been created with default attributes and without skeleton files: - | username | - | Alice | - | Brian | - - - Scenario Outline: User should not be able to re-share a folder to a group which he/she is not member of when share with only member group is enabled - Given using OCS API version "" - And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - And user "Carol" has been created with default attributes and without skeleton files - And group "grp1" has been created - And user "Carol" has been added to group "grp1" - And user "Alice" has created folder "/PARENT" - And user "Alice" has shared folder "/PARENT" with user "Brian" - And user "Brian" has accepted share "/PARENT" offered by user "Alice" - When user "Brian" shares folder "/Shares/PARENT" with group "grp1" using the sharing API - Then the OCS status code should be "" - And the HTTP status code should be "" - And as "Carol" folder "/Shares/PARENT" should not exist - Examples: - | ocs_api_version | ocs_status_code | http_status_code | - | 1 | 403 | 200 | - | 2 | 403 | 403 | - - - Scenario Outline: User should not be able to re-share a file to a group which he/she is not member of when share with only member group is enabled - Given using OCS API version "" - And parameter "shareapi_only_share_with_membership_groups" of app "core" has been set to "yes" - And user "Carol" has been created with default attributes and without skeleton files - And group "grp1" has been created - And user "Carol" has been added to group "grp1" - And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" - And user "Alice" has shared file "/textfile0.txt" with user "Brian" - And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice" - When user "Brian" shares folder "/Shares/textfile0.txt" with group "grp1" using the sharing API - Then the OCS status code should be "" - And the HTTP status code should be "" - And as "Carol" folder "/Shares/textfile0.txt" should not exist - Examples: - | ocs_api_version | ocs_status_code | http_status_code | - | 1 | 403 | 200 | - | 2 | 403 | 403 | diff --git a/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature b/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature index a0e49f8f5a..37976edc4d 100644 --- a/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature +++ b/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature @@ -190,12 +190,7 @@ Feature: sharing | mimetype | httpd/unix-directory | And as "Alice" folder "/Alice-folder/folder2" should not exist And as "Carol" folder "/Carol-folder/folder2" should exist - @skipOnOcis - Examples: - | path | - | /Shares/Carol-folder | - - @skipOnOcV10 @issue-2442 + @issue-2442 Examples: | path | | /Carol-folder | diff --git a/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature b/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature index ae114b9e86..5d12f53d4d 100644 --- a/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature +++ b/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature @@ -98,11 +98,7 @@ Feature: files and folders can be deleted from the trashbin And as "Alice" the file with original path "/textfile0.txt" should exist in the trashbin And as "Alice" the file with original path "/PARENT/parent.txt" should exist in the trashbin And as "Alice" the file with original path "/PARENT/CHILD/child.txt" should exist in the trashbin - @skipOnOcis - Examples: - | dav-path | status-code | - | new | 401 | - @skipOnOcV10 @personalSpace + @personalSpace Examples: | dav-path | status-code | | new | 404 | diff --git a/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature b/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature index c7e9dec76a..314d05acf3 100644 --- a/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature +++ b/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature @@ -188,11 +188,7 @@ Feature: files and folders exist in the trashbin after being deleted And the last webdav response should not contain the following elements | path | user | | textfile1.txt | testtrashbin100 | - @skipOnOcis - Examples: - | dav-path | status-code | - | new | 401 | - @skipOnOcV10 @personalSpace + @personalSpace Examples: | dav-path | status-code | | new | 404 | @@ -213,11 +209,7 @@ Feature: files and folders exist in the trashbin after being deleted | path | user | | textfile0.txt | testtrashbin101 | | textfile2.txt | testtrashbin101 | - @skipOnOcis - Examples: - | dav-path | status-code | - | new | 401 | - @skipOnOcV10 @personalSpace + @personalSpace Examples: | dav-path | status-code | | new | 404 | @@ -243,11 +235,7 @@ Feature: files and folders exist in the trashbin after being deleted | textfile0.txt | testtrashbin102 | | textfile2.txt | testtrashbin102 | | textfile3.txt | testtrashbin102 | - @skipOnOcis - Examples: - | dav-path | status-code | - | new | 401 | - @skipOnOcV10 @personalSpace + @personalSpace Examples: | dav-path | status-code | | new | 404 | @@ -260,11 +248,7 @@ Feature: files and folders exist in the trashbin after being deleted And user "testtrashbinempty" has uploaded file "filesForUpload/textfile.txt" to "/textfile1.txt" When user "Alice" tries to list the trashbin content for user "testtrashbinempty" Then the HTTP status code should be "" - @skipOnOcis - Examples: - | dav-path | status-code | - | new | 401 | - @skipOnOcV10 @personalSpace + @personalSpace Examples: | dav-path | status-code | | new | 404 | diff --git a/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature b/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature index f516c5c13f..05a1b50c9c 100644 --- a/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature +++ b/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature @@ -177,12 +177,6 @@ Feature: Restore deleted files/folders And as "Alice" the folder with original path "/textfile0.txt" should exist in the trashbin And user "Alice" should not see the following elements | /textfile0.txt | - @skipOnOcis - Examples: - | dav-path | status-code | - | old | 401 | - | new | 401 | - @skipOnOcV10 Examples: | dav-path | status-code | | old | 404 | diff --git a/tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature b/tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature index 1246c1e91d..422a578d12 100644 --- a/tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature +++ b/tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature @@ -10,7 +10,7 @@ Feature: sizing of previews of files downloaded through the webdav API Background: Given user "Alice" has been created with default attributes and without skeleton files - @skipOnOcV10 + Scenario Outline: download different sizes of previews of file Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt" When user "Alice" downloads the preview of "/parent.txt" with width and height using the WebDAV API diff --git a/tests/acceptance/features/coreApiWebdavPreviews/previewsExactSizing.feature b/tests/acceptance/features/coreApiWebdavPreviews/previewsExactSizing.feature deleted file mode 100644 index f113a170b7..0000000000 --- a/tests/acceptance/features/coreApiWebdavPreviews/previewsExactSizing.feature +++ /dev/null @@ -1,25 +0,0 @@ -@api @preview-extension-required -Feature: sizing of previews of files downloaded through the webdav API - As a user - I want previews to be the exact requested size even when I ask for an unusual preview size combination - So that the previews always have the exact size that I want as a user/client. - - This is optional behavior of an implementation. oC10 happens like this, - but OCIS does an auto-fix of the aspect ratio. - - Background: - Given user "Alice" has been created with default attributes and without skeleton files - - @skipOnOcis - Scenario Outline: download different sizes of previews of file - Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt" - When user "Alice" downloads the preview of "/parent.txt" with width and height using the WebDAV API - Then the HTTP status code should be "200" - And the downloaded image should be pixels wide and pixels high - Examples: - | width | height | - | 1 | 1 | - | 32 | 32 | - | 1024 | 1024 | - | 1 | 1024 | - | 1024 | 1 | diff --git a/tests/acceptance/features/coreApiWebdavProperties2/getFileProperties.feature b/tests/acceptance/features/coreApiWebdavProperties2/getFileProperties.feature index 9466c5d839..1e991ff635 100644 --- a/tests/acceptance/features/coreApiWebdavProperties2/getFileProperties.feature +++ b/tests/acceptance/features/coreApiWebdavProperties2/getFileProperties.feature @@ -306,19 +306,12 @@ Feature: get file properties And the value of the item "/d:error/s:message" in the response about user "Alice" should be "" or "" And the value of the item "/d:error/s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound" - @skipOnOcV10 Examples: | url | message1 | message2 | | /remote.php/dav/files/does-not-exist | Resource not found | Resource not found | | /remote.php/dav/does-not-exist | File not found in root | | - @skipOnOcis - Examples: - | url | message1 | message2 | - | /remote.php/dav/files/does-not-exist | Principal with name does-not-exist not found | | - | /remote.php/dav/does-not-exist | File not found: does-not-exist in 'root' | | - - @skipOnOcV10 @personalSpace + @personalSpace Examples: | url | message1 | message2 | | /remote.php/dav/spaces/%spaceid%/does-not-exist | Resource not found | |