Skip to content

Consolidate before steps and dynamically check if Elasticsearch is already enabled in browser UI test

Erick Banks requested to merge egb-browser-test-fixup into master

What does this MR do and why?

Instead of fabricating an Elasticsearch resource I've changed the before step to be more like the api tests that examine if Elasticsearch is already enabled, and if not, then turn it on. This will allow us to forgo the admin UI steps of turning on elasticsearch in live environments as elasticsearch is already turned on in those environments.

Also consolidated the before steps to one before block instead of having both a before and before(:all).

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports