Functional tests - close welcome screen if needed #57463
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
|
Solved in #58371 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds handling for the Kibana welcome screen (clicks it away).
Background
Currently, the Kibana welcome screen is disabled during functional tests via a Kibana config. But when executing the functional tests on a Elastic cloud production deployment (where this config entry is not whitelisted thus not working), the tests are failing because of the not handled welcome screen.
Since we want to double down on making sure that cloud production deployments are running fine, executing the tests there is particularly important to ensure quality.