blob: 957058cfc5edc02af5e490ed6d4c25660f964225 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
Feature: Sharing
As a user
I want to share files and folders with other users
So that those users can access the files and folders
Background:
Given user "Alice" has been created on the server with default attributes and without skeleton files
@smokeTest
Scenario: simple sharing
Given user "Brian" has been created on the server with default attributes and without skeleton files
And user "Alice" has uploaded on the server file with content "ownCloud test text file 0" to "/textfile0.txt"
And user "Alice" has set up a client with default settings
When the user adds "Brian Murphy" as collaborator of resource "%client_sync_path%/textfile0.txt" with permissions "edit,share" using the client-UI
Then user "Brian Murphy" should be listed in the collaborators list for file "%client_sync_path%/textfile0.txt" with permissions "edit,share" on the client-UI
@issue-7459
Scenario: Progress indicator should not be visible after unselecting the password protection checkbox while sharing through public link
Given user "Alice" has uploaded on the server file with content "ownCloud test text file 0" to "/textfile0.txt"
And user "Alice" has set up a client with default settings
When the user opens the public links dialog of "%client_sync_path%/textfile0.txt" using the client-UI
And the user toggles the password protection using the client-UI
And the user toggles the password protection using the client-UI
Then the password progress indicator should not be visible in the client-UI - expected to fail
@issue-7423
Scenario: unshare a reshared file
Given the setting "shareapi_auto_accept_share" on the server of app "core" has been set to "no"
And the administrator on the server has set the default folder for received shares to "Shares"
And user "Alice" has created on the server folder "simple-folder"
And user "Brian" has been created on the server with default attributes and without skeleton files
And user "Carol" has been created on the server with default attributes and without skeleton files
And user "Alice" has shared folder "simple-folder" on the server with user "Brian"
And user "Brian" has accepted the share "simple-folder" on the server offered by user "Alice"
And user "Brian" has shared folder "Shares/simple-folder" on the server with user "Carol"
And user "Brian" has set up a client with default settings
And user "Alice" has updated the share permissions on the server for folder "/simple-folder" to "read" for user "Brian"
When user "Brian" opens the sharing dialog of "%client_sync_path%/Shares/simple-folder" using the client-UI
Then the error text "The file can not be shared because it was shared without sharing permission." should be displayed in the sharing dialog
@smokeTest
Scenario: simple sharing of a file by public link without password
Given user "Alice" has uploaded on the server file with content "ownCloud test text file 0" to "/textfile0.txt"
And user "Alice" has set up a client with default settings
When the user creates a new public link for file "%client_sync_path%/textfile0.txt" without password using the client-UI
Then as user "Alice" the file "textfile0.txt" should have a public link on the server
And the public should be able to download the file "textfile0.txt" without password from the last created public link by "Alice" on the server
Scenario: simple sharing of a file by public link with password
Given user "Alice" has set up a client with default settings
And user "Alice" has uploaded on the server file with content "ownCloud test text file 0" to "/textfile0.txt"
When the user creates a new public link for file "%client_sync_path%/textfile0.txt" with password "pass123" using the client-UI
Then as user "Alice" the file "textfile0.txt" should have a public link on the server
And the public should be able to download the file "textfile0.txt" with password "pass123" from the last created public link by "Alice" on the server
@issue-8733
Scenario: user changes the expiration date of an already existing public link using webUI
Given user "Alice" has uploaded on the server file with content "ownCloud test text file 0" to "/textfile0.txt"
And user "Alice" has set up a client with default settings
And user "Alice" has created a public link on the server with following settings
| path | textfile0.txt |
| name | Public link |
| expireDate | 2031-10-14 |
When the user opens the public links dialog of "%client_sync_path%/textfile0.txt" using the client-UI
And the user edits the public link named "Public link" of file "textfile0.txt" changing following
| expireDate | 2038-07-21 |
Then the fields of the last public link share response of user "Alice" should include on the server
| expireDate | 2038-07-21 |
@smokeTest
Scenario: simple sharing of a folder by public link without password
Given user "Alice" has created on the server folder "simple-folder"
And user "Alice" has set up a client with default settings
When the user creates a new public link with permissions "Download / View" for folder "%client_sync_path%/simple-folder" without password using the client-UI
Then as user "Alice" the folder "simple-folder" should have a public link on the server
And the public should be able to download the folder "lorem.txt" without password from the last created public link by "Alice" on the server
Scenario: simple sharing of a folder by public link with password
Given user "Alice" has created on the server folder "simple-folder"
And user "Alice" has set up a client with default settings
When the user creates a new public link with permissions "Download / View" for folder "%client_sync_path%/simple-folder" with password "pass123" using the client-UI
Then as user "Alice" the folder "simple-folder" should have a public link on the server
And the public should be able to download the folder "lorem.txt" with password "pass123" from the last created public link by "Alice" on the server
@issue-8733
Scenario: user changes the expiration date of an already existing public link for folder using client-UI
Given user "Alice" has created on the server folder "simple-folder"
And user "Alice" has set up a client with default settings
And user "Alice" has created a public link on the server with following settings
| path | simple-folder |
| name | Public link |
| expireDate | 2031-10-14 |
| permissions | read, update, create, delete |
When the user opens the public links dialog of "%client_sync_path%/simple-folder" using the client-UI
And the user edits the public link named "Public link" of file "simple-folder" changing following
| expireDate | 2038-07-21 |
Then the fields of the last public link share response of user "Alice" on the server should include
| expireDate | 2038-07-21 |
Scenario Outline: simple sharing of folder by public link with different roles
Given user "Alice" has created on the server folder "simple-folder"
And user "Alice" has set up a client with default settings
When the user creates a new public link for folder "%client_sync_path%/simple-folder" using the client-UI with these details:
| role | <role> |
Then user "Alice" on the server should have a share with these details:
| field | value |
| share_type | public_link |
| uid_owner | Alice |
| permissions | <permissions> |
| path | /simple-folder |
| name | Public link |
Examples:
| role | permissions |
| Viewer | read |
| Editor | read, update, create, delete |
| Contributor | create |
Scenario: sharing by public link with "Uploader" role
Given user "Alice" has created on the server folder "simple-folder"
And user "Alice" on the server has created file "simple-folder/lorem.txt"
And user "Alice" has set up a client with default settings
When the user creates a new public link for folder "%client_sync_path%/simple-folder" with "Contributor" using the client-UI
Then user "Alice" on the server should have a share with these details:
| field | value |
| share_type | public_link |
| uid_owner | Alice |
| permissions | create |
| path | /simple-folder |
| name | Public link |
And the public should not be able to download the file "lorem.txt" from the last created public link by "Alice" on the server
|
