25 KiB
Scenarios from ownCloud10 core API tests that are expected to fail with OCIS storage while running with the Graph API
The expected failures in this file are from features in the owncloud/ocis repo.
File
Basic file management like up and download, move, copy, properties, trash, versions and chunking.
Custom dav properties with namespaces are rendered incorrectly
ocdav: double-check the webdav property parsing when custom namespaces are used
- coreApiWebdavProperties/setFileProperties.feature:128
- coreApiWebdavProperties/setFileProperties.feature:129
- coreApiWebdavProperties/setFileProperties.feature:130
file versions do not report the version author
- coreApiVersions/fileVersionAuthor.feature:14
- coreApiVersions/fileVersionAuthor.feature:60
- coreApiVersions/fileVersionAuthor.feature:92
- coreApiVersions/fileVersionAuthor.feature:123
- coreApiVersions/fileVersionAuthor.feature:161
- coreApiVersions/fileVersionAuthor.feature:193
- coreApiVersions/fileVersionAuthor.feature:229
- coreApiVersions/fileVersionAuthor.feature:274
- coreApiVersions/fileVersionAuthor.feature:356
- coreApiVersions/fileVersionAuthor.feature:435
- coreApiVersions/fileVersionAuthor.feature:466
Sync
Synchronization features like etag propagation, setting mtime and locking files
Uploading an old method chunked file with checksum should fail using new DAV path
- coreApiMain/checksums.feature:233
- coreApiMain/checksums.feature:234
- coreApiMain/checksums.feature:235
Share
d:quota-available-bytes in dprop of PROPFIND give wrong response value
- coreApiWebdavProperties/getQuota.feature:57
- coreApiWebdavProperties/getQuota.feature:58
- coreApiWebdavProperties/getQuota.feature:59
- coreApiWebdavProperties/getQuota.feature:73
- coreApiWebdavProperties/getQuota.feature:74
- coreApiWebdavProperties/getQuota.feature:75
deleting a file inside a received shared folder is moved to the trash-bin of the sharer not the receiver
- coreApiTrashbin/trashbinSharingToShares.feature:54
- coreApiTrashbin/trashbinSharingToShares.feature:55
- coreApiTrashbin/trashbinSharingToShares.feature:56
- coreApiTrashbin/trashbinSharingToShares.feature:83
- coreApiTrashbin/trashbinSharingToShares.feature:84
- coreApiTrashbin/trashbinSharingToShares.feature:85
- coreApiTrashbin/trashbinSharingToShares.feature:142
- coreApiTrashbin/trashbinSharingToShares.feature:143
- coreApiTrashbin/trashbinSharingToShares.feature:144
- coreApiTrashbin/trashbinSharingToShares.feature:202
- coreApiTrashbin/trashbinSharingToShares.feature:203
Other
API, search, favorites, config, capabilities, not existing endpoints, CORS and others
sending MKCOL requests to another or non-existing user's webDav endpoints as normal user should return 404
ocdav: api compatibility, return correct status code
trying to lock file of another user gives http 500
Missing properties in REPORT response, REPORT response has different date format for d:getlastmodified, d:getetag property has empty value in REPORT response
- coreApiWebdavOperations/search.feature:180
- coreApiWebdavOperations/search.feature:181
- coreApiWebdavOperations/search.feature:182
- coreApiWebdavOperations/search.feature:208
- coreApiWebdavOperations/search.feature:209
- coreApiWebdavOperations/search.feature:210
Support for favorites
- coreApiFavorites/favorites.feature:101
- coreApiFavorites/favorites.feature:102
- coreApiFavorites/favorites.feature:103
- coreApiFavorites/favorites.feature:124
- coreApiFavorites/favorites.feature:125
- coreApiFavorites/favorites.feature:126
- coreApiFavorites/favorites.feature:189
- coreApiFavorites/favorites.feature:190
- coreApiFavorites/favorites.feature:191
- coreApiFavorites/favorites.feature:145
- coreApiFavorites/favorites.feature:146
- coreApiFavorites/favorites.feature:147
- coreApiFavorites/favorites.feature:174
- coreApiFavorites/favorites.feature:175
- coreApiFavorites/favorites.feature:176
- coreApiFavorites/favoritesSharingToShares.feature:91
- coreApiFavorites/favoritesSharingToShares.feature:92
- coreApiFavorites/favoritesSharingToShares.feature:93
WWW-Authenticate header for unauthenticated requests is not clear
PATCH request for TUS upload with wrong checksum gives incorrect response
- coreApiWebdavUploadTUS/checksums.feature:74
- coreApiWebdavUploadTUS/checksums.feature:75
- coreApiWebdavUploadTUS/checksums.feature:76
- coreApiWebdavUploadTUS/checksums.feature:77
- coreApiWebdavUploadTUS/checksums.feature:79
- coreApiWebdavUploadTUS/checksums.feature:78
- coreApiWebdavUploadTUS/checksums.feature:147
- coreApiWebdavUploadTUS/checksums.feature:148
- coreApiWebdavUploadTUS/checksums.feature:149
- coreApiWebdavUploadTUS/checksums.feature:192
- coreApiWebdavUploadTUS/checksums.feature:193
- coreApiWebdavUploadTUS/checksums.feature:194
- coreApiWebdavUploadTUS/checksums.feature:195
- coreApiWebdavUploadTUS/checksums.feature:196
- coreApiWebdavUploadTUS/checksums.feature:197
- coreApiWebdavUploadTUS/checksums.feature:240
- coreApiWebdavUploadTUS/checksums.feature:241
- coreApiWebdavUploadTUS/checksums.feature:242
- coreApiWebdavUploadTUS/checksums.feature:243
- coreApiWebdavUploadTUS/checksums.feature:244
- coreApiWebdavUploadTUS/checksums.feature:245
- coreApiWebdavUploadTUS/uploadToShare.feature:255
- coreApiWebdavUploadTUS/uploadToShare.feature:256
- coreApiWebdavUploadTUS/uploadToShare.feature:279
- coreApiWebdavUploadTUS/uploadToShare.feature:280
- coreApiWebdavUploadTUS/uploadToShare.feature:375
- coreApiWebdavUploadTUS/uploadToShare.feature:376
Renaming resource to banned name is allowed in spaces webdav
- coreApiWebdavMove2/moveFile.feature:143
- coreApiWebdavMove1/moveFolder.feature:36
- coreApiWebdavMove1/moveFolder.feature:50
- coreApiWebdavMove1/moveFolder.feature:64
Trying to delete other user's trashbin item returns 409 for spaces path instead of 404
MOVE a file into same folder with same name returns 404 instead of 403
- coreApiWebdavMove2/moveFile.feature:100
- coreApiWebdavMove2/moveFile.feature:101
- coreApiWebdavMove2/moveFile.feature:102
- coreApiWebdavMove1/moveFolder.feature:217
- coreApiWebdavMove1/moveFolder.feature:218
- coreApiWebdavMove1/moveFolder.feature:219
- coreApiWebdavMove2/moveShareOnOcis.feature:334
- coreApiWebdavMove2/moveShareOnOcis.feature:337
- coreApiWebdavMove2/moveShareOnOcis.feature:340
COPY file/folder to same name is possible (but 500 code error for folder with spaces path)
- coreApiSharePublicLink2/copyFromPublicLink.feature:198
- coreApiWebdavProperties/copyFile.feature:1094
- coreApiWebdavProperties/copyFile.feature:1095
- coreApiWebdavProperties/copyFile.feature:1096
same href in REPORT request for all dav-path-version
- coreApiWebdavOperations/search.feature:42
- coreApiWebdavOperations/search.feature:43
- coreApiWebdavOperations/search.feature:60
- coreApiWebdavOperations/search.feature:61
- coreApiWebdavOperations/search.feature:79
- coreApiWebdavOperations/search.feature:80
- coreApiWebdavOperations/search.feature:110
- coreApiWebdavOperations/search.feature:111
- coreApiWebdavOperations/search.feature:130
- coreApiWebdavOperations/search.feature:131
- coreApiWebdavOperations/search.feature:151
- coreApiWebdavOperations/search.feature:152
- coreApiWebdavOperations/search.feature:229
- coreApiWebdavOperations/search.feature:230
Trying to restore personal file to file of share received folder returns 403 but the share file is deleted (new dav path)
Uploading with the same mtime and filename causes "internal server errors"
- coreApiWebdavUpload/uploadFile.feature:400
- coreApiWebdavUpload/uploadFile.feature:401
- coreApiWebdavUpload/uploadFile.feature:402
- coreApiWebdavUploadTUS/uploadFileMtime.feature:79
- coreApiWebdavUploadTUS/uploadFileMtime.feature:80
- coreApiWebdavUploadTUS/uploadFileMtime.feature:81
Won't fix
Not everything needs to be implemented for ocis. While the oc10 testsuite covers these things we are not looking at them right now.
- The
OC-LazyOpsheader is no longer supported by the client, implementing this is not necessary for a first production release. We plan to have an upload state machine to visualize the state of a file, see https://github.com/owncloud/ocis/issues/214 - Blacklisted ignored files are no longer required because ocis can handle
.htaccessfiles without security implications introduced by serving user provided files with apache.
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.