-
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/create - Create case Step 2 - Connector Fields should submit and push to servicenow sir connector #142282
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
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
New failure: CI Build - main |
2 tasks
2 tasks
cnasikas
added a commit
that referenced
this issue
Nov 16, 2022
## Summary This PR fixes a number of issues with the same error: `TestingLibraryElementError: Unable to find an element by: [data-test-subj="caseTitle"]`. The PR: - Clears unnecessary `act` - Wait for the form to render before trying to fill the form - Wait for the component to update all states to eliminate warnings - Fill tags when necessary to improve tests execution time - Replace `userEvent.type` with `userEvent.aste` when possible to improve execution time - Add `skipPointerEventsCheck: true` when necessary I run the test file 100 times locally without any errors. Fixes: #142287, #142288, #142285, #142286, #142284, #142283, #142282, #142281, #143407, #143406, #143405, #143408, #143403 ### 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)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Nov 16, 2022
## Summary This PR fixes a number of issues with the same error: `TestingLibraryElementError: Unable to find an element by: [data-test-subj="caseTitle"]`. The PR: - Clears unnecessary `act` - Wait for the form to render before trying to fill the form - Wait for the component to update all states to eliminate warnings - Fill tags when necessary to improve tests execution time - Replace `userEvent.type` with `userEvent.aste` when possible to improve execution time - Add `skipPointerEventsCheck: true` when necessary I run the test file 100 times locally without any errors. Fixes: elastic#142287, elastic#142288, elastic#142285, elastic#142286, elastic#142284, elastic#142283, elastic#142282, elastic#142281, elastic#143407, elastic#143406, elastic#143405, elastic#143408, elastic#143403 ### 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) (cherry picked from commit 6936644)
New failure: CI Build - 8.6 |
2 tasks
2 tasks
New failure: CI Build - main |
mistic
added a commit
that referenced
this issue
Nov 21, 2022
Skipped. main: 84068e6 |
cnasikas
added a commit
that referenced
this issue
Nov 23, 2022
## Summary The connectors in the create case form use `select` elements to display various fields. The values of the `select` are being fetched from the external service. To prevent flakiness we are waiting for the values to be presented first before trying to select the value. Fixes: #142284, #142282, #143407 ### 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)
New failure: CI Build - 8.6 |
cnasikas
added a commit
to cnasikas/kibana
that referenced
this issue
Nov 23, 2022
## Summary The connectors in the create case form use `select` elements to display various fields. The values of the `select` are being fetched from the external service. To prevent flakiness we are waiting for the values to be presented first before trying to select the value. Fixes: elastic#142284, elastic#142282, elastic#143407 ### 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) (cherry picked from commit cf0cde2) # Conflicts: # x-pack/plugins/cases/public/components/create/form_context.test.tsx
Fix backported to 8.6 #146213 |
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 - 8.5
The text was updated successfully, but these errors were encountered: