Initial QSfera import
This commit is contained in:
Курнат Андрей
@@ -0,0 +1,504 @@
|
||||
Feature: move (rename) file
|
||||
As a user
|
||||
I want to be able to move and rename files
|
||||
So that I can manage my file system
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes
|
||||
|
||||
@smokeTest
|
||||
Scenario Outline: moving a file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0" to "textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/FOLDER/textfile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the following headers should match these regular expressions for user "Alice"
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/FOLDER/textfile0.txt" for user "Alice" should be "КуСфера test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@smokeTest
|
||||
Scenario Outline: moving and overwriting a file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0 v1" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0 v2" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 1" to "textfile1.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/textfile1.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And the following headers should match these regular expressions for user "Alice"
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/textfile1.txt" for user "Alice" should be "КуСфера test text file 0 v2"
|
||||
And the content of version index "1" of file "/textfile1.txt" for user "Alice" should be "КуСфера test text file 0 v1"
|
||||
And as "Alice" file "/textfile0.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: moving (renaming) a file to be only different case
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0" to "textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/TextFile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/textfile0.txt" should not exist
|
||||
And the content of file "/TextFile0.txt" for user "Alice" should be "КуСфера test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@smokeTest
|
||||
Scenario Outline: moving (renaming) a file to a file with only different case to an existing file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 1" to "textfile1.txt"
|
||||
When user "Alice" moves file "/textfile1.txt" to "/TextFile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/textfile0.txt" for user "Alice" should be "КуСфера test text file 0"
|
||||
And the content of file "/TextFile0.txt" for user "Alice" should be "КуСфера test text file 1"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: moving (renaming) a file to a file in a folder with only different case to an existing file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "PARENT"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file parent" to "PARENT/parent.txt"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 1" to "textfile1.txt"
|
||||
When user "Alice" moves file "/textfile1.txt" to "/PARENT/Parent.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/PARENT/parent.txt" for user "Alice" should be "КуСфера test text file parent"
|
||||
And the content of file "/PARENT/Parent.txt" for user "Alice" should be "КуСфера test text file 1"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-1976
|
||||
Scenario Outline: try to move a file into same folder with same name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file" to "testfile.txt"
|
||||
When user "Alice" moves file "testfile.txt" to "testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" the file with original path "testfile.txt" should not exist in the trashbin
|
||||
And the content of file "testfile.txt" for user "Alice" should be "КуСфера test text file"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: move a file to existing file name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "test file" to "testfile.txt"
|
||||
And user "Alice" has uploaded file with content "some content" to "lorem.txt"
|
||||
When user "Alice" moves file "testfile.txt" to "lorem.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" file "lorem.txt" should exist
|
||||
And the content of file "lorem.txt" for user "Alice" should be "test file"
|
||||
But as "Alice" file "testfile.txt" should not exist
|
||||
And as "Alice" the file with original path "lorem.txt" should exist in the trashbin
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: move file into a not-existing folder
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToMove.txt"
|
||||
When user "Alice" moves file "/fileToMove.txt" to "/not-existing/fileToMove.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "409"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-1295 @issue-2177 @issue-3099
|
||||
Scenario Outline: rename a file into an invalid filename
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToRename.txt"
|
||||
When user "Alice" moves file "/fileToRename.txt" to "/with\\backslash" using the WebDAV API
|
||||
Then the HTTP status code should be "400"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: checking file id after a move
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt"
|
||||
And user "Alice" has stored id of file "/textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/FOLDER/textfile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And user "Alice" file "/FOLDER/textfile0.txt" should have the previously stored id
|
||||
And user "Alice" should not see the following elements
|
||||
| /textfile0.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-1295 @issue-2177
|
||||
Scenario Outline: renaming a file to a path with extension .part should not be possible
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToRename.txt"
|
||||
When user "Alice" moves file "/fileToRename.txt" to "/welcome.part" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And user "Alice" should see the following elements
|
||||
| /welcome.part |
|
||||
But user "Alice" should not see the following elements
|
||||
| /fileToRename.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@sqliteDB
|
||||
Scenario Outline: renaming to a file with special characters
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 1" to "textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 2" to "textfile2.txt"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 3" to "textfile3.txt"
|
||||
When user "Alice" moves the following file using the WebDAV API
|
||||
| source | destination |
|
||||
| /textfile0.txt | *a@b#c$e%f&g* |
|
||||
| /textfile1.txt | 1 2 3##.## |
|
||||
| /textfile2.txt | file[2] |
|
||||
| /textfile3.txt | file [ 3 ] |
|
||||
Then the HTTP status code of responses on all endpoints should be "201"
|
||||
And the content of file "*a@b#c$e%f&g*" for user "Alice" should be "КуСфера test text file 0"
|
||||
And the content of file "1 2 3##.##" for user "Alice" should be "КуСфера test text file 1"
|
||||
And the content of file "file[2]" for user "Alice" should be "КуСфера test text file 2"
|
||||
And the content of file "file [ 3 ]" for user "Alice" should be "КуСфера test text file 3"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-1259
|
||||
#after fixing the issues merge this Scenario into the one above
|
||||
Scenario Outline: renaming to a file with question mark in its name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0" to "textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/#oc ab?cd=ef#" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/#oc ab?cd=ef#" for user "Alice" should be "КуСфера test text file 0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: renaming file with dots in the path
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "<folder-name>"
|
||||
And user "Alice" has uploaded file with content "uploaded content for file name ending with a dot" to "<folder-name>/<file-name>"
|
||||
When user "Alice" moves file "<folder-name>/<file-name>" to "<folder-name>/abc.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "<folder-name>/abc.txt" should exist
|
||||
Examples:
|
||||
| dav-path-version | folder-name | file-name |
|
||||
| old | /upload. | abc. |
|
||||
| old | /upload. | abc . |
|
||||
| old | /upload.1 | abc |
|
||||
| old | /upload...1.. | abc...txt.. |
|
||||
| old | /... | abcd.txt |
|
||||
| old | /..upload | ..abc |
|
||||
| new | /upload. | abc. |
|
||||
| new | /upload. | abc . |
|
||||
| new | /upload.1 | ..abc.txt |
|
||||
| new | /upload...1.. | abc...txt.. |
|
||||
| new | /... | ... |
|
||||
| new | /..upload | ..abc |
|
||||
| spaces | /upload. | abc. |
|
||||
| spaces | /upload. | abc . |
|
||||
| spaces | /upload.1 | abc |
|
||||
| spaces | /upload...1.. | abc...txt.. |
|
||||
| spaces | /... | abcd.txt |
|
||||
| spaces | /... | ... |
|
||||
|
||||
@smokeTest
|
||||
Scenario Outline: user tries to move a file that doesnt exist into a folder
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
When user "Alice" moves file "/doesNotExist.txt" to "/FOLDER/textfile0.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "404"
|
||||
And as "Alice" file "/FOLDER/textfile0.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@smokeTest
|
||||
Scenario Outline: user tries to rename a file that doesn't exist
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" moves file "/doesNotExist.txt" to "/exist.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "404"
|
||||
And as "Alice" file "/exist.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: moving a hidden file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
And user "Alice" has uploaded the following files with content "hidden file"
|
||||
| path |
|
||||
| .hidden_file101 |
|
||||
| /FOLDER/.hidden_file102 |
|
||||
When user "Alice" moves the following files using the WebDAV API
|
||||
| from | to |
|
||||
| .hidden_file101 | /FOLDER/.hidden_file101 |
|
||||
| /FOLDER/.hidden_file102 | .hidden_file102 |
|
||||
Then the HTTP status code of responses on all endpoints should be "201"
|
||||
And as "Alice" the following files should exist
|
||||
| path |
|
||||
| .hidden_file102 |
|
||||
| /FOLDER/.hidden_file101 |
|
||||
And the content of the following files for user "Alice" should be "hidden file"
|
||||
| path |
|
||||
| .hidden_file102 |
|
||||
| /FOLDER/.hidden_file101 |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: renaming to/from a hidden file
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded the following files with content "hidden file"
|
||||
| path |
|
||||
| .hidden_file101 |
|
||||
| hidden_file101.txt |
|
||||
When user "Alice" moves the following files using the WebDAV API
|
||||
| from | to |
|
||||
| .hidden_file101 | hidden_file102.txt |
|
||||
| hidden_file101.txt | .hidden_file102 |
|
||||
Then the HTTP status code of responses on all endpoints should be "201"
|
||||
And as "Alice" the following files should exist
|
||||
| path |
|
||||
| .hidden_file102 |
|
||||
| hidden_file102.txt |
|
||||
And the content of the following files for user "Alice" should be "hidden file"
|
||||
| path |
|
||||
| .hidden_file102 |
|
||||
| hidden_file102.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: moving a file (deep moves with various folder and file names)
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "<source-folder>"
|
||||
And user "Alice" has created folder "<destination-folder>"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0" to "/<source-folder>/<source-file>"
|
||||
When user "Alice" moves file "/<source-folder>/<source-file>" to "/<destination-folder>/<destination-file>" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the following headers should match these regular expressions for user "Alice"
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/<destination-folder>/<destination-file>" for user "Alice" should be "КуСфера test text file 0"
|
||||
Examples:
|
||||
| dav-path-version | source-folder | source-file | destination-folder | destination-file |
|
||||
| old | text | file.txt | 0 | file.txt |
|
||||
| old | text | file.txt | 1 | file.txt |
|
||||
| old | 0 | file.txt | text | file.txt |
|
||||
| old | 1 | file.txt | text | file.txt |
|
||||
| old | texta | 0 | textb | file.txt |
|
||||
| old | texta | 1 | textb | file.txt |
|
||||
| old | texta | file.txt | textb | 0 |
|
||||
| old | texta | file.txt | textb | 1 |
|
||||
| new | text | file.txt | 0 | file.txt |
|
||||
| new | text | file.txt | 1 | file.txt |
|
||||
| new | 0 | file.txt | text | file.txt |
|
||||
| new | 1 | file.txt | text | file.txt |
|
||||
| new | texta | 0 | textb | file.txt |
|
||||
| new | texta | 1 | textb | file.txt |
|
||||
| new | texta | file.txt | textb | 0 |
|
||||
| new | texta | file.txt | textb | 1 |
|
||||
| spaces | text | file.txt | 0 | file.txt |
|
||||
| spaces | text | file.txt | 1 | file.txt |
|
||||
| spaces | 0 | file.txt | text | file.txt |
|
||||
| spaces | 1 | file.txt | text | file.txt |
|
||||
| spaces | texta | 0 | textb | file.txt |
|
||||
| spaces | texta | 1 | textb | file.txt |
|
||||
| spaces | texta | file.txt | textb | 0 |
|
||||
| spaces | texta | file.txt | textb | 1 |
|
||||
|
||||
|
||||
Scenario Outline: moving a file from a folder to the root
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "<source-folder>"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0" to "/<source-folder>/<source-file>"
|
||||
When user "Alice" moves file "/<source-folder>/<source-file>" to "/<destination-file>" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the following headers should match these regular expressions for user "Alice"
|
||||
| ETag | /^"[a-f0-9:\.]{1,32}"$/ |
|
||||
And the content of file "/<destination-file>" for user "Alice" should be "КуСфера test text file 0"
|
||||
Examples:
|
||||
| dav-path-version | source-folder | source-file | destination-file |
|
||||
| old | 0 | file.txt | file.txt |
|
||||
| old | 1 | file.txt | file.txt |
|
||||
| old | texta | 0 | file.txt |
|
||||
| old | texta | 1 | file.txt |
|
||||
| old | texta | file.txt | 0 |
|
||||
| old | texta | file.txt | 1 |
|
||||
| new | 0 | file.txt | file.txt |
|
||||
| new | 1 | file.txt | file.txt |
|
||||
| new | texta | 0 | file.txt |
|
||||
| new | texta | 1 | file.txt |
|
||||
| new | texta | file.txt | 0 |
|
||||
| new | texta | file.txt | 1 |
|
||||
| spaces | 0 | file.txt | file.txt |
|
||||
| spaces | 1 | file.txt | file.txt |
|
||||
| spaces | texta | 0 | file.txt |
|
||||
| spaces | texta | 1 | file.txt |
|
||||
| spaces | texta | file.txt | 0 |
|
||||
| spaces | texta | file.txt | 1 |
|
||||
|
||||
|
||||
Scenario Outline: move a file of size zero byte
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/zerobyte.txt" to "/zerobyte.txt"
|
||||
And user "Alice" has created folder "/testZeroByte"
|
||||
When user "Alice" moves file "/zerobyte.txt" to "/testZeroByte/zerobyte.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/testZeroByte/zerobyte.txt" should exist
|
||||
And as "Alice" file "/zerobyte.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename a file of size zero byte
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/zerobyte.txt" to "/zerobyte.txt"
|
||||
When user "Alice" moves file "/zerobyte.txt" to "/rename_zerobyte.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/rename_zerobyte.txt" should exist
|
||||
And as "Alice" file "/zerobyte.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename file to/from special characters
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "test file" to <from-file-name>
|
||||
When user "Alice" moves file <from-file-name> to <to-file-name> using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file <to-file-name> should exist
|
||||
But as "Alice" file <from-file-name> should not exist
|
||||
Examples:
|
||||
| dav-path-version | from-file-name | to-file-name |
|
||||
| old | "testfile.txt" | "'single'quotes.txt" |
|
||||
| old | "testfile.txt" | '"double"quotes.txt' |
|
||||
| old | "testfile.txt" | "strängé नेपाली.txt" |
|
||||
| old | "testfile.txt" | "file,comma.txt" |
|
||||
| old | "testfile.txt" | " start with space.txt" |
|
||||
| old | "'single'quotes.txt" | "testfile.txt" |
|
||||
| old | '"double"quotes.txt' | "testfile.txt" |
|
||||
| old | "strängé नेपाली.txt" | "testfile.txt" |
|
||||
| old | "file,comma.txt" | "testfile.txt" |
|
||||
| old | " start with space.txt" | "testfile.txt" |
|
||||
| new | "testfile.txt" | "'single'quotes.txt" |
|
||||
| new | "testfile.txt" | '"double"quotes.txt' |
|
||||
| new | "testfile.txt" | "strängé नेपाली.txt" |
|
||||
| new | "testfile.txt" | "file,comma.txt" |
|
||||
| new | "testfile.txt" | " start with space.txt" |
|
||||
| new | "'single'quotes.txt" | "testfile.txt" |
|
||||
| new | '"double"quotes.txt' | "testfile.txt" |
|
||||
| new | "strängé नेपाली.txt" | "testfile.txt" |
|
||||
| new | "file,comma.txt" | "testfile.txt" |
|
||||
| new | " start with space.txt" | "testfile.txt" |
|
||||
| spaces | "testfile.txt" | "'single'quotes.txt" |
|
||||
| spaces | "testfile.txt" | '"double"quotes.txt' |
|
||||
| spaces | "testfile.txt" | "strängé नेपाली.txt" |
|
||||
| spaces | "testfile.txt" | "file,comma.txt" |
|
||||
| spaces | "testfile.txt" | " start with space.txt" |
|
||||
| spaces | "'single'quotes.txt" | "testfile.txt" |
|
||||
| spaces | '"double"quotes.txt' | "testfile.txt" |
|
||||
| spaces | "strängé नेपाली.txt" | "testfile.txt" |
|
||||
| spaces | "file,comma.txt" | "testfile.txt" |
|
||||
| spaces | " start with space.txt" | "testfile.txt" |
|
||||
|
||||
|
||||
Scenario Outline: try to rename file to name having white space at the end
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "test file" to "testfile.txt"
|
||||
When user "Alice" moves file "testfile.txt" to "space at end " using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "space at end" should exist
|
||||
But as "Alice" file "testfile.txt" should not exist
|
||||
And as "Alice" file "space at end " should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: try to rename file to . and ..
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "test file" to "testfile.txt"
|
||||
When user "Alice" moves file "testfile.txt" to "<file-name>" using the WebDAV API
|
||||
Then the HTTP status code should be "<http-status-code>"
|
||||
Examples:
|
||||
| dav-path-version | file-name | http-status-code |
|
||||
| old | /. | 409 |
|
||||
| old | /.. | 404 |
|
||||
| new | /. | 409 |
|
||||
| new | /.. | 404 |
|
||||
| spaces | /. | 409 |
|
||||
| spaces | /.. | 400 |
|
||||
|
||||
|
||||
Scenario Outline: rename a file to .htaccess
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file 0" to "textfile0.txt"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/.htaccess" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And user "Alice" should see the following elements
|
||||
| .htaccess |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
@@ -0,0 +1,266 @@
|
||||
Feature: move (rename) folder
|
||||
As a user
|
||||
I want to be able to move and rename folders
|
||||
So that I can quickly manage my file system
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes
|
||||
|
||||
|
||||
Scenario Outline: rename a folder
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "testFolder"
|
||||
When user "Alice" moves folder "testFolder" to "renamedFolder" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" folder "renamedFolder" should exist
|
||||
But as "Alice" folder "testFolder" should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-3099
|
||||
Scenario Outline: renaming a folder to a backslash should return an error
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "\" using the WebDAV API
|
||||
Then the HTTP status code should be "400"
|
||||
And user "Alice" should see the following elements
|
||||
| /testshare |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-3099
|
||||
Scenario Outline: renaming a folder beginning with a backslash should return an error
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "\testshare" using the WebDAV API
|
||||
Then the HTTP status code should be "400"
|
||||
And user "Alice" should see the following elements
|
||||
| /testshare |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-3099
|
||||
Scenario Outline: renaming a folder including a backslash encoded should return an error
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "/hola\hola" using the WebDAV API
|
||||
Then the HTTP status code should be "400"
|
||||
And user "Alice" should see the following elements
|
||||
| /testshare |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: move a folder into an other folder
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
And user "Alice" has created folder "/an-other-folder"
|
||||
When user "Alice" moves folder "/testshare" to "/an-other-folder/testshare" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And user "Alice" should not see the following elements
|
||||
| /testshare |
|
||||
And user "Alice" should see the following elements
|
||||
| /an-other-folder/testshare |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: move a folder into a nonexistent folder
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "/not-existing/testshare" using the WebDAV API
|
||||
Then the HTTP status code should be "409"
|
||||
And user "Alice" should see the following elements
|
||||
| /testshare |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: renaming folder with dots in the path
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "<folder-name>"
|
||||
And user "Alice" has uploaded file with content "uploaded content for file name ending with a dot" to "<folder-name>/abc.txt"
|
||||
When user "Alice" moves folder "<folder-name>" to "/uploadFolder" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/uploadFolder/abc.txt" for user "Alice" should be "uploaded content for file name ending with a dot"
|
||||
Examples:
|
||||
| dav-path-version | folder-name |
|
||||
| old | /upload. |
|
||||
| old | /upload.1 |
|
||||
| old | /upload...1.. |
|
||||
| old | /... |
|
||||
| old | /..upload |
|
||||
| new | /upload. |
|
||||
| new | /upload.1 |
|
||||
| new | /upload...1.. |
|
||||
| new | /... |
|
||||
| new | /..upload |
|
||||
| spaces | /upload. |
|
||||
| spaces | /upload.1 |
|
||||
| spaces | /upload...1.. |
|
||||
| spaces | /... |
|
||||
| spaces | /..upload |
|
||||
|
||||
@issue-3023
|
||||
Scenario Outline: moving a folder into a sub-folder of itself
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "PARENT"
|
||||
And user "Alice" has created folder "PARENT/CHILD"
|
||||
And user "Alice" has uploaded file with content "parent text" to "/PARENT/parent.txt"
|
||||
And user "Alice" has uploaded file with content "child text" to "/PARENT/CHILD/child.txt"
|
||||
When user "Alice" moves folder "/PARENT" to "/PARENT/CHILD/PARENT" using the WebDAV API
|
||||
Then the HTTP status code should be "409"
|
||||
And the content of file "/PARENT/parent.txt" for user "Alice" should be "parent text"
|
||||
And the content of file "/PARENT/CHILD/child.txt" for user "Alice" should be "child text"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename folder to/from special characters
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder <from-folder-name>
|
||||
When user "Alice" moves folder <from-folder-name> to <to-folder-name> using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" folder <to-folder-name> should exist
|
||||
But as "Alice" folder <from-folder-name> should not exist
|
||||
Examples:
|
||||
| dav-path-version | from-folder-name | to-folder-name |
|
||||
| old | "testFolder" | "'single'quotes" |
|
||||
| old | "testFolder" | '"double"quotes' |
|
||||
| old | "testFolder" | "strängé नेपाली folder" |
|
||||
| old | "testFolder" | "$%#?&@" |
|
||||
| old | "testFolder" | "Sample,Folder,With,Comma" |
|
||||
| old | "testFolder" | " start with space" |
|
||||
| old | "testFolder" | "renamed.part" |
|
||||
| old | "'single'quotes" | "testFolder" |
|
||||
| old | '"double"quotes' | "testFolder" |
|
||||
| old | "strängé नेपाली folder" | "testFolder" |
|
||||
| old | "$%#?&@" | "testFolder" |
|
||||
| old | "Sample,Folder,With,Comma" | "testFolder" |
|
||||
| old | " start with space" | "testFolder" |
|
||||
| old | "renamed.part" | "testFolder" |
|
||||
| new | "testFolder" | "'single'quotes" |
|
||||
| new | "testFolder" | '"double"quotes' |
|
||||
| new | "testFolder" | "strängé नेपाली folder" |
|
||||
| new | "testFolder" | "$%#?&@" |
|
||||
| new | "testFolder" | "Sample,Folder,With,Comma" |
|
||||
| new | "testFolder" | " start with space" |
|
||||
| new | "testFolder" | "renamed.part" |
|
||||
| new | "'single'quotes" | "testFolder" |
|
||||
| new | '"double"quotes' | "testFolder" |
|
||||
| new | "strängé नेपाली folder" | "testFolder" |
|
||||
| new | "$%#?&@" | "testFolder" |
|
||||
| new | "Sample,Folder,With,Comma" | "testFolder" |
|
||||
| new | " start with space" | "testFolder" |
|
||||
| new | "renamed.part" | "testFolder" |
|
||||
| spaces | "testFolder" | "'single'quotes" |
|
||||
| spaces | "testFolder" | '"double"quotes' |
|
||||
| spaces | "testFolder" | "strängé नेपाली folder" |
|
||||
| spaces | "testFolder" | "$%#?&@" |
|
||||
| spaces | "testFolder" | "Sample,Folder,With,Comma" |
|
||||
| spaces | "testFolder" | " start with space" |
|
||||
| spaces | "testFolder" | "renamed.part" |
|
||||
| spaces | "'single'quotes" | "testFolder" |
|
||||
| spaces | '"double"quotes' | "testFolder" |
|
||||
| spaces | "strängé नेपाली folder" | "testFolder" |
|
||||
| spaces | "$%#?&@" | "testFolder" |
|
||||
| spaces | "Sample,Folder,With,Comma" | "testFolder" |
|
||||
| spaces | " start with space" | "testFolder" |
|
||||
| spaces | "renamed.part" | "testFolder" |
|
||||
|
||||
|
||||
Scenario Outline: try to rename folder to name having white space at the end
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "testFolder"
|
||||
When user "Alice" moves folder "testFolder" to "space at end " using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" folder "space at end" should exist
|
||||
But as "Alice" folder "testFolder" should not exist
|
||||
And as "Alice" folder "space at end " should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-1976
|
||||
Scenario Outline: try to rename folder to same name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "testFolder"
|
||||
When user "Alice" moves folder "testFolder" to "testFolder" using the WebDAV API
|
||||
Then the HTTP status code should be "404"
|
||||
And as "Alice" the folder with original path "testFolder" should not exist in the trashbin
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename a folder to existing folder name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "testFolder"
|
||||
And user "Alice" has uploaded file with content "some content" to "testFolder/lorem.txt"
|
||||
And user "Alice" has created folder "renamedFolder"
|
||||
When user "Alice" moves folder "testFolder" to "renamedFolder" using the WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" folder "renamedFolder" should exist
|
||||
And the content of file "renamedFolder/lorem.txt" for user "Alice" should be "some content"
|
||||
And as "Alice" the folder with original path "renamedFolder" should exist in the trashbin
|
||||
But as "Alice" folder "testFolder" should not exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: try to rename folder to . and ..
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "testFolder"
|
||||
When user "Alice" moves folder "testFolder" to "<folder-name>" using the WebDAV API
|
||||
Then the HTTP status code should be "<http-status-code>"
|
||||
Examples:
|
||||
| dav-path-version | folder-name | http-status-code |
|
||||
| old | /. | 409 |
|
||||
| old | /.. | 404 |
|
||||
| new | /. | 409 |
|
||||
| new | /.. | 404 |
|
||||
| spaces | /. | 409 |
|
||||
| spaces | /.. | 400 |
|
||||
|
||||
|
||||
Scenario Outline: rename a folder to .htaccess
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "/.htaccess" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And user "Alice" should see the following elements
|
||||
| /.htaccess |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
@@ -0,0 +1,340 @@
|
||||
@skipOnReva
|
||||
Feature: move (rename) file
|
||||
As a user
|
||||
I want to be able to move and rename files
|
||||
So that I can manage my file system
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes
|
||||
|
||||
|
||||
Scenario Outline: sharer moves a file into a shared folder
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
And user "Brian" has uploaded file with content "test data" to "/testfile.txt"
|
||||
When user "Brian" moves file "/testfile.txt" to "testshare/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/Shares/testshare/testfile.txt" for user "Alice" should be "test data"
|
||||
And the content of file "/testshare/testfile.txt" for user "Brian" should be "test data"
|
||||
And as "Brian" file "/testfile.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: sharee tries to move a file into a shared folder
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
And user "Alice" has uploaded file with content "test data" to "/testfile.txt"
|
||||
When user "Alice" moves file "/testfile.txt" to "Shares/testshare/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "502"
|
||||
And as "Alice" file "Shares/testshare/testfile.txt" should not exist
|
||||
And as "Brian" file "testshare/testfile.txt" should not exist
|
||||
But as "Alice" file "/testfile.txt" should exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: moving a file out of a shared folder as the sharer
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has uploaded file with content "test data" to "/testshare/testfile.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Brian" moves file "/testshare/testfile.txt" to "/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/testfile.txt" for user "Brian" should be "test data"
|
||||
And as "Alice" file "/Shares/testshare/testfile.txt" should not exist
|
||||
And as "Brian" file "/testshare/testfile.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: moving a file out of a shared folder as the sharee
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has uploaded file with content "test data" to "/testshare/testfile.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Alice" moves file "/Shares/testshare/testfile.txt" to "/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "502"
|
||||
And as "Alice" file "/Shares/testshare/testfile.txt" should exist
|
||||
And as "Brian" file "/testshare/testfile.txt" should exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: moving a folder into a shared folder the sharer
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
And user "Brian" has created folder "/testsubfolder"
|
||||
And user "Brian" has uploaded file with content "test data" to "/testsubfolder/testfile.txt"
|
||||
When user "Brian" moves folder "/testsubfolder" to "testshare/testsubfolder" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/Shares/testshare/testsubfolder/testfile.txt" for user "Alice" should be "test data"
|
||||
And the content of file "/testshare/testsubfolder/testfile.txt" for user "Brian" should be "test data"
|
||||
And as "Brian" file "/testsubfolder" should not exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: moving a folder into a shared folder as the sharee
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
And user "Alice" has created folder "/testsubfolder"
|
||||
And user "Alice" has uploaded file with content "test data" to "/testsubfolder/testfile.txt"
|
||||
When user "Alice" moves folder "/testsubfolder" to "Shares/testshare/testsubfolder" using the WebDAV API
|
||||
Then the HTTP status code should be "502"
|
||||
And as "Alice" folder "/Shares/testshare/testsubfolder" should not exist
|
||||
And as "Brian" folder "/testshare/testsubfolder" should not exist
|
||||
But as "Alice" folder "/testsubfolder" should exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: moving a folder out of a shared folder as the sharer
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created the following folders
|
||||
| path |
|
||||
| /testshare |
|
||||
| /testshare/testsubfolder |
|
||||
And user "Brian" has uploaded file with content "test data" to "/testshare/testsubfolder/testfile.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Brian" moves folder "/testshare/testsubfolder" to "/testsubfolder" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/testsubfolder/testfile.txt" for user "Brian" should be "test data"
|
||||
And as "Alice" folder "/testshare/testsubfolder" should not exist
|
||||
And as "Brian" folder "/testshare/testsubfolder" should not exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: moving a folder out of a shared folder as the sharee
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created the following folders
|
||||
| path |
|
||||
| /testshare |
|
||||
| /testshare/testsubfolder |
|
||||
And user "Brian" has uploaded file with content "test data" to "/testshare/testsubfolder/testfile.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Alice" moves folder "/Shares/testshare/testsubfolder" to "/testsubfolder" using the WebDAV API
|
||||
Then the HTTP status code should be "502"
|
||||
And as "Alice" folder "/Shares/testshare/testsubfolder" should exist
|
||||
And as "Brian" folder "/testshare/testsubfolder" should exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: sharee moves a file within a shared folder (change/all permissions)
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "testshare"
|
||||
And user "Brian" has created folder "testshare/child"
|
||||
And user "Brian" has uploaded file with content "test data" to "testshare/testfile.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Alice" moves folder "Shares/testshare/testfile.txt" to "Shares/testshare/child/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/Shares/testshare/child/testfile.txt" should exist
|
||||
And as "Brian" file "/testshare/child/testfile.txt" should exist
|
||||
And as "Alice" file "/Shares/testshare/testfile.txt" should not exist
|
||||
And as "Brian" file "/testshare/testfile.txt" should not exist
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
|
||||
|
||||
Scenario Outline: sharee tries to move a file within a shared folder (read permissions)
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "testshare"
|
||||
And user "Brian" has created folder "testshare/child"
|
||||
And user "Brian" has uploaded file with content "test data" to "testshare/testfile.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Alice" moves folder "Shares/testshare/testfile.txt" to "Shares/testshare/child/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" file "/Shares/testshare/child/testfile.txt" should not exist
|
||||
And as "Brian" file "/testshare/child/testfile.txt" should not exist
|
||||
And as "Alice" file "/Shares/testshare/testfile.txt" should exist
|
||||
And as "Brian" file "/testshare/testfile.txt" should exist
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-1976
|
||||
Scenario Outline: sharee tries to move a file into same shared folder with same name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes
|
||||
And user "Brian" has created folder "testshare"
|
||||
And user "Brian" has uploaded file with content "test data" to "testshare/testfile.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | testshare |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | <permissions-role> |
|
||||
And user "Alice" has a share "testshare" synced
|
||||
When user "Alice" moves folder "Shares/testshare/testfile.txt" to "Shares/testshare/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Brian" the file with original path "testshare/testfile.txt" should not exist in the trashbin
|
||||
And the content of file "Shares/testshare/testfile.txt" for user "Alice" should be "test data"
|
||||
And the content of file "testshare/testfile.txt" for user "Brian" should be "test data"
|
||||
Examples:
|
||||
| dav-path-version | permissions-role |
|
||||
| old | Viewer |
|
||||
| old | Uploader |
|
||||
| old | Editor |
|
||||
| new | Viewer |
|
||||
| new | Uploader |
|
||||
| new | Editor |
|
||||
| spaces | Viewer |
|
||||
| spaces | Uploader |
|
||||
| spaces | Editor |
|
||||
Reference in New Issue
Block a user