Test plan for elasticsearch code analyzer

Test Plan

Introduction

The Elasticsearch code analyzer allows users to search code but there are several cases where expected search results fail to appear.

For example, if I have a file with a.b.c=one_two_three and I search for one_two_three, I don't get the file returned in the search.

We should add E2E tests that perform searches via elasticsearch using common and problematic search terms in code from major languages.

See https://gitlab.com/gitlab-org/gitlab-ee/issues/10693

Scope

Included:

• Code searches of major languages (we'll need to come up with inclusion criteria and a list)
• Test against staging.gitlab.com (elasticsearch is enabled for the gitlab-ce project)

Excluded:

• Non-code searches
• Test against production (elasticsearch isn't available on gitlab.com yet)

Test Plan

Create a test inside ee/spec to have tests be run pre merge and use the already existing Elasticsearch server being used by the existing tests. The test needs to be tagged with :elastic and using data concerning the aformentioned strange behaviour.

To come up with test data (source code and search terms) we can refer to the linked issue and call on the support engineers to provide examples that caused problems for customers.