-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Security Solution] Unskip Cypress tests for rule execution log #232023
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
Merged
banderror
merged 2 commits into
elastic:main
from
banderror:unskip-cypress-tests-for-rule-execution-log
Aug 18, 2025
+23
−10
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Why do we need to wait for a rule execution before scheduling a rule run? These actions don’t seem related. Would be nice to add a comment here explaining why this step is necessary.
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.
@xcrzx This block of code is a replacement for the removed
waitForAlertsToPopulate()which was a weird logic for waiting for a rule execution to finish, and wasn't working anyways.My goal was to just fix and unskip the test while keeping its original logic and structure introduced by @nkhristinin. Refactoring it or changing what we test here would be out of the scope of this PR. That said, I agree that "These actions don’t seem related" and we need to rework the whole test. I'd also argue that calling the manual rule run API should be owned by the DE team, so even more consideration and rework might be needed here.
I can create a ticket for follow-up work. Is there anything you want me to do in this PR?
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.
Okay, I thought you might know the reason, but thanks for the explanation anyway.
This test kind of sits between the responsibilities of two teams, so it’s not that easy to say who should own it. But if it relies on intricate knowledge of how manual runs work under the hood, it would be better to transfer it to DE.
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.
Yeah, I agree. Ok, I'll get back to this in the coming days and open a follow-up ticket.