diff --git a/tests/acceptance/features/apiCapabilities/capabilities.feature b/tests/acceptance/features/apiCapabilities/capabilities.feature index 68928c51978d..b6c3c86b65bc 100644 --- a/tests/acceptance/features/apiCapabilities/capabilities.feature +++ b/tests/acceptance/features/apiCapabilities/capabilities.feature @@ -135,7 +135,7 @@ Feature: capabilities | capability | path_to_element | value | | files_sharing | user@@@profile_picture | 1 | - @files_trashbin-app-required @skipOnReva + @files_trashbin-app-required Scenario: getting trashbin app capability with admin user When the administrator retrieves the capabilities using the capabilities API Then the OCS status code should be "100" @@ -144,7 +144,7 @@ Feature: capabilities | capability | path_to_element | value | | files | undelete | 1 | - @files_versions-app-required @skipOnReva + @files_versions-app-required Scenario: getting versions app capability with admin user When the administrator retrieves the capabilities using the capabilities API Then the OCS status code should be "100" diff --git a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature index f67f5410a425..6e5ba16a470c 100644 --- a/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature +++ b/tests/acceptance/features/apiShareManagementBasicToShares/createShareToSharesFolder.feature @@ -235,7 +235,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @skipOnReva # reva doesn't have a pre-created admin user + @smokeTest Scenario Outline: User included in multiple groups receives a share from the admin Given using OCS API version "" And group "grp1" has been created diff --git a/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature b/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature index 19d7711c2c1e..092945017c3c 100644 --- a/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature +++ b/tests/acceptance/features/apiShareOperationsToShares1/gettingShares.feature @@ -106,8 +106,7 @@ Feature: sharing | 1 | 100 | | 2 | 200 | - @smokeTest @toFixOnOCIS - #after fixing all the issues merge this scenario with the one below + @smokeTest 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 - #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 | - 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/apiSharePublicLink3/updatePublicLinkShare.feature b/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature index bd3a45b223b2..0f8afc91cb4d 100644 --- a/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature +++ b/tests/acceptance/features/apiSharePublicLink3/updatePublicLinkShare.feature @@ -162,39 +162,6 @@ Feature: update a public link share | 2 | 200 | - 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 | +3 days | - 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 | +3 days | - | 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 | - - Scenario Outline: Creating a new public link share, updating its password and getting its info Given using OCS API version "" And user "Alice" has created folder "FOLDER" diff --git a/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature b/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature index 55e4b250b0a1..4bb3ddaf8d37 100644 --- a/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature +++ b/tests/acceptance/features/apiShareUpdateToShares/updateShare.feature @@ -158,7 +158,7 @@ Feature: sharing | 1 | 200 | create,delete | | 2 | 400 | create,delete | - @skipOnFilesClassifier @issue-files-classifier-291 @toFixOnOCIS + @skipOnFilesClassifier @issue-files-classifier-291 Scenario Outline: Share ownership change after moving a shared file outside of an outer share Given these users have been created with default attributes and without skeleton files: | username | @@ -228,7 +228,7 @@ Feature: sharing | path | | /Shares/Carol-folder | - @toFixOnOCIS @toFixOnOcV10 + @toFixOnOcV10 #after fixing all the issues merge this scenario with the one below Scenario Outline: API responds with a full set of parameters when owner changes the permission of a share Given using OCS API version ""