-
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] Re-enable broken ML tests #133510
Conversation
efeb5f7
to
431c046
Compare
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @xcrzx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
(cherry picked from commit 3eb00f5)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Resolves: #128318
Summary
This PR unskips and updates tests that were disabled With the introduction of the V3 ML Modules (#131166):
Other changes
Migrated
x-pack/test/detection_engine_api_integration/security_and_spaces/group1/create_ml.ts
from@kbn/except
toexcept
- an assertion library used by Jest. That allowed us to remove irrelevant checks by usingexpect.objectContaining
, hopefully reducing flakiness and simplifying test cases.