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: X-Pack Cloud Security Posture Functional Tests.x-pack/test/cloud_security_posture_functional/pages/findings_onboarding·ts - Cloud Security Posture Findings Page onboarding Misconfigurations - clicking on the No integrations installed prompt action button - install kubernetes posture integration: navigates to the KSPM integration installation page #203680

Closed
kibanamachine opened this issue Dec 10, 2024 · 2 comments
Closed

Failing test: X-Pack Cloud Security Posture Functional Tests.x-pack/test/cloud_security_posture_functional/pages/findings_onboarding·ts - Cloud Security Posture Findings Page onboarding Misconfigurations - clicking on the No integrations installed prompt action button - install kubernetes posture integration: navigates to the KSPM integration installation page #203680

kibanamachine opened this issue Dec 10, 2024 · 2 comments
Assignees
@alexreal1314
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Cloud Security Cloud Security team related

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: expected testSubject(globalLoadingIndicator-hidden) to exist
    at TestSubjects.existOrFail (test_subjects.ts:76:13)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at HeaderPageObject.awaitGlobalLoadingIndicatorHidden (header_page.ts:73:5)
    at HeaderPageObject.waitUntilLoadingHasFinished (header_page.ts:64:5)
    at Context.<anonymous> (findings_onboarding.ts:72:7)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-on-merge - 8.17
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Dec 10, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 10, 2024
@kibanamachine kibanamachine added the Team:Cloud Security Cloud Security team related label Dec 10, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 10, 2024
@alexreal1314 alexreal1314 mentioned this issue Feb 17, 2025
Merged
2 tasks
alexreal1314 added a commit that referenced this issue Feb 18, 2025
@alexreal1314
10973 migrate flaky e2e tests to jest 2 (#211363)
dac3690 
## Summary

This PR tries to fix the following issues - which are flaky FTR tests:

- #209529
- #201686
- #203680
- #178413 - test is still
skipped, added unit tests for rules table, header and counter
components.
- #193073
- #193616
- #191604
- #191593
- #191511
- #191474
- #191322
- #191128
- #191144
- #191027
- #190831
- #190779



There will be an RFC document which is going to be released to help us
better understand and decide which tests are more suitable to make as
E2E tests and which as unit tests.

### 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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed

### Closes
this PR closes the above mentioned issues in relation for this ticket -
elastic/security-team#10973
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Feb 18, 2025
@alexreal1314
10973 migrate flaky e2e tests to jest 2 (elastic#211363)
a391b6c 
## Summary

This PR tries to fix the following issues - which are flaky FTR tests:

- elastic#209529
- elastic#201686
- elastic#203680
- elastic#178413 - test is still
skipped, added unit tests for rules table, header and counter
components.
- elastic#193073
- elastic#193616
- elastic#191604
- elastic#191593
- elastic#191511
- elastic#191474
- elastic#191322
- elastic#191128
- elastic#191144
- elastic#191027
- elastic#190831
- elastic#190779

There will be an RFC document which is going to be released to help us
better understand and decide which tests are more suitable to make as
E2E tests and which as unit tests.

### 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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed

### Closes
this PR closes the above mentioned issues in relation for this ticket -
elastic/security-team#10973

(cherry picked from commit dac3690)
@alexreal1314 alexreal1314 self-assigned this Feb 18, 2025
@alexreal1314
Copy link
Contributor

closed by #211363

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexreal1314 alexreal1314

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Cloud Security Cloud Security team related
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@elasticmachine @alexreal1314 @kibanamachine