-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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/case_form_fields - Severity form field renders #188951
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
Jul 23, 2024
kibanamachine
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Jul 23, 2024
Pinging @elastic/response-ops (Team:ResponseOps) |
New failure: kibana-on-merge - main |
Skipped. main: f2f079b |
Pinging @elastic/response-ops-cases (Feature:Cases) |
guskovaue
added a commit
that referenced
this issue
Aug 26, 2024
Issue: #188951 Fix flaky test: x-pack/plugins/cases/public/components/case_form_fields/severity.test.tsx It seems that this wrapper `createAppMockRenderer` is very slow. But we do not need it for this small and simple component. So I just deleted it from the test and use common `render` instead.
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
Skipped. main: b8c3d17 |
1 task
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this issue
Nov 26, 2024
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this issue
Nov 26, 2024
…01406) ## Summary This PR removes the usage of `appMockRender` from some flaky tests in the hope they will stop being flaky. We suspect that the `appMockRender` is the source of flakiness and we would like to verify our assumption. Fixes: elastic#189105 Fixes: elastic#195698 Fixes: elastic#189014 Fixes: elastic#176679 Fixes: elastic#188951 Fixes: elastic#192672 ### Checklist - [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
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Dec 12, 2024
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Dec 12, 2024
…01406) ## Summary This PR removes the usage of `appMockRender` from some flaky tests in the hope they will stop being flaky. We suspect that the `appMockRender` is the source of flakiness and we would like to verify our assumption. Fixes: elastic#189105 Fixes: elastic#195698 Fixes: elastic#189014 Fixes: elastic#176679 Fixes: elastic#188951 Fixes: elastic#192672 ### Checklist - [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
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: kibana-on-merge - main
The text was updated successfully, but these errors were encountered: