mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-02-05 19:48:59 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7514 from owncloud/bump-to-v8.0.0-alpha.4

Browse Source 
[full-ci] chore: bump web to v8.0.0-alpha.4
This commit is contained in:
Jannik Stehle
2023-10-17 18:43:46 +02:00
committed by GitHub
parent c179485db6 c817f9b574
commit b5ad0796c4
3 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.drone.env
View File

@@ -1,3 +1,3 @@
# The test runner source for UI tests
WEB_COMMITID=6fd967a12cfbe8fda936680ecf353c12eab78452
WEB_COMMITID=81b683a3c5b9e719ce6fa44b72f268e419e1d97c
WEB_BRANCH=master

2
services/web/Makefile
View File

@@ -1,6 +1,6 @@
SHELL := bash
NAME := web
WEB_ASSETS_VERSION = v8.0.0-alpha.3
WEB_ASSETS_VERSION = v8.0.0-alpha.4
include ../../.make/recursion.mk

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

@@ -487,20 +487,20 @@ Feature: share resources where the sharee receives the share in multiple ways
# | 2 |
Scenario: share receiver renames a group share and receives same resource through user share with less permissions
Given group "grp" has been created
And user "Brian" has been added to group "grp"
And user "Alice" has been added to group "grp"
And user "Alice" has created folder "parent"
And user "Alice" has created folder "parent/child"
And user "Alice" has uploaded file with content "Share content" to "parent/child/lorem.txt"
And user "Alice" has shared folder "parent" with group "grp" with permissions "all"
And user "Brian" should be able to rename folder "/Shares/parent" to "/Shares/sharedParent"
And user "Alice" should be able to share folder "parent" with user "Brian" with permissions "read" using the sharing API
# Note: Brian has already accepted the share of this resource as a member of "grp".
# Now he has also received the same resource shared directly to "Brian".
# The server should effectively "auto-accept" this new "copy" of the resource
# and present to Brian only the single resource "Shares/sharedParent"
And as "Brian" folder "Shares/parent" should not exist
And as "Brian" folder "Shares/sharedParent" should exist
And as "Brian" file "Shares/sharedParent/child/lorem.txt" should exist
# Scenario: share receiver renames a group share and receives same resource through user share with less permissions
# Given group "grp" has been created
# And user "Brian" has been added to group "grp"
# And user "Alice" has been added to group "grp"
# And user "Alice" has created folder "parent"
# And user "Alice" has created folder "parent/child"
# And user "Alice" has uploaded file with content "Share content" to "parent/child/lorem.txt"
# And user "Alice" has shared folder "parent" with group "grp" with permissions "all"
# And user "Brian" should be able to rename folder "/Shares/parent" to "/Shares/sharedParent"
# And user "Alice" should be able to share folder "parent" with user "Brian" with permissions "read" using the sharing API
# # Note: Brian has already accepted the share of this resource as a member of "grp".
# # Now he has also received the same resource shared directly to "Brian".
# # The server should effectively "auto-accept" this new "copy" of the resource
# # and present to Brian only the single resource "Shares/sharedParent"
# And as "Brian" folder "Shares/parent" should not exist
# And as "Brian" folder "Shares/sharedParent" should exist
# And as "Brian" file "Shares/sharedParent/child/lorem.txt" should exist