From 219fbce7de4b63bd2ebea5c4dd4eb606be8b9ea3 Mon Sep 17 00:00:00 2001 From: Roman Perekhod Date: Mon, 4 Dec 2023 13:04:25 +0100 Subject: [PATCH] the tests were modified --- .../changingPublicLinkShare.feature | 4 ++-- .../updatePublicLinkShare.feature | 19 ------------------- 2 files changed, 2 insertions(+), 21 deletions(-) diff --git a/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature index 74296b42abd..30c5c447011 100644 --- a/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink1/changingPublicLinkShare.feature @@ -160,8 +160,8 @@ Feature: changing a public link share | path | /PARENT | | password | | Then the HTTP status code should be "200" - And the OCS status code should be "400" - And the OCS status message should be "missing required password" + And the OCS status code should be "104" + And the OCS status message should be "user is not allowed to delete the password from the public link" Scenario: administrator removes password of a read-only public link diff --git a/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature b/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature index c68f55000a1..07970716cbf 100644 --- a/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature +++ b/tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature @@ -101,25 +101,6 @@ Feature: update a public link share | 2 | 200 | - Scenario Outline: creating a new public link share with password and removing (updating) it to make the resources accessible without password using public API - Given using OCS API version "" - And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt" - And user "Alice" has created a public link share with settings - | path | randomfile.txt | - | password | %public% | - When user "Alice" updates the last public link share using the sharing API with - #removing password is basically making password empty - | password | %remove% | - Then the OCS status code should be "" - And the HTTP status code should be "200" - And the public should be able to download the last publicly shared file using the old public WebDAV API without a password and the content should be "Random data" - And the public should be able to download the last publicly shared file using the new public WebDAV API without a password and the content should be "Random data" - 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"