Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.8] [Security Solution] [Fix] Cypress test flakyness in Alert page Controls (#155988) #156486

Merged
merged 2 commits into from
May 3, 2023

Conversation

logeekal
Copy link
Contributor

@logeekal logeekal commented May 3, 2023

Backport

This will backport the following commits from main to 8.8:

Questions ?

Please refer to the Backport tool documentation

…ls (elastic#155988)

## Summary

Handles :  elastic#153685 and elastic#153686

This PR tries to fix the flakyness of cypress tests. Although, this
issue in cypress is very difficult to reproduce, I noticed that it is
coming mainly when adding extra control.

And it looks like during the course of dev one of the API of adding a
control called `addOptionsListControl` was changed to be a promise,
therefore, mainly the change is to await the promise before adding a new
control.

### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

(cherry picked from commit 6203acb)

# Conflicts:
#	x-pack/plugins/security_solution/public/common/lib/kibana/kibana_react.mock.ts
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 9.1MB 9.1MB +57.0B
Unknown metric groups

ESLint disabled line counts

id before after diff
enterpriseSearch 17 19 +2
securitySolution 399 402 +3
total +5

Total ESLint disabled count

id before after diff
enterpriseSearch 18 20 +2
securitySolution 479 482 +3
total +5

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@logeekal logeekal merged commit 5fb469c into elastic:8.8 May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants