sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Capabilities related scenarios are added in expected failure

Browse Source
This commit is contained in:
Prarup Gurung
2023-02-21 15:15:45 +05:45
parent 5a46a19f99
commit 0076c93dc6
5 changed files with 19 additions and 129 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/coreApiCapabilities/capabilities.feature
+4 -75
View File
@@ -1,32 +1,10 @@
@api @files_sharing-app-required @issue-ocis-reva-41
@api @files_sharing-app-required
Feature: capabilities
Background:
Given using OCS API version "1"
@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
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 | favorites | 1 |
| files | file_locking_support | 1 |
| files | file_locking_enable_file_action | EMPTY |
@smokeTest @skipOnOcis
Scenario: lock file action can be enabled
Given parameter "enable_lock_file_action" of app "files" 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 | file_locking_support | 1 |
| files | file_locking_enable_file_action | 1 |
@smokeTest @skipOnOcis
@smokeTest @issue-ocis-1285
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"
@@ -53,7 +31,7 @@ Feature: capabilities
| capability | path_to_element | value |
| files | versioning | 1 |
@skipOnOcis
@issue-ocis-1285
Scenario: getting default_permissions capability with admin user
When the administrator retrieves the capabilities using the capabilities API
Then the OCS status code should be "100"
@@ -62,7 +40,7 @@ Feature: capabilities
| capability | path_to_element | value |
| files_sharing | default_permissions | 31 |
@skipOnOcis
@issue-ocis-1285
Scenario: .htaccess is reported as a blacklisted file by default
When the administrator retrieves the capabilities using the capabilities API
Then the OCS status code should be "100"
@@ -71,55 +49,6 @@ Feature: capabilities
| capability | path_to_element | value |
| files | blacklisted_files@@@element[0] | .htaccess |
@skipOnOcis
Scenario: multiple files can be reported as blacklisted
Given the administrator has updated system config key "blacklisted_files" with value '["test.txt",".htaccess"]' and type "json"
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 | blacklisted_files@@@element[0] | test.txt |
| files | blacklisted_files@@@element[1] | .htaccess |
#feature added in #31824 released in 10.0.10
@smokeTest @skipOnOcis
Scenario: getting 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 |
| files_sharing | can_share | 1 |
#feature added in #32414 released in 10.0.10
@skipOnOcis
Scenario: getting async capabilities when async operations are enabled
Given the administrator has enabled async operations
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 |
| async | | 1.0 |
Scenario: getting async capabilities when async operations are disabled
Given the administrator has disabled async operations
When the administrator retrieves the capabilities using the capabilities API
Then the capabilities should contain
| capability | path_to_element | value |
| async | | EMPTY |
@skipOnOcis
Scenario: blacklisted_files_regex is reported in capabilities
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 | blacklisted_files_regex | \.(part\|filepart)$ |
@smokeTest
Scenario: getting default capabilities with admin user
When the administrator retrieves the capabilities using the capabilities API
tests/acceptance/features/coreApiTranslation/translation.feature
-36
View File
@@ -1,36 +0,0 @@
@api @skipOnLDAP @skipOnOcis
Feature: translate messages in api response to preferred language
As a user
I want response messages to be translated in preferred language
So that I can see and understand the response messages in my language
Scenario Outline: user tries to get non existing share and uses some preferred language
Given these users have been created with default attributes and without skeleton files:
| username |
| Alice |
| Brian |
| Carol |
And using <dav_version> DAV path
And user "Brian" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
And user "Brian" has shared file "textfile0.txt" with user "Carol"
When user "Alice" gets the info of the last share in language "<language>" using the sharing API
Then the OCS status code should be "404"
And the OCS status message should be "Wrong share ID, share doesn't exist" in language "<language>"
Examples:
| dav_version | language |
| old | de-DE |
| old | es-ES |
| old | zh-CN |
| old | fr-FR |
| new | de-DE |
| new | es-ES |
| new | zh-CN |
| new | fr-FR |
@skipOnOcV10 @personalSpace
Examples:
| dav_version | language |
| spaces | de-DE |
| spaces | es-ES |
| spaces | zh-CN |
| spaces | fr-FR |