Files
opencloud/tests/acceptance/expected-failures-API-on-EOS-storage.md
Jörn Friedrich Dreyer 40eec3460b clarify expected failures
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
2021-03-10 12:15:54 +00:00

168 KiB

Scenarios from ownCloud10 core API tests that are expected to fail with EOS storage

File

Basic file management like up and download, move, copy, properties, quota, trash, versions and chunking.

Propfind to trashbin endpoint requires UUID

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

uploading with old-chunking does not work

remote.php/dav/uploads endpoint does not exist

file id changes on every uploaded

renaming a resource does not work

file cannot contain ? character

Range Header is not obeyed when downloading a file

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

creating a folder that already exists returns an empty body

Some failing tests with Webdav custom properties

XML properties in webdav response not properly encoded

Sync

Checksum feature

Share

File and sync features in a shared scenario

listing received shares does not work

listing received shares does not work

XML properties in webdav response not properly encoded

elements cannot be favorited

Cannot set mtime on upload

groups endpoint does not exist

various sharing settings cannot be set (shareapi_auto_accept_share)

Accepting a share returns empty response

After accepting a share data in the received file cannot be downloaded

Response is empty when accepting a share

Sharing seems to work but does not work

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

Fields missing in delete share OCS response

file_target in share response

Shares not deleted when user is deleted

EOS no displayname owner when creating share

EOS mime-type is not set correctly when sharing

Sharee retrieves the information about a share -but gets response containing all the shares

Shares are not deleted when user is deleted

Delete shares from user when user is deleted

no displayname_owner shown when creating a share

when sharing a file mime-type field is set to application/octet-stream

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

cannot get ocs:share-permissions via WebDAV

Split old public API webdav tests from new public webdav tests

Range Header is not obeyed when downloading a file

Ability to return error messages in Webdav response bodies

Range Header is not obeyed when downloading a file

various sharing settings cannot be set

Prevent creating public share for the home root folder

Ability to return error messages in Webdav response bodies

Cannot set Mtime on upload

overwriting a file removes it's public links

listing received shares does not work

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

Set quota over settings

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

listing received shares does not work

trying to access a non-existing resource returns an empty body

Some failing tests with Webdav custom properties

filename cannot contain ?

uploading with old-chunking does not work

group support is not yet implemented

User Management

User and group management features

groups endpoint does not exist

OCS Provisioning API scenarios that fail

to be investigated and issues raised or comments added here

quota query

Other

no robots.txt available

There is no such thing like a "super-user"

no command equivalent to occ

ocs config endpoint only accessible by authorized users

HTTP 401 Unauthorized responses don't contain a body

users can access each-others data using the new webdav API

renaming a resource does not work

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

users can access each-others data using the new webdav API

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

Difference in response content of status.php and default capabilities

REPORT request not implemented

elements cannot be favorited

elements cannot be favorited

Authentication

Scenario Outline: Unauthenticated call

Previews via webDAV API tests fail on oCIS

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, implmenting this is not necessary for a first production release. We plan to have an uploed 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.

uploading with old-chunking does not work

remote.php/dav/uploads endpoint does not exist

renaming a resource does not work

blacklisted filenames like .htaccess & file.parts can be uploaded

blacklisted filenames like .htaccess & file.parts can be uploaded

blacklisted filenames like .htaccess & file.parts can be uploaded

system configuration options missing

blacklisted filenames like .htaccess & file.parts can be uploaded

blacklisted filenames like .htaccess & file.parts can be uploaded