Test plan: Ensure that `git push` and web UI changes to project and wiki repositories trigger reindexing
Test Plan
Introduction
Follow-up from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14057/diffs#note_181282316
When a user does a git push with elasticsearch enabled, we rely on the gitlab-shell / gitaly hooks running and triggering a reindex of the repository via the internal API. This applies for both wiki and project repositories. Until this is done, the changes won't appear in search results.
When a user edits a repository in the web UI (creates a new wiki page, say, or modifies README in the project repository), we also expect the repository to be reindexed.
We can't test these scenarios directly in the gitlab-ee spec/ directory because hooks are disabled in that environment. So I think we can justify a QA test for each scenario.
It does imply introducing an elasticsearch container to the QA test run.
Scope
ACC Matrix
| Secure | Responsive | Intuitive | Reliable | |
|---|---|---|---|---|
| Search | X |
Capabilities
- Search is
- Reliable - no matter how changes to a repo come into GitLab, the index is updated appropriately