mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-01-06 04:09:40 -06:00
Code Issues Packages Projects Releases Wiki Activity
Files
88cb35483f28dc4e07402e10081b573fe1eb8ffe
opencloud/tests/acceptance/expected-failures-API-on-OCIS-storage.md
Prajwol Amatya 941ef59cc9 refactor scenario example table (#6694)
2023-07-04 15:54:16 +05:45

82 KiB
Raw Blame History

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.

Getting information about a folder overwritten by a file gives 500 error instead of 404

Custom dav properties with namespaces are rendered incorrectly

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

Cannot set custom webDav properties

file versions do not report the version author

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

Webdav LOCK operations

Share

File and sync features in a shared scenario

accepting matching name shared resources from different users/groups sets no serial identifiers on the resource name for the receiver

sharing the shares folder to users exits with different status code than in oc10 backend

file_target of an auto-renamed file is not correct directly after sharing

File deletion using dav gives unique string in filename in the trashbin

cannot share a folder with create permission

Resource with share permission create is readable for sharee

OCS error message for attempting to access share via share id as an unauthorized user is not informative

Listing shares via ocs API does not show path for parent folders

Public link enforce permissions

download previews of other users file

different error message detail for previews of folder

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

Upload-only shares must not overwrite but create a separate file

Set quota over settings

deleting a file inside a received shared folder is moved to the trash-bin of the sharer not the receiver

changing user quota gives ocs status 103 / Cannot set quota

not possible to move file into a received folder

Expiration date for shares is not implemented

Expiration date of user shares

Expiration date of group shares

Cannot move folder/file from one received share to another

Sharing folder and sub-folder with same user but different permission,the permission of sub-folder is not obeyed

Empty OCS response for a share create request using a disabled user

Edit user share response has a "name" field

Share lists deleted user as 'user'

deleting a share with wrong authentication returns OCS status 996 / HTTP 500

User Management

User and group management features

incorrect ocs(v2) status value when getting info of share that does not exist should be 404, gives 998

ocs: api compatibility, return correct status code

Other

API, search, favorites, config, capabilities, not existing endpoints, CORS and others

Ability to return error messages in Webdav response bodies

sending MKCOL requests to another user's webDav endpoints as normal user gives 404 instead of 403

ocdav: api compatibility, return correct status code

trying to lock file of another user gives http 200

send (MOVE,COPY) requests to another user's webDav endpoints as normal user gives 400 instead of 403

ocdav: api compatibility, return correct status code

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

ocdav: api compatibility, return correct status code

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

Using double slash in URL to access a folder gives 501 and other status codes

Difference in response content of status.php and default capabilities

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

Support for favorites

And other missing implementation of favorites

WWW-Authenticate header for unauthenticated requests is not clear

Request to edit non-existing user by authorized admin gets unauthorized in http response

Sharing a same file twice to the same group

PATCH request for TUS upload with wrong checksum gives incorrect response

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

Trying to accept a share with invalid ID gives incorrect OCS and HTTP status

Shares to deleted group listed in the response

copying the file inside Shares folder returns 404

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

cannot set blacklisted file names

Preview of text file with UTF content does not render correctly

Share path in the response is different between share states

Content-type is not multipart/byteranges when downloading file with Range Header

moveShareInsideAnotherShare behaves differently on oCIS than oC10

Renaming resource to banned name is allowed in spaces webdav

REPORT method on spaces returns an incorrect d:href response

Cannot disable the dav propfind depth infinity for resources

graph/users: enable/disable users

OCS status code zero

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

Default capabilities for normal user and admin user not same as in oC-core

sharing the shares folder to users exits with different status code than in oc10 backend

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.

Reference in New Issue View Git Blame Copy Permalink