-
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
[Security Solution] Fix flaky tests: Detection and Response team 8.11-8.12 #165359
Comments
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
…166659) **Related to: #165359 **Resolves: #165504 ## Summary This PR unskips skipped rule integrations ESS tests. ## Details Besides just unskipping ESS tests this PR simplifies the test by fetching alert data from the ES directly instead of using multiple steps in UI to validate an expected field has an expected value. ## Flaky test runner ESS [related_integrations.cy.ts 100 runs](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3199) 🟢
The tickets related to true flakes will be assigned to the corresponding teams. |
We have eliminated test flakiness in the Rule Management area almost entirely, and have greatly reduced it in the Detection Engine area. At the time of writing, there's some leftover flakiness you can track using these links:
@maximpn and @jpdjere: you've done an amazing job, thank you so much for all your efforts made during the last 3 release cycles fighting the flakiness, unskipping tests, and enabling them in Serverless! I consider the 8.11 and 8.12 goals of this ticket accomplished, and so I'm closing it. Both teams will handle the leftover flakiness as part of separate tickets. cc @yctercero |
Epic: #153633
Summary
Fix flaky tests and unskip tests that belong to the Rule Management or the Detection Engine teams.
Our "inbox" of failed and skipped tests:
FTR tests: #165780
Sub-tasks
Prebuilt rules
Rule management and monitoring
Related integrations
The text was updated successfully, but these errors were encountered: