opencloud/tests/acceptance/expected-failures-API-on-OCIS-storage.md

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.

copy personal space file to shared folder root result share in decline state

• coreApiWebdavProperties/copyFile.feature:261
• coreApiWebdavProperties/copyFile.feature:262

Custom dav properties with namespaces are rendered incorrectly

ocdav: double-check the webdav property parsing when custom namespaces are used

• coreApiWebdavProperties/setFileProperties.feature:32
• coreApiWebdavProperties/setFileProperties.feature:33
• coreApiWebdavProperties/setFileProperties.feature:34
• coreApiWebdavProperties/setFileProperties.feature:69
• coreApiWebdavProperties/setFileProperties.feature:67
• coreApiWebdavProperties/setFileProperties.feature:68

Cannot set custom webDav properties

• coreApiWebdavProperties/getFileProperties.feature:316
• coreApiWebdavProperties/getFileProperties.feature:317
• coreApiWebdavProperties/getFileProperties.feature:318
• coreApiWebdavProperties/getFileProperties.feature:348
• coreApiWebdavProperties/getFileProperties.feature:349
• coreApiWebdavProperties/getFileProperties.feature:350

file versions do not report the version author

• coreApiVersions/fileVersionAuthor.feature:15
• coreApiVersions/fileVersionAuthor.feature:61
• coreApiVersions/fileVersionAuthor.feature:93
• coreApiVersions/fileVersionAuthor.feature:124
• coreApiVersions/fileVersionAuthor.feature:162
• coreApiVersions/fileVersionAuthor.feature:194
• coreApiVersions/fileVersionAuthor.feature:230
• coreApiVersions/fileVersionAuthor.feature:275
• coreApiVersions/fileVersionAuthor.feature:357
• coreApiVersions/fileVersionAuthor.feature:436
• coreApiVersions/fileVersionAuthor.feature:467

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:219
• coreApiMain/checksums.feature:220

Share

copying a folder within a public link folder to folder with same name as an already existing file overwrites the parent file

• coreApiSharePublicLink2/copyFromPublicLink.feature:75
• coreApiSharePublicLink2/copyFromPublicLink.feature:105
• coreApiSharePublicLink2/copyFromPublicLink.feature:199
• coreApiSharePublicLink2/copyFromPublicLink.feature:200
• coreApiSharePublicLink2/copyFromPublicLink.feature:217
• coreApiSharePublicLink2/copyFromPublicLink.feature:218

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:53
• coreApiTrashbin/trashbinSharingToShares.feature:54
• coreApiTrashbin/trashbinSharingToShares.feature:81
• coreApiTrashbin/trashbinSharingToShares.feature:82
• coreApiTrashbin/trashbinSharingToShares.feature:138
• coreApiTrashbin/trashbinSharingToShares.feature:139
• coreApiTrashbin/trashbinSharingToShares.feature:196
• coreApiTrashbin/trashbinSharingToShares.feature:197

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

• coreApiAuth/webDavMKCOLAuth.feature:42
• coreApiAuth/webDavMKCOLAuth.feature:53

trying to lock file of another user gives http 200

• coreApiAuth/webDavLOCKAuth.feature:46
• coreApiAuth/webDavLOCKAuth.feature:58

send POST requests to another user's webDav endpoints as normal user

ocdav: api compatibility, return correct status code

• coreApiAuth/webDavPOSTAuth.feature:46
• coreApiAuth/webDavPOSTAuth.feature:55

Another users space literally does not exist because it is not listed as a space for him, 404 seems correct, expects 403

• coreApiAuth/webDavPUTAuth.feature:46
• coreApiAuth/webDavPUTAuth.feature:58

[old/new/spaces] In ocis and oc10, REPORT request response differently

• 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:124
• coreApiFavorites/favorites.feature:125
• coreApiFavorites/favorites.feature:189
• coreApiFavorites/favorites.feature:190

And other missing implementation of favorites

• 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:88
• coreApiFavorites/favoritesSharingToShares.feature:89

WWW-Authenticate header for unauthenticated requests is not clear

• coreApiWebdavOperations/refuseAccess.feature:21
• coreApiWebdavOperations/refuseAccess.feature:22

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:197
• coreApiWebdavUploadTUS/checksums.feature:196
• coreApiWebdavUploadTUS/checksums.feature:240
• coreApiWebdavUploadTUS/checksums.feature:241
• coreApiWebdavUploadTUS/checksums.feature:242
• coreApiWebdavUploadTUS/checksums.feature:243
• coreApiWebdavUploadTUS/checksums.feature:245
• coreApiWebdavUploadTUS/checksums.feature:244
• coreApiWebdavUploadTUS/optionsRequest.feature:10
• coreApiWebdavUploadTUS/optionsRequest.feature:25
• coreApiWebdavUploadTUS/uploadToShare.feature:226
• coreApiWebdavUploadTUS/uploadToShare.feature:227
• coreApiWebdavUploadTUS/uploadToShare.feature:250
• coreApiWebdavUploadTUS/uploadToShare.feature:251
• coreApiWebdavUploadTUS/uploadToShare.feature:274
• coreApiWebdavUploadTUS/uploadToShare.feature:275
• coreApiWebdavUploadTUS/uploadToShare.feature:317
• coreApiWebdavUploadTUS/uploadToShare.feature:318
• coreApiWebdavUploadTUS/uploadToShare.feature:369
• coreApiWebdavUploadTUS/uploadToShare.feature:370

TUS OPTIONS requests do not reply with TUS headers when invalid password

• coreApiWebdavUploadTUS/optionsRequest.feature:40
• coreApiWebdavUploadTUS/optionsRequest.feature:55

copying the file inside Shares folder returns 412

• coreApiWebdavProperties/copyFile.feature:408
• coreApiWebdavProperties/copyFile.feature:409
• coreApiWebdavProperties/copyFile.feature:410
• coreApiWebdavProperties/copyFile.feature:435
• coreApiWebdavProperties/copyFile.feature:436
• coreApiWebdavProperties/copyFile.feature:437
• coreApiWebdavProperties/copyFile.feature:238
• coreApiWebdavProperties/copyFile.feature:239

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-LazyOps header 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 .htaccess files without security implications introduced by serving user provided files with apache.

Blacklist files extensions

• coreApiWebdavProperties/copyFile.feature:107
• coreApiWebdavProperties/copyFile.feature:108
• coreApiWebdavProperties/copyFile.feature:109
• coreApiWebdavProperties/createFileFolder.feature:95
• coreApiWebdavProperties/createFileFolder.feature:96
• coreApiWebdavProperties/createFileFolder.feature:97
• coreApiWebdavUpload/uploadFile.feature:153
• coreApiWebdavUpload/uploadFile.feature:152
• coreApiWebdavUpload/uploadFile.feature:154
• coreApiWebdavMove2/moveFile.feature:177
• coreApiWebdavMove2/moveFile.feature:178
• coreApiWebdavMove2/moveFile.feature:143

Renaming resource to banned name is allowed in spaces webdav

• coreApiWebdavMove1/moveFolder.feature:36
• coreApiWebdavMove1/moveFolder.feature:50
• coreApiWebdavMove1/moveFolder.feature:64
• coreApiWebdavMove2/moveFile.feature:179

REPORT method on spaces returns an incorrect d:href response

• coreApiFavorites/favorites.feature:103
• coreApiFavorites/favorites.feature:126
• coreApiFavorites/favorites.feature:191

HTTP status code differ while deleting file of another user's trash bin

• coreApiTrashbin/trashbinDelete.feature:92

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:307
• coreApiWebdavMove2/moveShareOnOcis.feature:310

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.