-
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/all_cases - Severity form field renders #176336
Failing test: Jest Tests.x-pack/plugins/cases/public/components/all_cases - Severity form field renders #176336
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
New failure: CI Build - main |
Pinging @elastic/response-ops-cases (Feature:Cases) |
New failure: CI Build - main |
Skipped. main: c094f61 |
New failure: CI Build - main |
New failure: CI Build - main |
Skipped. main: 207d844 |
New failure: CI Build - main |
New failure: CI Build - main |
Skipped. main: e6892c8 |
Fixes #176336 ## Summary The only thing I could find in the test was a bunch of unnecessary DOM searches. This is one of the most expensive operations in tests so I: 1. Converted the 3 redundant `findByTestId('options-filter-popover-button-severity')` into just 1. 2. Did a single `findAllByRole('option')` instead of a search for every single value + a search for all to guarantee length was 4. Locally the test duration was reduced from 300ms to 150+-. Let's see how it behaves in the pipeline.
New failure: kibana-on-merge - main |
We're seeing this fail on a few pull requests in addition to ^. Skipped main: d9c3300 |
New failure: kibana-on-merge - main |
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: