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.

Sign up for GitHub

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

Jump to bottom

Failing test: Jest Tests.x-pack/plugins/cases/public/components/create - Create case Step 2 - Connector Fields should submit and push to servicenow itsm connector #142281

Closed
kibanamachine opened this issue Sep 29, 2022 · 3 comments · Fixed by #145211
Closed

Failing test: Jest Tests.x-pack/plugins/cases/public/components/create - Create case Step 2 - Connector Fields should submit and push to servicenow itsm connector #142281

kibanamachine opened this issue Sep 29, 2022 · 3 comments · Fixed by #145211
Assignees
@cnasikas
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
Copy link
Contributor

kibanamachine commented Sep 29, 2022 •
edited
Loading

A test failed on a tracked branch

Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/x-pack/plugins/cases/public/components/create/form_context.test.tsx:564:5
    at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:30:5)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/x-pack/plugins/cases/public/components/create/form_context.test.tsx:415:3
    at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:30:5)
    at Object.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/x-pack/plugins/cases/public/components/create/form_context.test.tsx:121:1)
    at Runtime._execModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:1299:24)
    at Runtime._loadModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:898:12)
    at Runtime.requireModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:746:10)
    at jestAdapter (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at runTestInternal (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:380:16)
    at runTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:472:34)
    at Object.worker (/var/lib/buildkite-agent/builds/kb-n2-4-spot-df08b440c5dd8216/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/testWorker.js:133:12)

First failure: CI Build - 8.5
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Sep 29, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 29, 2022
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Sep 29, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 29, 2022
@cnasikas cnasikas added the Feature:Cases Cases feature label Sep 30, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@cnasikas cnasikas mentioned this issue Nov 15, 2022
Merged
2 tasks
@cnasikas cnasikas self-assigned this Nov 15, 2022
@cnasikas cnasikas linked a pull request Nov 15, 2022 that will close this issue
[Cases] Fix flaky tests in the create case form #145211
Merged
2 tasks
cnasikas added a commit that referenced this issue Nov 16, 2022
@cnasikas
[Cases] Fix flaky tests in the create case form (#145211)
6936644 
## 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
@cnasikas
[Cases] Fix flaky tests in the create case form (elastic#145211)
b75686f 
## 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cnasikas cnasikas

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)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Cases] Fix flaky tests in the create case form cnasikas/kibana
3 participants
@cnasikas @elasticmachine @kibanamachine