-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Acceptance Tests for case-sensitive file names #32357
Labels
Comments
9 tasks
This was referenced Nov 20, 2018
10 tasks
Needs someone to look at what useful test scenarios remain to be added. |
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add acceptance test scenarios to API for things like:
renaming (moving) a file to be the same name, with just case different API acceptance tests for case-sensitive file move-rename #32358
moving a file (changing the name) "over the top" of an existing file that just has different case API acceptance tests for case-sensitive file move-rename #32358
moving a file (into another folder) "over the top" of an existing file that just has different case API acceptance tests for case-sensitive file move-rename #32358
deleting a file, when 2 files exist with different case deleting a file when 2 files exist with different case #33597
copying a file, when 2 files exist with different case add test copying a file when 2 files exist with different case #33605 Copying a file case sensitive test #33623
downloading a file, when 2 files exist with different case API acceptance tests for case-sensitive file move-rename #32358 the
Then
checks verify that download gets the correct case-sensitive filedo similar with folders add test deleting folder different case #33611
share to a sharee that has an existing file/folder with different case https://github.com/owncloud/core/pull/38950/files
mixup file and folder, e.g. file called MyStuff and folder called mystuff
make a few webUI acceptance test scenarios to smoketest the webUI behavior.
The text was updated successfully, but these errors were encountered: