Initial QSfera import
This commit is contained in:
@@ -0,0 +1,70 @@
|
||||
Feature: date search
|
||||
As a user
|
||||
I want to do search resources by date
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
|
||||
@issue-7060 @issue-10329
|
||||
Scenario Outline: search resources using different dav path
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "uploadFolder"
|
||||
When user "Alice" searches for 'Mtime:"today"' using the WebDAV API
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| /uploadFolder |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: search resources using different search patterns (KQL feature) in the personal space
|
||||
Given user "Alice" uploads a file "filesForUpload/textfile.txt" to "/today.txt" with mtime "today" via TUS inside of the space "Personal" using the WebDAV API
|
||||
And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/yesterday.txt" with mtime "yesterday" via TUS inside of the space "Personal" using the WebDAV API
|
||||
And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/lastWeek.txt" with mtime "lastWeek" via TUS inside of the space "Personal" using the WebDAV API
|
||||
And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/lastMonth.txt" with mtime "lastMonth" via TUS inside of the space "Personal" using the WebDAV API
|
||||
And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/lastYear.txt" with mtime "lastYear" via TUS inside of the space "Personal" using the WebDAV API
|
||||
And using spaces DAV path
|
||||
When user "Alice" searches for '<pattern>' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| <search-result-1> |
|
||||
| <search-result-2> |
|
||||
But the search result of user "Alice" should not contain these entries:
|
||||
| <search-result-3> |
|
||||
| <search-result-4> |
|
||||
Examples:
|
||||
| pattern | search-result-1 | search-result-2 | search-result-3 | search-result-4 |
|
||||
| Mtime:today | today.txt | | yesterday.txt | lastWeek.txt |
|
||||
| Mtime:yesterday | yesterday.txt | | today.txt | |
|
||||
| Mtime:"this week" | today.txt | | lastWeek.txt | lastMonth.txt |
|
||||
| Mtime:"this month" | today.txt | | lastMonth.txt | |
|
||||
| Mtime:"last month" | lastMonth.txt | | today.txt | |
|
||||
| Mtime:"this year" | today.txt | | lastYear.txt | |
|
||||
| Mtime:"last year" | lastYear.txt | | today.txt | |
|
||||
| Mtime>=$today | today.txt | | yesterday.txt | |
|
||||
| Mtime>$yesterday | today.txt | | | |
|
||||
| Mtime>=$yesterday | today.txt | yesterday.txt | | |
|
||||
# Mtime<$today. "<" has to be escaped
|
||||
| Mtime<$today | yesterday.txt | lastYear.txt | today.txt | |
|
||||
|
||||
@issue-10329
|
||||
Scenario: search resources using different search patterns (KQL feature) in the shares folder
|
||||
Given user "Brian" has been created with default attributes
|
||||
And using spaces DAV path
|
||||
And user "Alice" has created folder "sharedFolder"
|
||||
And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/sharedFolder/yesterday.txt" with mtime "yesterday" via TUS inside of the space "Personal" using the WebDAV API
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | sharedFolder |
|
||||
| space | Personal |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Brian" has a share "sharedFolder" synced
|
||||
When user "Brian" searches for "Mtime:yesterday" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Brian" should contain these entries:
|
||||
| yesterday.txt |
|
||||
But the search result of user "Alice" should not contain these entries:
|
||||
| sharedFolder |
|
||||
@@ -0,0 +1,165 @@
|
||||
Feature: search for favorites
|
||||
As a user
|
||||
I want to be able to search for my favorite files and folders
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes
|
||||
And using spaces DAV path
|
||||
|
||||
|
||||
Scenario: search by favorite files and folders in the Personal space
|
||||
Given user "Alice" has created folder "first"
|
||||
And user "Alice" has created folder "first/second"
|
||||
And user "Alice" has uploaded file "filesForUpload/testavatar.jpg" to "first/second/testavatar.jpg"
|
||||
And user "Alice" has marked file "first/second/testavatar.jpg" as favorite from space "Personal"
|
||||
And user "Alice" has marked folder "first" as favorite from space "Personal"
|
||||
When user "Alice" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "2" entries
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| first |
|
||||
| testavatar.jpg |
|
||||
But the search result of user "Alice" should not contain these entries:
|
||||
| second |
|
||||
|
||||
|
||||
Scenario: search for favorite files and folders in a project space
|
||||
Given user "Brian" has been created with default attributes
|
||||
And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
|
||||
And user "Alice" has created a space "new-space" with the default quota using the Graph API
|
||||
And user "Alice" has uploaded a file inside space "new-space" with content "hello world" to "text.txt"
|
||||
And user "Alice" has uploaded a file inside space "new-space" with content "hello world" to "text2.txt"
|
||||
And user "Alice" has created a folder "space-folder" in space "new-space"
|
||||
And user "Alice" has sent the following space share invitation:
|
||||
| space | new-space |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Space Viewer |
|
||||
And user "Brian" has marked file "text.txt" as favorite from space "new-space"
|
||||
And user "Brian" has marked folder "space-folder" as favorite from space "new-space"
|
||||
When user "Brian" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "2" entries
|
||||
And the search result of user "Brian" should contain these entries:
|
||||
| text.txt |
|
||||
| space-folder |
|
||||
But the search result of user "Brian" should not contain these entries:
|
||||
| text2.txt |
|
||||
When user "Alice" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
|
||||
@issue-2488
|
||||
Scenario: search for favorite shared files and folders
|
||||
Given user "Brian" has been created with default attributes
|
||||
And user "Alice" has created folder "parent"
|
||||
And user "Alice" has created folder "parent/sub"
|
||||
And user "Alice" has created folder "parent/sub/sub2"
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file" to "parent/sub/sub2/textfile.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | parent |
|
||||
| space | Personal |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | parent/sub/sub2/textfile.txt |
|
||||
| space | Personal |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Brian" has a share "textfile.txt" synced
|
||||
And user "Brian" has a share "parent" synced
|
||||
And user "Brian" has marked file "textfile.txt" as favorite from space "Shares"
|
||||
And user "Brian" has marked folder "parent/sub" as favorite from space "Shares"
|
||||
When user "Brian" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "3" entries
|
||||
And the search result of user "Brian" should contain these entries:
|
||||
| textfile.txt |
|
||||
| sub |
|
||||
But the search result of user "Brian" should not contain these entries:
|
||||
| parent |
|
||||
| parent/sub/sub2 |
|
||||
When user "Alice" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
|
||||
|
||||
Scenario Outline: search for favorite files by name and media type in the Personal space
|
||||
Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "test-textfile.txt"
|
||||
And user "Alice" has uploaded file "filesForUpload/simple.odt" to "test.odt"
|
||||
And user "Alice" has uploaded file "filesForUpload/lorem.txt" to "test-not-favorite.txt"
|
||||
And user "Alice" has marked file "test-textfile.txt" as favorite from space "Personal"
|
||||
And user "Alice" has marked file "test.odt" as favorite from space "Personal"
|
||||
When user "Alice" searches for '<search-patern>' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "2" entries
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| test-textfile.txt |
|
||||
| test.odt |
|
||||
But the search result of user "Alice" should not contain these entries:
|
||||
| test-not-favorite.txt |
|
||||
Examples:
|
||||
| search-patern |
|
||||
| name:"test*" AND is:favorite |
|
||||
| mediatype:("document") AND is:favorite |
|
||||
|
||||
|
||||
Scenario: search for favorite files after unmarking a file as favorite
|
||||
Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile.txt"
|
||||
And user "Alice" has marked file "textfile.txt" as favorite from space "Personal"
|
||||
And user "Alice" has unmarked file "textfile.txt" as favorite from space "Personal"
|
||||
When user "Alice" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
|
||||
|
||||
Scenario: search for favorite files after deleting a file
|
||||
Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile.txt"
|
||||
And user "Alice" has marked file "textfile.txt" as favorite from space "Personal"
|
||||
And user "Alice" has deleted file "textfile.txt"
|
||||
When user "Alice" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
|
||||
|
||||
Scenario: search for favorite files after restoring a file
|
||||
Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile.txt"
|
||||
And user "Alice" has marked file "textfile.txt" as favorite from space "Personal"
|
||||
And user "Alice" has deleted file "textfile.txt"
|
||||
And user "Alice" has restored the file with original path "textfile.txt"
|
||||
When user "Alice" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "1" entries
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| textfile.txt |
|
||||
|
||||
|
||||
Scenario: search for favorite files after moving a file
|
||||
Given user "Alice" has created folder "parent"
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile.txt"
|
||||
And user "Alice" has marked file "textfile.txt" as favorite from space "Personal"
|
||||
And user "Alice" has moved file "textfile.txt" to "parent/textfile.txt"
|
||||
When user "Alice" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "1" entries
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| textfile.txt |
|
||||
|
||||
|
||||
Scenario: search for favorite shared files after removing the access to the shared file
|
||||
Given user "Brian" has been created with default attributes
|
||||
And user "Alice" has uploaded file with content "КуСфера test text file" to "textfile.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | textfile.txt |
|
||||
| space | Personal |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Brian" has a share "textfile.txt" synced
|
||||
And user "Brian" has marked file "textfile.txt" as favorite from space "Shares"
|
||||
And user "Alice" has removed the access of user "Brian" from resource "textfile.txt" of space "Personal"
|
||||
When user "Brian" searches for 'is:favorite' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
@@ -0,0 +1,467 @@
|
||||
Feature: Search
|
||||
As a user
|
||||
I want to search for resources in the space
|
||||
So that I can get them quickly
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes:
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
And using spaces DAV path
|
||||
And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
|
||||
And user "Alice" has created a space "project101" with the default quota using the Graph API
|
||||
And user "Alice" has created a folder "folderMain/SubFolder1/subFOLDER2" in space "project101"
|
||||
And user "Alice" has uploaded a file inside space "project101" with content "some content" to "folderMain/SubFolder1/subFOLDER2/insideTheFolder.txt"
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: user can search items inside project space
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created a folder "AlicePersonal" in space "Personal"
|
||||
And user "Alice" has uploaded a file inside space "Personal" with content "inside Alice personal space" to "AlicePersonal/insideAlicePersonal.txt"
|
||||
And user "Brian" has created a folder "BrianPersonal" in space "Personal"
|
||||
And user "Brian" has uploaded file with content "inside Brian personal space" to "BrianPersonal/insideBrianPersonal.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | BrianPersonal |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Alice" has a share "BrianPersonal" synced
|
||||
When user "Alice" searches for "*inside*" inside space "project101" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "1" entries
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| insideTheFolder.txt |
|
||||
But the search result of user "Alice" should not contain these entries:
|
||||
| insideAlicePersonal.txt |
|
||||
| insideBrianPersonal.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: user can search items inside personal space
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created a folder "AlicePersonal" in space "Personal"
|
||||
And user "Alice" has uploaded a file inside space "Personal" with content "inside Alice personal space" to "AlicePersonal/insideAlicePersonal.txt"
|
||||
And user "Brian" has created a folder "BrianPersonal" in space "Personal"
|
||||
And user "Brian" has uploaded file with content "inside Brian personal space" to "BrianPersonal/insideBrianPersonal.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | BrianPersonal |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Alice" has a share "BrianPersonal" synced
|
||||
When user "Alice" searches for "*inside*" inside space "Personal" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "1" entries
|
||||
And the search result of user "Alice" should contain only these entries:
|
||||
| insideAlicePersonal.txt |
|
||||
But the search result of user "Alice" should not contain these entries:
|
||||
| insideBrianPersonal.txt |
|
||||
| insideTheFolder.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: user cannot search items inside shares space
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created a folder "AlicePersonal" in space "Personal"
|
||||
And user "Alice" has uploaded a file inside space "Personal" with content "inside Alice personal space" to "AlicePersonal/insideAlicePersonal.txt"
|
||||
And user "Brian" has created a folder "BrianPersonal" in space "Personal"
|
||||
And user "Brian" has uploaded file with content "inside Brian personal space" to "BrianPersonal/insideBrianPersonal.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | BrianPersonal |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Alice" has a share "BrianPersonal" synced
|
||||
When user "Alice" searches for "*inside*" inside space "Shares" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
And the search result of user "Alice" should not contain these entries:
|
||||
| insideBrianPersonal.txt |
|
||||
| insideAlicePersonal.txt |
|
||||
| insideTheFolder.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: user can search hidden files
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created a folder ".space" in space "project101"
|
||||
When user "Alice" searches for "*.sp*" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "1" entries
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| /.space |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: user cannot search pending share
|
||||
Given user "Brian" has disabled auto-accepting
|
||||
And using <dav-path-version> DAV path
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | folderMain |
|
||||
| space | project101 |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
When user "Brian" searches for "*folder*" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
And the search result of user "Brian" should not contain these entries:
|
||||
| SubFolder1 |
|
||||
| subFOLDER2 |
|
||||
| insideTheFolder.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: user cannot search declined share
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | folderMain |
|
||||
| space | project101 |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Brian" has a share "folderMain" synced
|
||||
And user "Brian" has disabled sync of last shared resource
|
||||
When user "Brian" searches for "*folder*" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
And the search result of user "Brian" should not contain these entries:
|
||||
| SubFolder1 |
|
||||
| subFOLDER2 |
|
||||
| insideTheFolder.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: user cannot search deleted items
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has removed the folder "folderMain" from space "project101"
|
||||
When user "Alice" searches for "*folderMain*" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "0" entries
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario: user can search project space by name
|
||||
Given using spaces DAV path
|
||||
When user "Alice" searches for '*project101*' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "1" entries
|
||||
And for user "Alice" the search result should contain space "project101"
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: user can search inside folder in space
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" searches for "*folder*" inside folder "/folderMain" in space "project101" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "3" entries
|
||||
And the search result of user "Alice" should contain only these entries:
|
||||
| SubFolder1 |
|
||||
| subFOLDER2 |
|
||||
| insideTheFolder.txt |
|
||||
But the search result of user "Alice" should not contain these entries:
|
||||
| folderMain |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: search inside folder in shares
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | folderMain |
|
||||
| space | project101 |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Brian" has a share "folderMain" synced
|
||||
When user "Brian" searches for "*folder*" inside folder "/folderMain" in space "Shares" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Brian" should contain only these entries:
|
||||
| SubFolder1 |
|
||||
| subFOLDER2 |
|
||||
| insideTheFolder.txt |
|
||||
But the search result of user "Brian" should not contain these entries:
|
||||
| /folderMain |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: search files inside the folder
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "hello world inside root" to "file1.txt"
|
||||
And user "Alice" has created folder "/Folder"
|
||||
And user "Alice" has uploaded file with content "hello world inside folder" to "/Folder/file2.txt"
|
||||
And user "Alice" has created folder "/Folder/SubFolder"
|
||||
And user "Alice" has uploaded file with content "hello world inside sub-folder" to "/Folder/SubFolder/file3.txt"
|
||||
When user "Alice" searches for "*file*" inside folder "/Folder" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain only these entries:
|
||||
| file2.txt |
|
||||
| file3.txt |
|
||||
But the search result of user "Alice" should not contain these entries:
|
||||
| file1.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-7114 @issue-10329
|
||||
Scenario Outline: search files inside the folder with white space character in its name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/New Folder"
|
||||
And user "Alice" has uploaded file with content "hello world inside folder" to "/New Folder/file.txt"
|
||||
And user "Alice" has created folder "/New Folder/Sub Folder"
|
||||
And user "Alice" has uploaded file with content "hello world inside sub folder" to "/New Folder/Sub Folder/file1.txt"
|
||||
When user "Alice" searches for "*file*" inside folder "/New Folder" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain only these entries:
|
||||
| file.txt |
|
||||
| file1.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-7114 @issue-10329
|
||||
Scenario Outline: search files with white space character in its name
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/New Folder"
|
||||
And user "Alice" has uploaded file with content "hello world" to "/new file.txt"
|
||||
And user "Alice" has created folder "/New Folder/New Sub Folder"
|
||||
When user "Alice" searches for "*new*" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain only these entries:
|
||||
| New Folder |
|
||||
| New Sub Folder |
|
||||
| new file.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-enterprise-6000 @issue-7028 @issue-7092 @issue-10329
|
||||
Scenario Outline: sharee cannot find resources that are not shared
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created a folder "foo/sharedToBrian" in space "Personal"
|
||||
And user "Alice" has created a folder "sharedToCarol" in space "Personal"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | foo |
|
||||
| space | Personal |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Brian" has a share "foo" synced
|
||||
When user "Brian" searches for "shared*" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Brian" should contain these entries:
|
||||
| sharedToBrian |
|
||||
But the search result of user "Brian" should not contain these entries:
|
||||
| sharedToCarol |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: search resources using different search patterns (KQL feature)
|
||||
Given using spaces DAV path
|
||||
And user "Alice" has created a folder "subfolder" in space "project101"
|
||||
When user "Alice" searches for '<pattern>' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "1" entries
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| <search-result> |
|
||||
Examples:
|
||||
| pattern | search-result | description |
|
||||
| fold* | folderMain | starts with |
|
||||
| *der1 | SubFolder1 | ends with |
|
||||
| subfolder | subfolder | exact search |
|
||||
| name:*der2 | subFOLDER2 | patern 'name:'' |
|
||||
| name:"*der2" | subFOLDER2 | pattern 'name:""' (with quotes) |
|
||||
|
||||
@issue-7812 @issue-8442 @issue-10329
|
||||
Scenario: try to search with invalid patterns
|
||||
Given using spaces DAV path
|
||||
And user "Alice" has uploaded file with content "test file" to "testFile.txt"
|
||||
When user "Alice" searches for 'AND mediatype:document' using the WebDAV API
|
||||
Then the HTTP status code should be "400"
|
||||
And the value of the item "/d:error/s:message" in the response should be "error: bad request: the expression can't begin from a binary operator: 'AND'"
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: search a file globally (in all spaces)
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created a folder "AlicePersonal" in space "Personal"
|
||||
And user "Alice" has uploaded a file inside space "Personal" with content "inside Alice personal space" to "AlicePersonal/insideAlicePersonal.txt"
|
||||
And user "Brian" has created a folder "BrianPersonal" in space "Personal"
|
||||
And user "Brian" has uploaded file with content "inside Brian personal space" to "BrianPersonal/insideBrianPersonal.txt"
|
||||
And user "Brian" has sent the following resource share invitation:
|
||||
| resource | BrianPersonal |
|
||||
| space | Personal |
|
||||
| sharee | Alice |
|
||||
| shareType | user |
|
||||
| permissionsRole | Viewer |
|
||||
And user "Alice" has a share "BrianPersonal" synced
|
||||
When user "Alice" searches for "*inside*" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result should contain "3" entries
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| insideAlicePersonal.txt |
|
||||
| insideTheFolder.txt |
|
||||
| insideBrianPersonal.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: search for files by extension
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" searches for "*txt*" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| insideTheFolder.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: search with empty field
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" searches for "" using the WebDAV API
|
||||
Then the HTTP status code should be "400"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: limit returned search entries to only 1 entry
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" searches for "*folder*" and limits the results to "1" items using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain any "1" of these entries:
|
||||
| insideTheFolder.txt |
|
||||
| folderMain |
|
||||
| SubFolder1 |
|
||||
| subFOLDER2 |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-10329
|
||||
Scenario Outline: search for entry with emoji by pattern
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "hello world" to "upload😀 😁.txt"
|
||||
When user "Alice" searches for '"*😀 😁*"' using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the search result of user "Alice" should contain these entries:
|
||||
| upload😀 😁.txt |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-4712 @issue-9780 @issue-9781 @issue-9783 @issue-10329
|
||||
Scenario Outline: report extra properties in search entries for a file
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" searches for "*insideTheFo*" using the WebDAV API requesting these properties:
|
||||
| oc:fileid |
|
||||
| oc:permissions |
|
||||
| d:getlastmodified |
|
||||
| d:getetag |
|
||||
| d:getcontenttype |
|
||||
| oc:size |
|
||||
| oc:owner-id |
|
||||
| oc:owner-display-name |
|
||||
Then the HTTP status code should be "207"
|
||||
And file "insideTheFolder.txt" in the search result of user "Alice" should contain these properties:
|
||||
| name | value |
|
||||
| oc:fileid | \d* |
|
||||
| oc:permissions | ^(RDNVW\|RMDNVW)$ |
|
||||
| d:getlastmodified | ^[MTWFS][uedhfriatno]{2},\s(\d){2}\s[JFMAJSOND][anebrpyulgctov]{2}\s\d{4}\s\d{2}:\d{2}:\d{2} GMT$ |
|
||||
| d:getetag | ^\"[a-f0-9:\.]{1,32}\"$ |
|
||||
| d:getcontenttype | text\/plain |
|
||||
| oc:size | 15 |
|
||||
| oc:owner-id | %username% |
|
||||
| oc:owner-display-name | %displayname% |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-4712 @issue-9780 @issue-9781 @issue-9783 @issue-10329
|
||||
Scenario Outline: report extra properties in search entries for a folder
|
||||
Given using <dav-path-version> DAV path
|
||||
When user "Alice" searches for "*folderMain*" using the WebDAV API requesting these properties:
|
||||
| oc:fileid |
|
||||
| oc:permissions |
|
||||
| d:getlastmodified |
|
||||
| d:getetag |
|
||||
| d:getcontenttype |
|
||||
| oc:size |
|
||||
| oc:owner-id |
|
||||
| oc:owner-display-name |
|
||||
Then the HTTP status code should be "207"
|
||||
And folder "folderMain" in the search result of user "Alice" should contain these properties:
|
||||
| name | value |
|
||||
| oc:fileid | \d* |
|
||||
| oc:permissions | ^(RDNVCK\|RMDNVCK)$ |
|
||||
| d:getlastmodified | ^[MTWFS][uedhfriatno]{2},\s(\d){2}\s[JFMAJSOND][anebrpyulgctov]{2}\s\d{4}\s\d{2}:\d{2}:\d{2} GMT$ |
|
||||
| d:getetag | ^\"[a-f0-9:\.]{1,32}\"$ |
|
||||
| oc:size | 0 |
|
||||
| oc:owner-id | %username% |
|
||||
| oc:owner-display-name | %displayname% |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
Reference in New Issue
Block a user