sharing-v1.feature 44.8 KB
Newer Older
Sergio Bertolin's avatar
Sergio Bertolin committed
1
2
3
Feature: sharing
  Background:
    Given using api version "1"
4
    Given using old dav path
Sergio Bertolin's avatar
Sergio Bertolin committed
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

  Scenario: Creating a new share with user
    Given user "user0" exists
    And user "user1" exists
    And As an "user0"
    When sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | welcome.txt |
      | shareWith | user1 |
      | shareType | 0 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

  Scenario: Creating a share with a group
    Given user "user0" exists
    And user "user1" exists
    And group "sharing-group" exists
    And As an "user0"
    When sending "POST" to "/apps/files_sharing/api/v1/shares" 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"

29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
  Scenario: Creating a new share with user who already received a share through their group
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "sharing-group" exists
    And user "user1" belongs to group "sharing-group"
    And file "welcome.txt" of user "user0" is shared with group "sharing-group"
    And As an "user0"
    Then sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | welcome.txt |
      | shareWith | user1 |
      | shareType | 0 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

Sergio Bertolin's avatar
Sergio Bertolin committed
44
45
46
  Scenario: Creating a new public share
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
47
    When creating a share with
Sergio Bertolin's avatar
Sergio Bertolin committed
48
49
50
51
52
53
54
55
56
      | path | welcome.txt |
      | shareType | 3 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Public shared file "welcome.txt" can be downloaded

  Scenario: Creating a new public share with password
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
57
    When creating a share with
Sergio Bertolin's avatar
Sergio Bertolin committed
58
59
60
61
62
63
64
      | path | welcome.txt |
      | shareType | 3 |
      | password | publicpw |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Public shared file "welcome.txt" with password "publicpw" can be downloaded

65
66
67
  Scenario: Creating a new public share of a folder
   Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
68
    When creating a share with
69
70
71
72
73
74
75
76
77
78
      | path | FOLDER |
      | shareType | 3 |
      | password | publicpw |
      | expireDate | +3 days |
      | publicUpload | true |
      | permissions | 7 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
79
      | permissions | 15 |
80
81
82
      | expiration | +3 days |
      | url | AN_URL |
      | token | A_TOKEN |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
83
      | mimetype | httpd/unix-directory |
84

Sergio Bertolin's avatar
Sergio Bertolin committed
85
86
87
  Scenario: Creating a new public share with password and adding an expiration date
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
88
    When creating a share with
Sergio Bertolin's avatar
Sergio Bertolin committed
89
90
91
      | path | welcome.txt |
      | shareType | 3 |
      | password | publicpw |
92
93
    And Updating last share with
      | expireDate | +3 days |
Sergio Bertolin's avatar
Sergio Bertolin committed
94
95
96
97
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Public shared file "welcome.txt" with password "publicpw" can be downloaded

98
  Scenario: Creating a new public share, updating its expiration date and getting its info
99
100
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
101
    When creating a share with
102
103
104
105
      | path | FOLDER |
      | shareType | 3 |
    And Updating last share with
      | expireDate | +3 days |
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
    And Getting info of last share 
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | folder |
      | item_source | A_NUMBER |
      | share_type | 3 |
      | file_source | A_NUMBER |
      | file_target | /FOLDER |
      | permissions | 1 |
      | stime | A_NUMBER |
      | expiration | +3 days |
      | token | A_TOKEN |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
      | url | AN_URL |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
127
      | mimetype | httpd/unix-directory |
128
129
130
131

  Scenario: Creating a new public share, updating its password and getting its info
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
132
    When creating a share with
133
134
135
      | path | FOLDER |
      | shareType | 3 |
    And Updating last share with 
136
      | password | publicpw |
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
    And Getting info of last share 
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | folder |
      | item_source | A_NUMBER |
      | share_type | 3 |
      | file_source | A_NUMBER |
      | file_target | /FOLDER |
      | permissions | 1 |
      | stime | A_NUMBER |
      | token | A_TOKEN |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
      | url | AN_URL |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
157
      | mimetype | httpd/unix-directory |
158
159
160
161

  Scenario: Creating a new public share, updating its permissions and getting its info
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
162
    When creating a share with
163
164
165
      | path | FOLDER |
      | shareType | 3 |
    And Updating last share with
166
167
168
169
170
171
172
173
174
175
176
      | permissions | 7 |
    And Getting info of last share 
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | folder |
      | item_source | A_NUMBER |
      | share_type | 3 |
      | file_source | A_NUMBER |
      | file_target | /FOLDER |
177
      | permissions | 15 |
178
179
180
181
182
183
184
185
186
      | stime | A_NUMBER |
      | token | A_TOKEN |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
      | url | AN_URL |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
187
      | mimetype | httpd/unix-directory |
188

189
190
191
  Scenario: Creating a new public share, updating publicUpload option and getting its info
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
192
    When creating a share with
193
194
195
196
197
198
199
200
201
202
203
204
205
206
      | path | FOLDER |
      | shareType | 3 |
    And Updating last share with
      | publicUpload | true |
    And Getting info of last share 
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | folder |
      | item_source | A_NUMBER |
      | share_type | 3 |
      | file_source | A_NUMBER |
      | file_target | /FOLDER |
207
      | permissions | 15 |
208
209
210
211
212
213
214
215
216
      | stime | A_NUMBER |
      | token | A_TOKEN |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
      | url | AN_URL |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
217
      | mimetype | httpd/unix-directory |
218

219
220
221
  Scenario: getting all shares of a user using that user
    Given user "user0" exists
    And user "user1" exists
222
223
    And User "user0" moved file "/textfile0.txt" to "/file_to_share.txt"
    And file "file_to_share.txt" of user "user0" is shared with user "user1"
224
225
226
227
    And As an "user0"
    When sending "GET" to "/apps/files_sharing/api/v1/shares"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
228
    And File "file_to_share.txt" should be included in the response
229
230

  Scenario: getting all shares of a user using another user
231
232
    Given user "user0" exists
    And user "user1" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
233
    And file "textfile0.txt" of user "user0" is shared with user "user1"
234
235
236
237
    And As an "admin"
    When sending "GET" to "/apps/files_sharing/api/v1/shares"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
238
    And File "textfile0.txt" should not be included in the response
239

240
241
242
243
244
  Scenario: getting all shares of a file
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
245
246
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile0.txt" of user "user0" is shared with user "user2"
247
248
249
250
251
252
253
254
    And As an "user0"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?path=textfile0.txt"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And User "user1" should be included in the response
    And User "user2" should be included in the response
    And User "user3" should not be included in the response

Roeland Jago Douma's avatar
Roeland Jago Douma committed
255
256
257
258
259
260
261
262
263
264
265
266
267
268
  Scenario: getting all shares of a file with reshares
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile0 (2).txt" of user "user1" is shared with user "user2"
    And As an "user0"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?reshares=true&path=textfile0.txt"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And User "user1" should be included in the response
    And User "user2" should be included in the response
    And User "user3" should not be included in the response
269

Sergio Bertolin's avatar
Sergio Bertolin committed
270
271
272
273
274
275
  Scenario: Reshared files can be still accessed if a user in the middle removes it.
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
276
277
278
    And User "user1" moved file "/textfile0 (2).txt" to "/textfile0_shared.txt"
    And file "textfile0_shared.txt" of user "user1" is shared with user "user2"
    And file "textfile0_shared.txt" of user "user2" is shared with user "user3"
Sergio Bertolin's avatar
Sergio Bertolin committed
279
    And As an "user1"
280
    When User "user1" deletes file "/textfile0_shared.txt"
Sergio Bertolin's avatar
Sergio Bertolin committed
281
    And As an "user3"
282
    And Downloading file "/textfile0_shared.txt" with range "bytes=1-7"
Sergio Bertolin's avatar
Sergio Bertolin committed
283
284
    Then Downloaded content should be "wnCloud"

285
286
287
  Scenario: getting share info of a share
    Given user "user0" exists
    And user "user1" exists
288
289
    And User "user0" moved file "/textfile0.txt" to "/file_to_share.txt"
    And file "file_to_share.txt" of user "user0" is shared with user "user1"
290
291
292
293
294
295
296
297
298
299
300
    And As an "user0"
    When Getting info of last share
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | file |
      | item_source | A_NUMBER |
      | share_type | 0 |
      | share_with | user1 |
      | file_source | A_NUMBER |
301
302
      | file_target | /file_to_share.txt |
      | path | /file_to_share.txt |
303
      | permissions | 19 |
304
305
306
307
308
309
310
311
      | stime | A_NUMBER |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | share_with_displayname | user1 |
      | displayname_owner | user0 |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
312
      | mimetype          | text/plain |
313

314
315
316
317
318
319
  Scenario: keep group permissions in sync
    Given As an "admin"
    Given user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
Sergio Bertolin's avatar
Sergio Bertolin committed
320
    And file "textfile0.txt" of user "user0" is shared with group "group1"
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
    And User "user1" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
    And As an "user0"
    When Updating last share with
      | permissions | 1 |
    And Getting info of last share
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | file |
      | item_source | A_NUMBER |
      | share_type | 1 |
      | file_source | A_NUMBER |
      | file_target | /textfile0.txt |
      | permissions | 1 |
      | stime | A_NUMBER |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
343
      | mimetype          | text/plain |
344

345
346
347
  Scenario: Sharee can see the share
    Given user "user0" exists
    And user "user1" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
348
    And file "textfile0.txt" of user "user0" is shared with user "user1"
349
350
351
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
    Then the OCS status code should be "100"
352
353
354
    And the HTTP status code should be "200"
    And last share_id is included in the answer

Roeland Jago Douma's avatar
Roeland Jago Douma committed
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
  Scenario: Sharee can see the filtered share
    Given user "user0" exists
    And user "user1" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile1.txt" of user "user0" is shared with user "user1"
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true&path=textfile1 (2).txt"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And last share_id is included in the answer

  Scenario: Sharee can't see the share that is filtered out
    Given user "user0" exists
    And user "user1" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile1.txt" of user "user0" is shared with user "user1"
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true&path=textfile0 (2).txt"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And last share_id is not included in the answer

377
378
379
380
381
382
383
384
385
386
  Scenario: Sharee can see the group share
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group0" exists
    And user "user1" belongs to group "group0"
    And file "textfile0.txt" of user "user0" is shared with group "group0"
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
    Then the OCS status code should be "100"
387
388
389
    And the HTTP status code should be "200"
    And last share_id is included in the answer

Sergio Bertolin's avatar
Sergio Bertolin committed
390
391
392
393
394
395
396
397
398
399
400
401
402
  Scenario: User is not allowed to reshare file
    As an "admin"
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And As an "user0"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 8 |
    And As an "user1"
    When creating a share with
403
      | path | /textfile0 (2).txt |
Sergio Bertolin's avatar
Sergio Bertolin committed
404
405
406
407
408
409
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 31 |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"

410
411
412
413
414
415
416
417
418
419
420
421
422
  Scenario: User is not allowed to reshare file with more permissions
    As an "admin"
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And As an "user0"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 16 |
    And As an "user1"
    When creating a share with
423
      | path | /textfile0 (2).txt |
424
425
426
427
428
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 31 |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"
Sergio Bertolin's avatar
Sergio Bertolin committed
429

430
431
432
433
  Scenario: Get a share with a user which didn't received the share 
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
434
    And file "textfile0.txt" of user "user0" is shared with user "user1"
435
436
437
438
439
    And As an "user2"
    When Getting info of last share 
    Then the OCS status code should be "404" 
    And the HTTP status code should be "200"

440
441
442
443
444
445
  Scenario: Share of folder and sub-folder to same user - core#20645
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group0" exists
    And user "user1" belongs to group "group0"
Sergio Bertolin's avatar
Sergio Bertolin committed
446
447
    And file "/PARENT" of user "user0" is shared with user "user1"
    When file "/PARENT/CHILD" of user "user0" is shared with group "group0"
448
449
450
451
452
453
    Then user "user1" should see following elements
      | /FOLDER/ |
      | /PARENT/ |
      | /CHILD/ |
      | /PARENT/parent.txt |
      | /CHILD/child.txt |
454
455
    And the HTTP status code should be "200"

456
  Scenario: Share a file by multiple channels 
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And group "group0" exists
    And user "user1" belongs to group "group0"
    And user "user2" belongs to group "group0"
    And user "user0" created a folder "/common"
    And user "user0" created a folder "/common/sub"
    And file "common" of user "user0" is shared with group "group0"
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    And User "user1" moved file "/textfile0.txt" to "/common/textfile0.txt"
    And User "user1" moved file "/common/textfile0.txt" to "/common/sub/textfile0.txt"
    And As an "user2"
    When Downloading file "/common/sub/textfile0.txt" with range "bytes=9-17"
    Then Downloaded content should be "test text"
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
    And Downloaded content when downloading file "/textfile0.txt" with range "bytes=9-17" should be "test text"
    And user "user2" should see following elements
      | /common/sub/textfile0.txt |

  Scenario: Share a file by multiple channels
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And group "group0" exists
    And user "user1" belongs to group "group0"
    And user "user2" belongs to group "group0"
    And user "user0" created a folder "/common"
    And user "user0" created a folder "/common/sub"
    And file "common" of user "user0" is shared with group "group0"
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    And User "user1" moved file "/textfile0.txt" to "/common/textfile0.txt"
    And User "user1" moved file "/common/textfile0.txt" to "/common/sub/textfile0.txt"
    And As an "user2"
    When Downloading file "/textfile0.txt" with range "bytes=9-17"
    Then Downloaded content should be "test text"
494
495
496
    And user "user2" should see following elements
      | /common/sub/textfile0.txt |

497
498
499
500
501
502
  Scenario: Delete all group shares
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
Sergio Bertolin's avatar
Sergio Bertolin committed
503
    And file "textfile0.txt" of user "user0" is shared with group "group1"
504
505
506
507
508
509
510
511
512
    And User "user1" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
    And As an "user0"
    And Deleting last share
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And last share_id is not included in the answer

513
514
515
  Scenario: delete a share
    Given user "user0" exists
    And user "user1" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
516
    And file "textfile0.txt" of user "user0" is shared with user "user1"
517
518
519
520
521
    And As an "user0"
    When Deleting last share
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

Roeland Jago Douma's avatar
Roeland Jago Douma committed
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
  Scenario: Keep usergroup shares (#22143)
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And group "group" exists
    And user "user1" belongs to group "group"
    And user "user2" belongs to group "group"
    And user "user0" created a folder "/TMP"
    And file "TMP" of user "user0" is shared with group "group"
    And user "user1" created a folder "/myFOLDER"
    And User "user1" moves file "/TMP" to "/myFOLDER/myTMP"
    And user "user2" does not exist
    And user "user1" should see following elements
      | /myFOLDER/myTMP/ |
537
538

  Scenario: Check quota of owners parent directory of a shared file
539
    Given using old dav path
540
541
542
543
544
545
546
547
    And As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user1" has a quota of "0"
    And User "user0" moved file "/welcome.txt" to "/myfile.txt"
    And file "myfile.txt" of user "user0" is shared with user "user1"
    When User "user1" uploads file "data/textfile.txt" to "/myfile.txt"
    Then the HTTP status code should be "204"
548
549
550
551
552
553
554

  Scenario: Don't allow sharing of the root
    Given user "user0" exists
    And As an "user0"
    When creating a share with
      | path | / |
      | shareType | 3 |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
555
556
557
558
559
560
561
562
563
564
565
566
567
    Then the OCS status code should be "403"

  Scenario: Allow modification of reshare
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user0" created a folder "/TMP"
    And file "TMP" of user "user0" is shared with user "user1"
    And file "TMP" of user "user1" is shared with user "user2"
    And As an "user1"
    When Updating last share with
      | permissions | 1 |
    Then the OCS status code should be "100"
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588

  Scenario: Do not allow reshare to exceed permissions
    Given 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 | 21 |
    And As an "user1"
    And creating a share with
      | path | /TMP |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 21 |
    When Updating last share with
      | permissions | 31 |
    Then the OCS status code should be "404"
Roeland Jago Douma's avatar
Roeland Jago Douma committed
589
590
591
592
593
594
595
596
597
598
599
600

  Scenario: Only allow 1 link share per file/folder
    Given user "user0" exists
    And As an "user0"
    And creating a share with
      | path | welcome.txt |
      | shareType | 3 |
    When save last share id
    And creating a share with
      | path | welcome.txt |
      | shareType | 3      |
    Then share ids should match
601
602
603
604
605

  Scenario: Correct webdav share-permissions for owned file
    Given user "user0" exists
    And User "user0" uploads file with content "foo" to "/tmp.txt"
    When as "user0" gets properties of folder "/tmp.txt" with
606
607
      |{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"
608
609
610
611
612

  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"
613
    And file "/tmp.txt" of user "user0" is shared with user "user1"
614
    When as "user1" gets properties of folder "/tmp.txt" with
615
616
      |{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"
617
618
619
620
621
622
623
624
625
626

  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 As an "user0"
    And Updating last share with
      | permissions | 3 |
    When as "user1" gets properties of folder "/tmp.txt" with
627
628
      |{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"
629
630
631
632
633
634
635
636
637
638

  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 As an "user0"
    And Updating last share with
      | permissions | 17 |
    When as "user1" gets properties of folder "/tmp.txt" with
639
640
      |{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"
641
642
643
644
645

  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
646
647
      |{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"
648
649
650
651
652
653
654

  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"
    When as "user1" gets properties of folder "/tmp" with
655
656
      |{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"
657
658
659
660
661
662
663
664
665
666

  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 As an "user0"
    And Updating last share with
      | permissions | 29 |
    When as "user1" gets properties of folder "/tmp" with
667
668
      |{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"
669
670
671
672
673
674
675
676
677
678

  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 As an "user0"
    And Updating last share with
      | permissions | 27 |
    When as "user1" gets properties of folder "/tmp" with
679
680
      |{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"
681
682
683
684
685
686
687
688
689
690

  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 As an "user0"
    And Updating last share with
      | permissions | 23 |
    When as "user1" gets properties of folder "/tmp" with
691
692
      |{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"
693
694
695
696
697
698
699
700
701
702

  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 As an "user0"
    And Updating last share with
      | permissions | 15 |
    When as "user1" gets properties of folder "/tmp" with
703
704
      |{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"
705

706
  Scenario: unique target names for incoming shares
707
708
709
710
711
712
713
714
715
716
    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 file "/foo" of user "user1" is shared with user "user2"
    Then user "user2" should see following elements
      | /foo/       |
      | /foo%20(2)/ |
717
718
719
720
721
722
723
724
725
726
727

  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 sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | welcome.txt |
      | shareWith | user1 |
      | shareType | 0 |
728
729
    Then the OCS status code should be "997"
    And the HTTP status code should be "401"
730
731

  Scenario: Merging shares for recipient when shared from outside with group and member
732
733
    Given using old dav path
    And As an "admin"
734
735
736
737
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
738
739
740
741
742
    And user "user0" created a folder "/merge-test-outside"
    When folder "/merge-test-outside" of user "user0" is shared with group "group1"
    And folder "/merge-test-outside" of user "user0" is shared with user "user1"
    Then as "user1" the folder "/merge-test-outside" exists
    And as "user1" the folder "/merge-test-outside (2)" does not exist
743
744
745
746
747
748
749

  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"
750
751
752
753
    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 folder "/merge-test-outside-perms" of user "user0" is shared with user "user1" with permissions 31
    Then as "user1" gets properties of folder "/merge-test-outside-perms" with
754
755
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
756
    And as "user1" the folder "/merge-test-outside-perms (2)" does not exist
757
758
759
760
761
762
763
764
765

  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"
766
767
768
769
770
    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 folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group2"
    Then as "user1" the folder "/merge-test-outside-twogroups" exists
    And as "user1" the folder "/merge-test-outside-twogroups (2)" does not exist
771
772
773
774
775
776
777
778
779

  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"
780
781
782
783
    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 folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group2" with permissions 31
    Then as "user1" gets properties of folder "/merge-test-outside-twogroups-perms" with
784
785
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
786
    And as "user1" the folder "/merge-test-outside-twogroups-perms (2)" does not exist
787
788
789
790
791
792
793
794
795

  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"
796
797
798
799
800
    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 folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group2" with permissions 31
    And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with user "user1" with permissions 1
    Then as "user1" gets properties of folder "/merge-test-outside-twogroups-member-perms" with
801
802
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
803
    And as "user1" the folder "/merge-test-outside-twogroups-member-perms (2)" does not exist
804
805
806
807
808
809

  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"
810
    And user "user0" created a folder "/merge-test-inside-group"
811
    When folder "/merge-test-inside-group" of user "user0" is shared with group "group1"
812
813
    Then as "user0" the folder "/merge-test-inside-group" exists
    And as "user0" the folder "/merge-test-inside-group (2)" does not exist
814
815
816
817
818
819
820
821

  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"
822
823
824
825
826
827
    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
828
829
830
831
832
833
834
835

  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"
836
837
838
839
    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
840
841
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "RDNVCK"
842
843
    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
844

845
846
847
848
849
850
  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"
851
852
    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"
853
    And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
854
855
    And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
    Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
856
857
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
858
    And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
859
860
861
862
863
864
865

  Scenario: Merging shares for recipient when shared from outside with user then group 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"
866
867
    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"
868
    And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
869
870
    And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
    Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
871
872
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
873
    And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
874

875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
  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 "200"

  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 "user0" deletes folder "/common"
    When User "user0" empties trashbin
891
    Then as "user1" the folder "/sub" does not exist
892

Sergio Bertolin's avatar
Sergio Bertolin committed
893
894
895
896
897
898
899
900
901
902
903
904
905
906
  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 sending "POST" to "/apps/files_sharing/api/v1/shares" 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"

907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
  Scenario: sharing subfolder when parent already shared
    Given As an "admin"
    Given user "user0" exists
    Given user "user1" exists
    And group "sharing-group" exists
    And user "user0" created a folder "/test"
    And user "user0" created a folder "/test/sub"
    And file "/test" of user "user0" is shared with group "sharing-group"
    And As an "user0"
    When sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | /test/sub |
      | shareWith | user1 |
      | shareType | 0 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
	And as "user1" the folder "/sub" exists

  Scenario: sharing subfolder when parent already shared with group of sharer
    Given As an "admin"
    Given user "user0" exists
    Given user "user1" exists
    And group "sharing-group" exists
    And user "user0" belongs to group "sharing-group"
    And user "user0" created a folder "/test"
    And user "user0" created a folder "/test/sub"
    And file "/test" of user "user0" is shared with group "sharing-group"
    And As an "user0"
    When sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | /test/sub |
      | shareWith | user1 |
      | shareType | 0 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
	And as "user1" the folder "/sub" exists

  Scenario: sharing subfolder of already shared folder, GET result is correct
    Given As an "admin"
    Given user "user0" exists
    Given user "user1" exists
    Given user "user2" exists
    Given user "user3" exists
    Given user "user4" exists
    And user "user0" created a folder "/folder1"
    And file "/folder1" of user "user0" is shared with user "user1"
    And file "/folder1" of user "user0" is shared with user "user2"
	And user "user0" created a folder "/folder1/folder2"
    And file "/folder1/folder2" of user "user0" is shared with user "user3"
    And file "/folder1/folder2" of user "user0" is shared with user "user4"
    And As an "user0"
    When sending "GET" to "/apps/files_sharing/api/v1/shares"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
	And the response contains 4 entries
	And File "/folder1" should be included as path in the response
	And File "/folder1/folder2" should be included as path in the response
	And sending "GET" to "/apps/files_sharing/api/v1/shares?path=/folder1/folder2"
	And the response contains 2 entries
	And File "/folder1" should not be included as path in the response
	And File "/folder1/folder2" should be included as path in the response

967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
  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 "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

982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
  Scenario: Increasing permissions is allowed for owner
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "new-group" exists
    And user "user0" belongs to group "new-group"
    And user "user1" belongs to group "new-group"
    And Assure user "user0" is subadmin of group "new-group"
    And As an "user0"
    And folder "/FOLDER" of user "user0" is shared with group "new-group"
    And Updating last share with
      | permissions | 0 |
    When Updating last share with
      | permissions | 31 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

  Scenario: Adding public upload to a read only shared folder as recipient is not allowed
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And As an "user0"
    And user "user0" created a folder "/test"
    And folder "/test" of user "user0" is shared with user "user1" with permissions 17
    And As an "user1"
    And creating a share with
      | path | /test |
      | shareType | 3 |
      | publicUpload | false |
    When Updating last share with
      | publicUpload | true |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"

  Scenario: Adding public upload to a shared folder as recipient is allowed with permissions
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And As an "user0"
    And user "user0" created a folder "/test"
    And folder "/test" of user "user0" is shared with user "user1" with permissions 31
    And As an "user1"
    And creating a share with
      | path | /test |
      | shareType | 3 |
      | publicUpload | false |
    When Updating last share with
      | publicUpload | true |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

  Scenario: Adding public upload to a read only shared folder as recipient is not allowed
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And As an "user0"
    And user "user0" created a folder "/test"
    And folder "/test" of user "user0" is shared with user "user1" with permissions 17
    And As an "user1"
    And creating a share with
      | path | /test |
      | shareType | 3 |
      | permissions | 1 |
    When Updating last share with
      | permissions | 15 |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"

  Scenario: Adding public upload to a shared folder as recipient is allowed with permissions
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And As an "user0"
    And user "user0" created a folder "/test"
    And folder "/test" of user "user0" is shared with user "user1" with permissions 31
    And As an "user1"
    And creating a share with
      | path | /test |
      | shareType | 3 |
      | permissions | 1 |
    When Updating last share with
      | permissions | 15 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

    Scenario: resharing using a public link with read only permissions is not allowed
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And As an "user0"
    And user "user0" created a folder "/test"
    And folder "/test" of user "user0" is shared with user "user1" with permissions 1
    And As an "user1"
    And creating a share with
      | path | /test |
      | shareType | 3 |
      | publicUpload | false |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"

  Scenario: resharing using a public link with read and write permissions only is not allowed
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And As an "user0"
    And user "user0" created a folder "/test"
    And folder "/test" of user "user0" is shared with user "user1" with permissions 15
    And As an "user1"
    And creating a share with
      | path | /test |
      | shareType | 3 |
      | publicUpload | false |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"