Files
opencloud/tests/acceptance/features/apiSearch1/dateSearch.feature
2025-02-14 09:26:32 +01:00

71 lines
4.2 KiB
Gherkin

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&lt;$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 |