-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Failing test: Jest Tests.x-pack/plugins/cases/public/components/all_cases - AllCasesListGeneric Actions Row actions should disable row actions when selecting a case #148096
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Dec 26, 2022
kibanamachine
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Dec 26, 2022
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
Fixed by #149005 |
New failure: CI Build - main |
I'm sorry @js-jankisalvi but this failure occurred just minutes after the tests were unskipped by #149005 Skipped when dealing with #150923 |
2 tasks
cnasikas
added a commit
that referenced
this issue
May 15, 2023
## Summary This PR fixes the flaky tests in `x-pack/plugins/cases/public/components/all_cases/all_cases_list.test.tsx`. It modifies the `getComputedStyle` to be more performant. For more information see https://blog.sentry.io/sentrys-frontend-tests-migrating-from-enzyme-to-react-testing-library and jsdom/jsdom#3234. I run the test multiple times on CI to ensure that the test is not flaky anymore: Specifically: - Test run 50 times in ccf2716 - Test run 40 times in c56c650 - Test run 50 times in b04d613 - Test run 50 times in e0ef292 - Test run 55 times in 1ba6bac Fixes: #148096, #150923 ### 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 ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
jasonrhodes
pushed a commit
that referenced
this issue
May 17, 2023
## Summary This PR fixes the flaky tests in `x-pack/plugins/cases/public/components/all_cases/all_cases_list.test.tsx`. It modifies the `getComputedStyle` to be more performant. For more information see https://blog.sentry.io/sentrys-frontend-tests-migrating-from-enzyme-to-react-testing-library and jsdom/jsdom#3234. I run the test multiple times on CI to ensure that the test is not flaky anymore: Specifically: - Test run 50 times in ccf2716 - Test run 40 times in c56c650 - Test run 50 times in b04d613 - Test run 50 times in e0ef292 - Test run 55 times in 1ba6bac Fixes: #148096, #150923 ### 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 ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
New failure: CI Build - 8.12 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: