-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cover all Webdav file operations #297
Comments
Well we can simply duplicate tests changing the stament |
What is left here? I am seeing:
Anything else needed? |
Indeed, seems I can't think of anything else. Maybe need to add cases where permissions are denied (already with move/copy) |
Note that these could have special implications when dealing with encryption and could reveal issues like owncloud/core#26978 (comment) |
Deletion, in trashbin feature file can have more cases. Deleting a folder, shared folder and so on. |
See owncloud/core#32366 for some "current" review of webDAV acceptance test scenarios. |
@PVince81 @DeepDiver1975 |
see issue #634 |
I think the above listed by Sergio are already nice to have a good base coverage. Most important is likely the upload with and without chunking, with and without overwrite on old and new endpoint. We might already have coverage for this in the api upload tests. |
I added this to the next sprint backlog, just so that someone can quickly look if there are ideas here for test scenarios that do not exist yet. Then if easy, add scenarios. Or if there is a lot do do then mention it here. |
Almost all of the operations are covered by API acceptance tests. The next step will be to add more tests to check the edge cases. More tests that can be added to Webdav file operations
|
The remaining things here have been put into separate issues. Closing |
In integration tests, we don't cover all file operations yet, only a few like move and copy.
It would be good to complete the list and also possibly do it for both the old and the new endpoint. (too bad behat doesn't have a way to run the same test with different data)
@SergioBertolinSG
The text was updated successfully, but these errors were encountered: