-
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][Detections] increases coverage of bulk edit rules action according to test plan #141929
[Security Solution][Detections] increases coverage of bulk edit rules action according to test plan #141929
Conversation
# Conflicts: # x-pack/plugins/security_solution/cypress/e2e/detection_rules/custom_query_rule.cy.ts # x-pack/plugins/security_solution/cypress/screens/create_new_rule.ts # x-pack/plugins/security_solution/cypress/tasks/create_new_rule.ts
…hub.com/vitaliidm/kibana into detections/bulk-edit-rule-actions-tests
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
it('Overwrite rule actions in rules', () => { | ||
const expectedActionFrequency = 'On each rule execution'; | ||
|
||
loadPrebuiltDetectionRulesFromHeaderBtn(); |
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 prebuilt rules for this test case? Installation of all prebuilt rules is a heavy and error-prone operation that often fails due to timeouts. And that's not clear from the test body why we even need prebuilt rules here.
If prebuilt rules are required to check that the "Custom rules cannot be edited" modal is not displayed, I would isolate that in a separate test case and make an explicit check.
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.
It's not only to ensure no modal displayed, but also to ensure no errors happened when successfully applying both add and overwrite actions to custom and prebuilt rules
x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules_actions.cy.ts
Show resolved
Hide resolved
x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules_actions.cy.ts
Show resolved
Hide resolved
x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules_actions.cy.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules_actions.cy.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules_actions.cy.ts
Outdated
Show resolved
Hide resolved
…hub.com/vitaliidm/kibana into detections/bulk-edit-rule-actions-tests
@xcrzx feedback has been addressed |
Files by Code Ownerelastic/security-detections-response
elastic/security-detections-response-alerts
elastic/security-detections-response-rules
elastic/security-solution
elastic/security-threat-hunting
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @vitaliidm |
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, thanks for addressing my comments 👍
… action according to test plan (elastic#141929) ## Summary - adds missing tests according to [test plan](https://docs.google.com/document/d/116x7ITTTJQ6cTiwaGK831_f6Ox7XB3qyLiHxC3Cmf8w/edit#heading=h.tzaw2977z8ue) (internal document) - small refactoring of cypress tasks related to rule actions: create Email connector moved to common tasks from create_rule screen, as it used in bulk editing as well (cherry picked from commit d07301f)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
… action according to test plan (#141929) (#142978) ## Summary - adds missing tests according to [test plan](https://docs.google.com/document/d/116x7ITTTJQ6cTiwaGK831_f6Ox7XB3qyLiHxC3Cmf8w/edit#heading=h.tzaw2977z8ue) (internal document) - small refactoring of cypress tasks related to rule actions: create Email connector moved to common tasks from create_rule screen, as it used in bulk editing as well (cherry picked from commit d07301f) Co-authored-by: Vitalii Dmyterko <[email protected]>
… action according to test plan (elastic#141929) ## Summary - adds missing tests according to [test plan](https://docs.google.com/document/d/116x7ITTTJQ6cTiwaGK831_f6Ox7XB3qyLiHxC3Cmf8w/edit#heading=h.tzaw2977z8ue) (internal document) - small refactoring of cypress tasks related to rule actions: create Email connector moved to common tasks from create_rule screen, as it used in bulk editing as well
… action according to test plan (elastic#141929) ## Summary - adds missing tests according to [test plan](https://docs.google.com/document/d/116x7ITTTJQ6cTiwaGK831_f6Ox7XB3qyLiHxC3Cmf8w/edit#heading=h.tzaw2977z8ue) (internal document) - small refactoring of cypress tasks related to rule actions: create Email connector moved to common tasks from create_rule screen, as it used in bulk editing as well
Summary