mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-05-24 16:41:35 -04:00
Code Issues Packages Projects Releases Wiki Activity

Removed scenarios tagged with @skipOnOcis tag

Browse Source
This commit is contained in:
Prarup Gurung
2023-02-07 11:38:44 +05:45
parent 7ec0e3c65c
commit 8b6df0d729
19 changed files with 19 additions and 1280 deletions
Download Patch File Download Diff File Expand all files Collapse all files

823
tests/acceptance/features/coreApiCapabilities/capabilities.feature
View File

@@ -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

0
tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareExpirationDate.feature Normal file
View File

12
tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature
View File

@@ -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/ |
| <share> |
@skipOnOcis
Examples:
| share |
| /Shares/foo (2)/ |
@skipOnOcV10
Examples:
| share |
| /Shares/foo (1)/ |
| /Shares/foo (1)/ |

83
tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareWhenExcludedFromSharing.feature
View File

@@ -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 "<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 "<http_status_code>"
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 "<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 "<http_status_code>"
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 "<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 "<http_status_code>"
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 "<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 "<http_status_code>"
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 |

21
tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature
View File

@@ -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 |

127
tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature
View File

@@ -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 "<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 "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
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 "<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 "<ocs_status_code>"
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 "<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 "<ocs_status_code>"
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 "<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 "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
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 "<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 "<ocs_status_code>"
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 "<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 "<ocs_status_code>"
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 |

15
tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature
View File

@@ -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 "<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 "<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 "<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 "<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 "<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 |

5
tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature
View File

@@ -108,14 +108,9 @@ Feature: sharing
And as user "Brian" folder "/merge-test-inside-twogroups-perms" should contain a property "oc:permissions" with value "<expected_permission_1>" or with value "<expected_permission_2>"
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

35
tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature
View File

@@ -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 "<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 "<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 "<ocs_status_code>"
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 "<ocs_api_version>"

34
tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature
View File

@@ -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 "<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 "<ocs_status_code>"
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 "<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

17
tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature
View File

@@ -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 "<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 "<http_status_code>"
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 "<ocs_api_version>"

48
tests/acceptance/features/coreApiShareReshareToShares2/reShareWhenShareWithOnlyMembershipGroups.feature
View File

@@ -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 "<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 "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
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 "<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 "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
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 |

7
tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature
View File

@@ -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 |

6
tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature
View File

@@ -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 |

24
tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature
View File

@@ -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 "<status-code>"
@skipOnOcis
Examples:
| dav-path | status-code |
| new | 401 |
@skipOnOcV10 @personalSpace
@personalSpace
Examples:
| dav-path | status-code |
| new | 404 |

6
tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature
View File

@@ -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 |

2
tests/acceptance/features/coreApiWebdavPreviews/previewsAutoAdustedSizing.feature
View File

@@ -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 <request_width> and height <request_height> using the WebDAV API

25
tests/acceptance/features/coreApiWebdavPreviews/previewsExactSizing.feature
View File

@@ -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 <width> and height <height> using the WebDAV API
Then the HTTP status code should be "200"
And the downloaded image should be <width> pixels wide and <height> pixels high
Examples:
| width | height |
| 1 | 1 |
| 32 | 32 |
| 1024 | 1024 |
| 1 | 1024 |
| 1024 | 1 |

9
tests/acceptance/features/coreApiWebdavProperties2/getFileProperties.feature
View File

@@ -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 "<message1>" or "<message2>"
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 | |