123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612 |
- Feature: sharing
- Background:
- Given using api version "1"
- Given using new dav path
- Scenario: Correct webdav share-permissions for received file with edit and reshare permissions
- Given user "user0" exists
- And user "user1" exists
- And User "user0" uploads file with content "foo" to "/tmp.txt"
- And file "/tmp.txt" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- When as "user1" gets properties of folder "/tmp.txt" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "19"
- Scenario: Correct webdav share-permissions for received file with edit permissions but no reshare permissions
- Given user "user0" exists
- And user "user1" exists
- And User "user0" uploads file with content "foo" to "/tmp.txt"
- And file "tmp.txt" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And As an "user0"
- And Updating last share with
- | permissions | 3 |
- When as "user1" gets properties of folder "/tmp.txt" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "3"
- Scenario: Correct webdav share-permissions for received file with reshare permissions but no edit permissions
- Given user "user0" exists
- And user "user1" exists
- And User "user0" uploads file with content "foo" to "/tmp.txt"
- And file "tmp.txt" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And As an "user0"
- And Updating last share with
- | permissions | 17 |
- When as "user1" gets properties of folder "/tmp.txt" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "17"
- Scenario: Correct webdav share-permissions for owned folder
- Given user "user0" exists
- And user "user0" created a folder "/tmp"
- When as "user0" gets properties of folder "/" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "31"
- Scenario: Correct webdav share-permissions for received folder with all permissions
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "31"
- Scenario: Correct webdav share-permissions for received folder with all permissions but edit
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And As an "user0"
- And Updating last share with
- | permissions | 29 |
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "29"
- Scenario: Correct webdav share-permissions for received folder with all permissions but create
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And As an "user0"
- And Updating last share with
- | permissions | 27 |
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "27"
- Scenario: Correct webdav share-permissions for received folder with all permissions but delete
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And As an "user0"
- And Updating last share with
- | permissions | 23 |
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "23"
- Scenario: Correct webdav share-permissions for received folder with all permissions but share
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And As an "user0"
- And Updating last share with
- | permissions | 15 |
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "15"
- Scenario: unique target names for incoming shares
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user0" created a folder "/foo"
- And user "user1" created a folder "/foo"
- When file "/foo" of user "user0" is shared with user "user2"
- And user "user2" accepts last share
- And file "/foo" of user "user1" is shared with user "user2"
- And user "user2" accepts last share
- Then user "user2" should see following elements
- | /foo/ |
- | /foo%20(2)/ |
- Scenario: Creating a new share with a disabled user
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And assure user "user0" is disabled
- And As an "user0"
- When creating a share with
- | path | welcome.txt |
- | shareWith | user1 |
- | shareType | 0 |
- Then the OCS status code should be "997"
- And the HTTP status code should be "401"
- Scenario: Deleting a group share as its owner
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user0" belongs to group "group1"
- And user "user1" belongs to group "group1"
- And As an "user0"
- And creating a share with
- | path | welcome.txt |
- | shareType | 1 |
- | shareWith | group1 |
- When As an "user0"
- And Deleting last share
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And Getting info of last share
- And the OCS status code should be "404"
- And the HTTP status code should be "200"
- And As an "user1"
- And Getting info of last share
- And the OCS status code should be "404"
- And the HTTP status code should be "200"
- Scenario: Deleting a group share as user
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And As an "user0"
- And creating a share with
- | path | welcome.txt |
- | shareType | 1 |
- | shareWith | group1 |
- When As an "user1"
- And Deleting last share
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- Scenario: Merging shares for recipient when shared from outside with group and member
- Given using old dav path
- And As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And user "user0" created a folder "/merge-test-outside"
- When folder "/merge-test-outside" of user "user0" is shared with group "group1"
- And user "user1" accepts last share
- And folder "/merge-test-outside" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- Then as "user1" the folder "/merge-test-outside" exists
- And as "user1" the folder "/merge-test-outside (2)" does not exist
- Scenario: Merging shares for recipient when shared from outside with group and member with different permissions
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And user "user0" created a folder "/merge-test-outside-perms"
- When folder "/merge-test-outside-perms" of user "user0" is shared with group "group1" with permissions 1
- And user "user1" accepts last share
- And folder "/merge-test-outside-perms" of user "user0" is shared with user "user1" with permissions 31
- And user "user1" accepts last share
- Then as "user1" gets properties of folder "/merge-test-outside-perms" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRGDNVCK"
- And as "user1" the folder "/merge-test-outside-perms (2)" does not exist
- Scenario: Merging shares for recipient when shared from outside with two groups
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And group "group2" exists
- And user "user1" belongs to group "group1"
- And user "user1" belongs to group "group2"
- And user "user0" created a folder "/merge-test-outside-twogroups"
- When folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group1"
- And user "user1" accepts last share
- And folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group2"
- And user "user1" accepts last share
- Then as "user1" the folder "/merge-test-outside-twogroups" exists
- And as "user1" the folder "/merge-test-outside-twogroups (2)" does not exist
- Scenario: Merging shares for recipient when shared from outside with two groups with different permissions
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And group "group2" exists
- And user "user1" belongs to group "group1"
- And user "user1" belongs to group "group2"
- And user "user0" created a folder "/merge-test-outside-twogroups-perms"
- When folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group1" with permissions 1
- And user "user1" accepts last share
- And folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group2" with permissions 31
- And user "user1" accepts last share
- Then as "user1" gets properties of folder "/merge-test-outside-twogroups-perms" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRGDNVCK"
- And as "user1" the folder "/merge-test-outside-twogroups-perms (2)" does not exist
- Scenario: Merging shares for recipient when shared from outside with two groups and member
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And group "group2" exists
- And user "user1" belongs to group "group1"
- And user "user1" belongs to group "group2"
- And user "user0" created a folder "/merge-test-outside-twogroups-member-perms"
- When folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group1" with permissions 1
- And user "user1" accepts last share
- And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group2" with permissions 31
- And user "user1" accepts last share
- And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with user "user1" with permissions 1
- And user "user1" accepts last share
- Then as "user1" gets properties of folder "/merge-test-outside-twogroups-member-perms" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRGDNVCK"
- And as "user1" the folder "/merge-test-outside-twogroups-member-perms (2)" does not exist
- Scenario: Merging shares for recipient when shared from inside with group
- Given As an "admin"
- And user "user0" exists
- And group "group1" exists
- And user "user0" belongs to group "group1"
- And user "user0" created a folder "/merge-test-inside-group"
- When folder "/merge-test-inside-group" of user "user0" is shared with group "group1"
- Then as "user0" the folder "/merge-test-inside-group" exists
- And as "user0" the folder "/merge-test-inside-group (2)" does not exist
- Scenario: Merging shares for recipient when shared from inside with two groups
- Given As an "admin"
- And user "user0" exists
- And group "group1" exists
- And group "group2" exists
- And user "user0" belongs to group "group1"
- And user "user0" belongs to group "group2"
- And user "user0" created a folder "/merge-test-inside-twogroups"
- When folder "/merge-test-inside-twogroups" of user "user0" is shared with group "group1"
- And folder "/merge-test-inside-twogroups" of user "user0" is shared with group "group2"
- Then as "user0" the folder "/merge-test-inside-twogroups" exists
- And as "user0" the folder "/merge-test-inside-twogroups (2)" does not exist
- And as "user0" the folder "/merge-test-inside-twogroups (3)" does not exist
- Scenario: Merging shares for recipient when shared from inside with group with less permissions
- Given As an "admin"
- And user "user0" exists
- And group "group1" exists
- And group "group2" exists
- And user "user0" belongs to group "group1"
- And user "user0" belongs to group "group2"
- And user "user0" created a folder "/merge-test-inside-twogroups-perms"
- When folder "/merge-test-inside-twogroups-perms" of user "user0" is shared with group "group1"
- And folder "/merge-test-inside-twogroups-perms" of user "user0" is shared with group "group2"
- Then as "user0" gets properties of folder "/merge-test-inside-twogroups-perms" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "RGDNVCK"
- And as "user0" the folder "/merge-test-inside-twogroups-perms (2)" does not exist
- And as "user0" the folder "/merge-test-inside-twogroups-perms (3)" does not exist
- Scenario: Merging shares for recipient when shared from outside with group then user and recipient renames in between
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And user "user0" created a folder "/merge-test-outside-groups-renamebeforesecondshare"
- When folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
- And user "user1" accepts last share
- And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
- And Sleep for "1" seconds
- And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRGDNVCK"
- And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
- Scenario: Merging shares for recipient when shared from outside with user then group and recipient renames in between
- Given using old dav path
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And user "user0" created a folder "/merge-test-outside-groups-renamebeforesecondshare"
- When folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
- And Sleep for "1" seconds
- And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
- And user "user1" accepts last share
- Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRGDNVCK"
- And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
- Scenario: Empting trashbin
- Given As an "admin"
- And user "user0" exists
- And User "user0" deletes file "/textfile0.txt"
- When User "user0" empties trashbin
- Then the HTTP status code should be "204"
- Scenario: orphaned shares
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/common"
- And user "user0" created a folder "/common/sub"
- And file "/common/sub" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And User "user0" deletes folder "/common"
- When User "user0" empties trashbin
- Then as "user1" the folder "/sub" does not exist
- Scenario: sharing again an own file while belonging to a group
- Given As an "admin"
- Given user "user0" exists
- And group "sharing-group" exists
- And user "user0" belongs to group "sharing-group"
- And file "welcome.txt" of user "user0" is shared with group "sharing-group"
- And Deleting last share
- When creating a share with
- | path | welcome.txt |
- | shareWith | sharing-group |
- | shareType | 1 |
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- Scenario: unshare from self
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "sharing-group" exists
- And user "user0" belongs to group "sharing-group"
- And user "user1" belongs to group "sharing-group"
- And file "/PARENT/parent.txt" of user "user0" is shared with group "sharing-group"
- And user "user1" accepts last share
- And user "user0" stores etag of element "/PARENT"
- And user "user1" stores etag of element "/"
- And As an "user1"
- When Deleting last share
- Then etag of element "/" of user "user1" has changed
- And etag of element "/PARENT" of user "user0" has not changed
- Scenario: do not allow to increase permissions on received share
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/TMP"
- And As an "user0"
- And creating a share with
- | path | TMP |
- | shareType | 0 |
- | shareWith | user1 |
- | permissions | 17 |
- When As an "user1"
- And Updating last share with
- | permissions | 19 |
- Then the OCS status code should be "403"
- And the HTTP status code should be "200"
- Scenario: do not allow to increase permissions on non received share with user with resharing rights
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user0" created a folder "/TMP"
- And As an "user0"
- And creating a share with
- | path | TMP |
- | shareType | 0 |
- | shareWith | user1 |
- | permissions | 31 |
- And user "user1" accepts last share
- And creating a share with
- | path | TMP |
- | shareType | 0 |
- | shareWith | user2 |
- | permissions | 17 |
- When As an "user1"
- And Updating last share with
- | permissions | 19 |
- Then the OCS status code should be "403"
- And the HTTP status code should be "200"
- Scenario: do not allow to increase link share permissions on reshare
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/TMP"
- And As an "user0"
- And creating a share with
- | path | TMP |
- | shareType | 0 |
- | shareWith | user1 |
- | permissions | 17 |
- When As an "user1"
- And accepting last share
- And creating a share with
- | path | TMP |
- | shareType | 3 |
- And Updating last share with
- | publicUpload | true |
- Then the OCS status code should be "404"
- And the HTTP status code should be "200"
- Scenario: do not allow to increase link share permissions on sub reshare
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/TMP"
- And user "user0" created a folder "/TMP/SUB"
- And As an "user0"
- And creating a share with
- | path | TMP |
- | shareType | 0 |
- | shareWith | user1 |
- | permissions | 17 |
- When As an "user1"
- And accepting last share
- And creating a share with
- | path | TMP/SUB |
- | shareType | 3 |
- And Updating last share with
- | publicUpload | true |
- Then the OCS status code should be "404"
- And the HTTP status code should be "200"
- Scenario: deleting file out of a share as recipient creates a backup for the owner
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/shared"
- And User "user0" moved file "/textfile0.txt" to "/shared/shared_file.txt"
- And folder "/shared" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- When User "user1" deletes file "/shared/shared_file.txt"
- Then as "user1" the file "/shared/shared_file.txt" does not exist
- And as "user0" the file "/shared/shared_file.txt" does not exist
- And as "user0" the file "/shared_file.txt" exists in trash
- And as "user1" the file "/shared_file.txt" exists in trash
- Scenario: deleting folder out of a share as recipient creates a backup for the owner
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/shared"
- And user "user0" created a folder "/shared/sub"
- And User "user0" moved file "/textfile0.txt" to "/shared/sub/shared_file.txt"
- And folder "/shared" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- When User "user1" deletes folder "/shared/sub"
- Then as "user1" the folder "/shared/sub" does not exist
- And as "user0" the folder "/shared/sub" does not exist
- And as "user0" the folder "/sub" exists in trash
- And as "user0" the file "/sub/shared_file.txt" exists in trash
- And as "user1" the folder "/sub" exists in trash
- And as "user1" the file "/sub/shared_file.txt" exists in trash
- Scenario: moving a file into a share as recipient
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/shared"
- And folder "/shared" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- When User "user1" moved file "/textfile0.txt" to "/shared/shared_file.txt"
- Then as "user1" the file "/shared/shared_file.txt" exists
- And as "user0" the file "/shared/shared_file.txt" exists
- Scenario: receiving shares into a configured share_folder
- Given As an "admin"
- And invoking occ with "config:system:set share_folder --value received_shares"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/shared_folder"
- And User "user0" moved file "/textfile0.txt" to "/shared_file.txt"
- When folder "/shared_folder" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- Then as "user1" the file "/received_shares/shared_folder" exists
- When file "/shared_file.txt" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- Then as "user1" the file "/received_shares/shared_file.txt" exists
- Scenario: Owner of subshares is adjusted after moving into received share
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user0" created a folder "/shared"
- And folder "/shared" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And user "user1" created a folder "/movein"
- And user "user1" created a folder "/movein/subshare"
- When As an "user1"
- And folder "/movein" of user "user1" is shared with user "user2"
- And save last share id
- Then Getting info of last share
- And Share fields of last share match with
- | uid_file_owner | user1 |
- | share_with | user2 |
- When User "user1" moved file "/movein" to "/shared/movein"
- Then As an "user0"
- And Getting info of last share
- And Share fields of last share match with
- | uid_file_owner | user0 |
- | share_with | user2 |
- Scenario: Owner of subshares is adjusted after moving out of received share
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user0" created a folder "/shared"
- And user "user0" created a folder "/shared/moveout"
- And user "user0" created a folder "/shared/moveout/subshare"
- And folder "/shared" of user "user0" is shared with user "user1"
- And user "user1" accepts last share
- And As an "user1"
- And folder "/shared/moveout/subshare" of user "user1" is shared with user "user2"
- And save last share id
- When As an "user1"
- Then Getting info of last share
- And Share fields of last share match with
- | uid_file_owner | user0 |
- | share_with | user2 |
- When User "user1" moved file "/shared/moveout" to "/moveout"
- Then Getting info of last share
- And Share fields of last share match with
- | uid_file_owner | user1 |
- | share_with | user2 |
- Scenario: Link shares inside of group shares keep their original data when the root share is updated
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And As an "user0"
- And user "user0" created a folder "/share"
- And folder "/share" of user "user0" is shared with group "group1"
- And user "user1" accepts last share
- And user "user0" created a folder "/share/subfolder"
- And As an "user1"
- And save the last share data as "original"
- And as "user1" creating a share with
- | path | /share/subfolder |
- | shareType | 3 |
- | permissions | 31 |
- And save the last share data as "link"
- And As an "user0"
- And restore the last share data from "original"
- When Updating last share with
- | permissions | 23 |
- | expireDate | +3 days |
- And restore the last share data from "link"
- And Getting info of last share
- And Share fields of last share match with
- | id | A_NUMBER |
- | item_source | A_NUMBER |
- | share_type | 3 |
- | permissions | 23 |
- | file_target | /subfolder |
- | expireDate | |
|