-
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: X-Pack Cloud Security Posture Functional Tests.x-pack/test/cloud_security_posture_functional/pages/findings_onboarding·ts - Cloud Security Posture Findings Page onboarding Vulnerabilities - clicking on the No integrations installed
prompt action button - install CNVM
: navigates to the CNVM integration installation page
#197143
Comments
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
Navigation happened according to the screenshot, also 50 runs of the flaky test runner were successful, closing as intermittent flakiness |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - main |
## Summary This PR tries to fix the following issues - which are flaky FTR tests: - #197143 - convert to unit test - #190967 - fixed - #187470 - fixed - #186302 - convert to unit test - #186438 - convert to unit test 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
closed by #208345 |
New failure: kibana-on-merge - 8.18 |
closed by #210743 |
A test failed on a tracked branch
First failure: kibana-on-merge - main
The text was updated successfully, but these errors were encountered: