mirror of
https://github.com/owncloud/ocis
synced 2026-04-26 09:45:19 +02:00
46 KiB
46 KiB
Scenarios from OCIS API tests that are expected to fail with OCIS storage
The expected failures in this file are from features in the owncloud/ocis repo.
Downloading the archive of the resource (files | folder) using resource path is not possible
- apiArchiver/downloadByPath.feature:25
- apiArchiver/downloadByPath.feature:26
- apiArchiver/downloadByPath.feature:43
- apiArchiver/downloadByPath.feature:44
- apiArchiver/downloadByPath.feature:47
- apiArchiver/downloadByPath.feature:73
- apiArchiver/downloadByPath.feature:171
- apiArchiver/downloadByPath.feature:172
PATCH request for TUS upload with wrong checksum gives incorrect response
- apiSpacesShares/shareUploadTUS.feature:297
- apiSpacesShares/shareUploadTUS.feature:317
- apiSpacesShares/shareUploadTUS.feature:398
Settings service user can list other peoples assignments
A User can get information of another user with Graph API
- apiGraphUser/getUser.feature:56
- apiGraphUser/getUser.feature:57
- apiGraphUser/getUser.feature:58
- apiGraphUser/getUser.feature:59
- apiGraphUser/getUser.feature:60
- apiGraphUser/getUser.feature:61
- apiGraphUser/getUser.feature:62
- apiGraphUser/getUser.feature:63
- apiGraphUser/getUser.feature:64
- apiGraphUser/getUser.feature:65
- apiGraphUser/getUser.feature:66
- apiGraphUser/getUser.feature:67
- apiGraphUser/getUser.feature:362
- apiGraphUser/getUser.feature:363
- apiGraphUser/getUser.feature:364
- apiGraphUser/getUser.feature:365
- apiGraphUser/getUser.feature:366
- apiGraphUser/getUser.feature:367
- apiGraphUser/getUser.feature:368
- apiGraphUser/getUser.feature:369
- apiGraphUser/getUser.feature:370
- apiGraphUser/getUser.feature:371
- apiGraphUser/getUser.feature:372
- apiGraphUser/getUser.feature:373
- apiGraphUser/getUser.feature:388
- apiGraphUser/getUser.feature:389
- apiGraphUser/getUser.feature:390
Normal user can get expanded members information of a group
- apiGraphGroup/getGroup.feature:399
- apiGraphGroup/getGroup.feature:400
- apiGraphGroup/getGroup.feature:401
- apiGraphGroup/getGroup.feature:460
- apiGraphGroup/getGroup.feature:461
- apiGraphGroup/getGroup.feature:462
- apiGraphGroup/getGroup.feature:508
- apiGraphGroup/getGroup.feature:509
- apiGraphGroup/getGroup.feature:510
Same users can be added in a group multiple time
Users are added in a group with wrong host in host-part of user
Adding the same user as multiple members in a single request results in listing the same user twice in the group
Shared file locking is not possible using different path
- apiLocks/lockFiles.feature:185
- apiLocks/lockFiles.feature:186
- apiLocks/lockFiles.feature:187
- apiLocks/lockFiles.feature:309
- apiLocks/lockFiles.feature:310
- apiLocks/lockFiles.feature:311
- apiLocks/lockFiles.feature:364
- apiLocks/lockFiles.feature:365
- apiLocks/lockFiles.feature:366
- apiLocks/lockFiles.feature:367
- apiLocks/lockFiles.feature:368
- apiLocks/lockFiles.feature:369
- apiLocks/lockFiles.feature:399
- apiLocks/lockFiles.feature:400
- apiLocks/lockFiles.feature:401
- apiLocks/lockFiles.feature:402
- apiLocks/lockFiles.feature:403
- apiLocks/lockFiles.feature:404
- apiLocks/unlockFiles.feature:62
- apiLocks/unlockFiles.feature:63
- apiLocks/unlockFiles.feature:64
- apiLocks/unlockFiles.feature:171
- apiLocks/unlockFiles.feature:172
- apiLocks/unlockFiles.feature:173
- apiLocks/unlockFiles.feature:174
- apiLocks/unlockFiles.feature:175
- apiLocks/unlockFiles.feature:176
- apiLocks/unlockFiles.feature:199
- apiLocks/unlockFiles.feature:200
- apiLocks/unlockFiles.feature:201
- apiLocks/unlockFiles.feature:202
- apiLocks/unlockFiles.feature:203
- apiLocks/unlockFiles.feature:204
- apiLocks/unlockFiles.feature:227
- apiLocks/unlockFiles.feature:228
- apiLocks/unlockFiles.feature:229
- apiLocks/unlockFiles.feature:230
- apiLocks/unlockFiles.feature:231
- apiLocks/unlockFiles.feature:232
Folders can be locked and locking works partially
- apiLocks/lockFiles.feature:443
- apiLocks/lockFiles.feature:444
- apiLocks/lockFiles.feature:445
- apiLocks/lockFiles.feature:446
- apiLocks/lockFiles.feature:447
- apiLocks/lockFiles.feature:448
- apiLocks/lockFiles.feature:417
- apiLocks/lockFiles.feature:418
- apiLocks/lockFiles.feature:419
- apiLocks/lockFiles.feature:420
- apiLocks/lockFiles.feature:421
- apiLocks/lockFiles.feature:422
Anonymous users can unlock a file shared to them through a public link if they get the lock token
- apiLocks/unlockFiles.feature:42
- apiLocks/unlockFiles.feature:43
- apiLocks/unlockFiles.feature:44
- apiLocks/unlockFiles.feature:45
- apiLocks/unlockFiles.feature:46
- apiLocks/unlockFiles.feature:47
Trying to unlock a shared file with sharer's lock token gives 500
- apiLocks/unlockFiles.feature:115
- apiLocks/unlockFiles.feature:116
- apiLocks/unlockFiles.feature:117
- apiLocks/unlockFiles.feature:118
- apiLocks/unlockFiles.feature:119
- apiLocks/unlockFiles.feature:120
- apiLocks/unlockFiles.feature:143
- apiLocks/unlockFiles.feature:144
- apiLocks/unlockFiles.feature:145
- apiLocks/unlockFiles.feature:146
- apiLocks/unlockFiles.feature:147
- apiLocks/unlockFiles.feature:148
Anonymous user trying lock a file shared to them through a public link gives 405
- apiLocks/lockFiles.feature:532
- apiLocks/lockFiles.feature:533
- apiLocks/lockFiles.feature:534
- apiLocks/lockFiles.feature:535
- apiLocks/lockFiles.feature:554
- apiLocks/lockFiles.feature:555
- apiLocks/lockFiles.feature:556
- apiLocks/lockFiles.feature:557
blocksDownload link type is not implemented yet (sharing-ng)
- apiSharingNgItemLinkShare/createItemLinkShare.feature:109
- apiSharingNgItemLinkShare/createItemLinkShare.feature:209
- apiSharingNgItemLinkShare/createItemLinkShare.feature:311
- apiSharingNgItemLinkShare/createItemLinkShare.feature:411
- apiSharingNgItemLinkShare/createLinkShareWithoutPasswordEnforce.feature:49
- apiSharingNgItemLinkShare/createLinkShareWithoutPasswordEnforce.feature:85
- apiSharingNgItemLinkShare/createLinkShareWithoutPasswordEnforce.feature:150
- apiSharingNgItemLinkShare/createLinkShareWithoutPasswordEnforce.feature:188
- apiSharingNgLinkShareManagement/updateItemLinkShare.feature:73
- apiSharingNgLinkShareManagement/updateItemLinkShare.feature:75
- apiSharingNgLinkShareManagement/updateItemLinkShare.feature:76
- apiSharingNgLinkShareManagement/updateItemLinkShare.feature:77
- apiSharingNgLinkShareManagement/updateItemLinkShare.feature:143
- apiSharingNgLinkShareManagement/updateItemLinkShare.feature:406
- apiSharingNgLinkShareManagement/updateItemLinkShare.feature:798
- apiSharingNgDriveLinkShare/createDriveLinkShare.feature:106
- apiSharingNgDriveLinkShare/createDriveLinkShare.feature:204
- apiSharingNgDriveLinkShare/createDriveLinkShare.feature:384
- apiSharingNgDriveLinkShare/createDriveLinkShare.feature:426
- apiSharingNgLinkShareManagement/deleteLinkShare.feature:27
- apiSharingNgLinkShareManagement/deleteLinkShare.feature:43
- apiSharingNgLinkShareManagement/deleteLinkShare.feature:63
- apiSharingNgLinkShareManagement/deleteLinkShare.feature:81
- apiSharingNgDriveInvitation/removeAccessToDrive.feature:177
- apiSharingNgDriveInvitation/removeAccessToDrive.feature:206
- apiSharingNgDriveInvitation/removeAccessToDrive.feature:236
sharee (editor role) MOVE a file by file-id into shared sub-folder returns 502
MOVE a file into same folder with same name returns 404 instead of 403
- apiSpacesShares/moveSpaces.feature:69
- apiSpacesShares/moveSpaces.feature:70
- apiSpacesShares/moveSpaces.feature:416
- apiSpacesDavOperation/moveByFileId.feature:61
- apiSpacesDavOperation/moveByFileId.feature:174
- apiSpacesDavOperation/moveByFileId.feature:175
- apiSpacesDavOperation/moveByFileId.feature:176
- apiSpacesDavOperation/moveByFileId.feature:393
OCM. admin cannot get federated users if he hasn't connection with them
OCM. federated connection is not dropped when one of the users deletes the connection
OCM. server crash after deleting share for ocm user
same href in REPORT request for all dav-path-version
- apiSearch1/dateSearch.feature:17
- apiSearch1/dateSearch.feature:18
- apiSearch1/search.feature:41
- apiSearch1/search.feature:42
- apiSearch1/search.feature:69
- apiSearch1/search.feature:70
- apiSearch1/search.feature:196
- apiSearch1/search.feature:197
- apiSearch1/search.feature:220
- apiSearch1/search.feature:221
- apiSearch1/search.feature:241
- apiSearch1/search.feature:242
- apiSearch1/search.feature:260
- apiSearch1/search.feature:259
- apiSearch1/search.feature:277
- apiSearch1/search.feature:278
- apiSearch1/search.feature:301
- apiSearch1/search.feature:302
- apiSearch1/search.feature:353
- apiSearch1/search.feature:354
- apiSearch2/tagSearch.feature:34
- apiSearch2/tagSearch.feature:35
- apiSearch2/tagSearch.feature:62
- apiSearch2/tagSearch.feature:63
- apiSearch2/tagSearch.feature:83
- apiSearch2/tagSearch.feature:84
- apiSearch2/tagSearch.feature:106
- apiSearch2/tagSearch.feature:107
- apiSearch2/tagSearch.feature:136
- apiSearch2/tagSearch.feature:137
- apiSearch2/tagSearch.feature:170
- apiSearch2/tagSearch.feature:171
- apiSearch2/tagSearch.feature:206
- apiSearch2/tagSearch.feature:207
- apiSearch2/tagSearch.feature:225
- apiSearch2/tagSearch.feature:226
- apiSearchContent/contentSearch.feature:25
- apiSearchContent/contentSearch.feature:26
- apiSearchContent/contentSearch.feature:49
- apiSearchContent/contentSearch.feature:50
- apiSearchContent/contentSearch.feature:82
- apiSearchContent/contentSearch.feature:83
- apiSearchContent/contentSearch.feature:110
- apiSearchContent/contentSearch.feature:111
- apiSearchContent/contentSearch.feature:129
- apiSearchContent/contentSearch.feature:130
- apiSearchContent/contentSearch.feature:146
- apiSearchContent/contentSearch.feature:147
- apiSearchContent/contentSearch.feature:162
- apiSearchContent/contentSearch.feature:163
- apiSearchContent/contentSearch.feature:185
- apiSearchContent/contentSearch.feature:186
- apiSearchContent/contentSearch.feature:214
- apiSearchContent/contentSearch.feature:215
- apiSearchContent/contentSearch.feature:266
- apiSearchContent/contentSearch.feature:267
Readiness check for some services returns 500 status code
- apiServiceAvailability/serviceAvailabilityCheck.feature:111
- apiServiceAvailability/serviceAvailabilityCheck.feature:120
- apiServiceAvailability/serviceAvailabilityCheck.feature:131
[OCM] Hide & Enable Sync fail with received federated shares
[OCM] federated user trying to download file shared with permissions role Secure Viewer returns 500 status code
Commented out when backport the release-7.1.1 to master
Delete user containing + in username returns 404 but user gets deleted
OCM. delete-accepted-user endpoint always returns 200
- apiOcm/deleteFederatedConnections.feature:123
- apiOcm/deleteFederatedConnections.feature:130
- apiOcm/deleteFederatedConnections.feature:142
server returns status code 500 when creating token for non-existent user (Impersonation)
Server returns status code 500 when deleting auth-app token of a different user
[Sharing NG] sharedByMe endpoint is missing data for drives shared via link
Missing shareid on response of a PROPFIND on the sharejail root
- apiContract/propfindShares.feature:170
- apiContract/propfindShares.feature:171
- apiContract/propfindShares.feature:172
Folder shared with Secure view can be downloaded.
PROPFIND request to resource shared with user when deleted retains it's oc:share-type property
- apiContract/propfindShares.feature:194
- apiContract/propfindShares.feature:195
- apiContract/propfindShares.feature:196
- apiContract/propfindShares.feature:197
- apiContract/propfindShares.feature:198
- apiContract/propfindShares.feature:199
- apiContract/propfindShares.feature:223
- apiContract/propfindShares.feature:224
Creation date is missing for space members
- apiSharingNgPermissions/listPermissions.feature:874
- apiSharingNgPermissions/listPermissions.feature:1548
- apiSharingNgPermissions/listPermissions.feature:1549
- apiSharingNgPermissions/listPermissions.feature:1550
- apiSharingNgPermissions/listPermissions.feature:2263
Lost permission when received multiple shares on the same resource
Activity. No activity for copying a zero byte file
Activity. no event for deleting a file using file-id
Uploaders are not allowed to MOVE
Shares drive can be shared via link share with Internal role using permissions endpoint
Activities. no event for restoring file
Note: always have an empty line at the end of this file. The bash script that processes this file requires that the last line has a newline on the end.