mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-03-03 11:28:38 -06:00
Code Issues Packages Projects Releases Wiki Activity

skip tests moving between shares jail

Browse Source
This commit is contained in:
Viktor Scharf
2023-10-20 16:12:51 +02:00
parent 67365bd7a2
commit 4e27005e68
6 changed files with 39 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -261,36 +261,36 @@ Feature: share resources where the sharee receives the share in multiple ways
And user "Alice" should not be able to delete folder "/Shares/child1/child2"
# Scenario: sharing parent folder to user with all permissions and its child folder to group with read permission then check reshare operation
# Given group "grp1" has been created
# And user "Carol" has been created with default attributes and without skeleton files
# And user "Carol" has created the following folders
# | path |
# | /parent |
# | /parent/child1 |
# | /parent/child1/child2 |
# And user "Alice" has been added to group "grp1"
# And user "Brian" has been added to group "grp1"
# And user "Carol" has created a share with settings
# | path | /parent |
# | shareType | user |
# | shareWith | Brian |
# | permissions | all |
# And user "Carol" has created a share with settings
# | path | /parent/child1 |
# | shareType | group |
# | shareWith | grp1 |
# | permissions | read |
# When user "Brian" creates a share using the sharing API with settings
# | path | /Shares/parent |
# | shareType | user |
# | shareWith | Alice |
# | permissions | read |
# Then the HTTP status code should be "200"
# And the OCS status code should be "100"
# And as "Brian" folder "/Shares/child1" should exist
# And as "Alice" folder "/Shares/child1" should exist
# And as "Alice" folder "/Shares/parent" should exist
Scenario: sharing parent folder to user with all permissions and its child folder to group with read permission then check reshare operation
Given group "grp1" has been created
And user "Carol" has been created with default attributes and without skeleton files
And user "Carol" has created the following folders
| path |
| /parent |
| /parent/child1 |
| /parent/child1/child2 |
And user "Alice" has been added to group "grp1"
And user "Brian" has been added to group "grp1"
And user "Carol" has created a share with settings
| path | /parent |
| shareType | user |
| shareWith | Brian |
| permissions | all |
And user "Carol" has created a share with settings
| path | /parent/child1 |
| shareType | group |
| shareWith | grp1 |
| permissions | read |
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/parent |
| shareType | user |
| shareWith | Alice |
| permissions | read |
Then the HTTP status code should be "200"
And the OCS status code should be "100"
And as "Brian" folder "/Shares/child1" should exist
And as "Alice" folder "/Shares/child1" should exist
And as "Alice" folder "/Shares/parent" should exist
Scenario: sharing parent folder to group with read permission and its child folder to user with all permissions then check create operation
@@ -458,8 +458,8 @@ Feature: share resources where the sharee receives the share in multiple ways
And as "Brian" folder "Shares/sharedParent" should exist
And as "Brian" file "Shares/sharedParent/child/lorem.txt" should exist
Scenario Outline: share receiver renames a group share and receives same resource through user share with additional permissions
@skip @issue-7555
Scenario Outline: share receiver renames a group share and receives same resource through user share with additional permissions
Given using OCS API version "<ocs_api_version>"
And group "grp" has been created
And user "Brian" has been added to group "grp"

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

@@ -469,7 +469,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-2146 @issue-764
@issue-2146 @issue-764 @issue-7555
Scenario: share a file by multiple channels and download from sub-folder and direct file share
Given these users have been created with default attributes and without skeleton files:
| username |

2
tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature
View File

@@ -11,7 +11,7 @@ Feature: sharing
| Brian |
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
@issue-7555
Scenario Outline: delete all group shares
Given using OCS API version "<ocs_api_version>"
And group "grp1" has been created

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

@@ -28,7 +28,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-1289
@issue-1289 @issue-7555
Scenario Outline: keep group permissions in sync when the share is renamed by the receiver and then the permissions are updated by sharer
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files

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

@@ -7,7 +7,7 @@ Feature: using trashbin together with sharing
Given user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file with content "file to delete" to "/textfile0.txt"
@smokeTest
@smokeTest @issue-7555
Scenario Outline: deleting a received folder doesn't move it to trashbin
Given using <dav-path-version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -27,7 +27,7 @@ Feature: using trashbin together with sharing
| dav-path-version |
| spaces |
@issue-7555
Scenario Outline: deleting a file in a received folder moves it to trashbin of both users
Given using <dav-path-version> DAV path
And user "Brian" has been created with default attributes and without skeleton files
@@ -150,7 +150,7 @@ Feature: using trashbin together with sharing
| dav-path-version |
| spaces |
@issue-7555
Scenario Outline: deleting a file in a received folder when restored it comes back to the original path
Given using <dav-path-version> DAV path
And user "Brian" has been created with default attributes and without skeleton files

2
tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature
View File

@@ -144,7 +144,7 @@ Feature: file versions remember the author of each version
| 1 | Brian |
| 2 | Alice |
@issue-7555
Scenario: enable file versioning and check the history of changes in sharer after renaming file by sharee
Given group "grp1" has been created
And user "Alice" has been added to group "grp1"