[Detection Engine] Limit the scope of an exceptions integration test #193228
Conversation
This file contains 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
The hope here is that this fixes some flakiness in the test, by restricting the alerts being asserted upon to only those created within the test (via filtering on the created rule's ID). Surrounding tests do this, and it seems likely that the failure (elastic#181887) was caused by a previous test's alerts being present during this test.
rylnd
added
release_note:skip
|
Pinging @elastic/security-detection-engine (Team:Detection Engine) |
|
Closing this, as this change is unnecessary. |
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: cc @rylnd |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The hope here is that this fixes some flakiness in the test, by restricting the alerts being asserted upon to only those created within the test (via filtering on the created rule's ID). Surrounding tests do this, and it seems likely that the failure
(#181887) was caused by a previous test's alerts being present during this test.