New blackbox elasticsearch approach
What does this MR do?
This is my attempt at doing a true blackbox test of elasticsearch as per this issue #227724 (closed). It's not currently in the proper place as a longer running test like this should probably be in a nightly run, but this is just to solicit feedback and see if we want to start end-to-end testing elasticsearch in this manner.
We're planning on adding docker images to the registry with known entities already indexed in elasticsearch so that we can just do record recall tests on test runs that run frequently (like the per MR gitlab-qa runs) rather than wait up to ten minutes for record insertion, indexing and retrieval. But we want to test record insertion, indexing, and retrieval too, just at a slower cadence, hence this test that runs nightly.
This should run in nightly after !43043 (merged) gets merged.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team