[web] e2e tests for search

[exalate-issue-sync]

Description

Search is a fundamental feature of the product, hence it needs some e2e tests.

User Stories

• As a owncloud we want to be sure that core features like search work as expected so that we can release without the risk of broken core features.

Value

Avoid regressions.

Acceptance Criteria

• set up tika in docker-compose dev stack and in drone (note: tika needs to be up and running before ocis starts, so depends_on is not sufficient)
• One big "smoke" test e2e story with a couple of search combinations being tested as follows:
  • as test background, create some files, some of them with assigned tags. make sure they are in different locations (personal space, subfolder of the personal space, maybe an incoming accepted share and a project space).
  • scenario:
    • user enters no search term, hits enter. expected: navigates to search result page, page shows "Search for files"
    • user selects a tag. expected: page updates with search result for the selected tag.
    • user enters a search term, hits enter. expected: page updates with search result for the selected tag + search term.
    • user deselects the tag. expected: page updates with search result for the search term.
    • user toggles Search in file content. expected: page updates with search result for fulltext search by the provided search term (i.e. search term is not used for file name search anymore but for file content).
    • user clicks on a .txt file in the search result. expected: text editor opens the file.
    • user closes the text editor. expected: navigates back to the search result page.
• delete the old acceptance tests for search

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] code review happened
  [ ] CI is green
  [ ] critical code received unit tests by the developer
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues

[grgprarup]

Setup Tika

• set up tika in docker-compose dev stack
• drone
  (note: tika needs to be up and running before ocis starts, so depends_on is not sufficient)

Test to be added:

• as test background, create some files, some of them with assigned tags. make sure they are in different locations (personal space, subfolder of the personal space, maybe an incoming accepted share and a project space)
• user enters no search term, hits enter. expected: navigates to search result page, page shows "Search for files"
• user selects a tag. expected: page updates with search result for the selected tag.
• user enters a search term, hits enter. expected: page updates with search result for the selected tag + search term
• user deselects the tag. expected: page updates with search result for the search term
• user toggles Search in file content. expected: page updates with search result for fulltext search by the provided search term (i.e. search term is not used for file name search anymore but for file content) [full-ci] [tests-only] [E2E] full text search tests added #9238
• user clicks on a .txt file in the search result. expected: text editor opens the file [tests-only] [full-ci] file viewer editor close step addition #9365
• user closes the text editor. expected: navigates back to the search result page [tests-only] Enable passing e2e test #9550 [ocis] search in file content button is cleared #9242
• delete the old acceptance tests for search [tests-only][full-ci]Remove acceptance tests related to search #9564

[grgprarup]

This PR #9238 adds a scenario for all test cases.

More Tests cases could be added

• Search using content (Content:keyword)
• Search using a tag (Tags:tagName)
  (web won't support it. it is not too obvious for the user. there are no hints for users, like use "Tags:" or "Content:" in the search line)

Post Task:

• Add an API step for adding tags to the resource (need to refactor the test added by [full-ci] [tests-only] [E2E] full text search tests added #9238) [tests-only] [full-ci] added api step to assign tag on resources #9311

[SwikritiT]

TODO

• search re-shared file [tests-only] Add e2e tests for searching renamed and reshared resources #9549
• search renamed file [tests-only] Add e2e tests for searching renamed and reshared resources #9549

[SwikritiT]

All the PR's are merged and the checklists is complete, closing this as done