Open banderror opened 4 days ago
Pinging @elastic/security-solution (Team: SecuritySolution)
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)
Pinging @elastic/security-detections-response (Team:Detections and Resp)
@jpdjere Please check this ticket and prioritize working on it after https://github.com/elastic/kibana/issues/202078. Before writing any tests and test plans, review what we already have and try to plan your work and share the plan with me and the team, so we could give feedback on the scope, approach, etc.
cc @pborgonovi
Epics: https://github.com/elastic/security-team/issues/1974 (internal), https://github.com/elastic/kibana/issues/174168
Summary
Write test plans (one or a few) and create a comprehensive suite of automated tests for the workflow of exporting and importing prebuilt rules.
Please note that test plans for prebuilt rule export and import have been already written in https://github.com/elastic/kibana/pull/191116, and there is already test coverage for that. What I would like us to do is to review the existing plans, the tests, compare them with the cases described in the RFC, think about any other edge cases, audit the existing plans and coverage, and add anything that's missing.
Features to cover:
rule_id
's (edge cases)Please cover both the features under the feature flag turned ON and OFF.
Related tickets
Related functional tickets to cover with tests:
Related bugs to cover with tests:
TODO