You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Backport
This will backport the following commits from `main` to `8.19`:
- [[Security Solution] Actualize prebuilt rule upgrade test plans
(#222606)](#222606)
<!--- Backport version: 9.6.6 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)
<!--BACKPORT [{"author":{"name":"Maxim
Palenov","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-06-24T10:09:52Z","message":"[Security
Solution] Actualize prebuilt rule upgrade test plans
(#222606)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/202078\n**Resolves:**https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR
actualizes prebuilt rule upgrade test plans to correspond to the current
feature state.\n\n## Details\n\nThe changes are summarized in the
following items\n\n- Missing scenarios were added\n-
#166215 was addressed\n- The
wording was fixed to make the test scenarios shorter and focused\n-
Prebuilt Rules Customization Milestone 2 test scenarios were migrated to
a separate test plan `prebuilt_rule_json_diff.md`. The functionality is
still relevant and used for rule type changes and under low-tier
licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v9.1.0","v8.19.0"],"title":"[Security
Solution] Actualize prebuilt rule upgrade test
plans","number":222606,"url":"https://github.com/elastic/kibana/pull/222606","mergeCommit":{"message":"[Security
Solution] Actualize prebuilt rule upgrade test plans
(#222606)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/202078\n**Resolves:**https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR
actualizes prebuilt rule upgrade test plans to correspond to the current
feature state.\n\n## Details\n\nThe changes are summarized in the
following items\n\n- Missing scenarios were added\n-
#166215 was addressed\n- The
wording was fixed to make the test scenarios shorter and focused\n-
Prebuilt Rules Customization Milestone 2 test scenarios were migrated to
a separate test plan `prebuilt_rule_json_diff.md`. The functionality is
still relevant and used for rule type changes and under low-tier
licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222606","number":222606,"mergeCommit":{"message":"[Security
Solution] Actualize prebuilt rule upgrade test plans
(#222606)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/202078\n**Resolves:**https://github.com/elastic/kibana/issues/166215\n\n## Summary\n\nThis PR
actualizes prebuilt rule upgrade test plans to correspond to the current
feature state.\n\n## Details\n\nThe changes are summarized in the
following items\n\n- Missing scenarios were added\n-
#166215 was addressed\n- The
wording was fixed to make the test scenarios shorter and focused\n-
Prebuilt Rules Customization Milestone 2 test scenarios were migrated to
a separate test plan `prebuilt_rule_json_diff.md`. The functionality is
still relevant and used for rule type changes and under low-tier
licenses.","sha":"1a59438b125e45418d01cab29cc06ca0838740a2"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Maxim Palenov <[email protected]>
Copy file name to clipboardExpand all lines: x-pack/solutions/security/plugins/security_solution/docs/testing/test_plans/detection_response/prebuilt_rules/prebuilt_rule_installation.md
-[**Scenario: User can see correct rule information in preview before installing**](#scenario-user-can-see-correct-rule-information-in-preview-before-installing)
47
47
-[**Scenario: Optional tabs and sections without content should be hidden in preview before installing**](#scenario-optional-tabs-and-sections-without-content-should-be-hidden-in-preview-before-installing)
-[**Scenario: User can search prebuilt rules by rule name, index pattern or MITRE ATT\&CK™ tactic or technique on the Prebuilt Rules installation page**](#scenario-user-can-search-prebuilt-rules-by-rule-name-index-pattern-or-mitre-attck-tactic-or-technique-on-the-prebuilt-rules-installation-page)
50
+
-[**Scenario: User can filter prebuilt rules by tags on the Prebuilt Rules installation page**](#scenario-user-can-filter-prebuilt-rules-by-tags-on-the-prebuilt-rules-installation-page)
51
+
-[**Scenario: User can sort prebuilt rules on Prebuilt Rules installation page**](#scenario-user-can-sort-prebuilt-rules-on-prebuilt-rules-installation-page)
52
+
-[**Scenario: User can paginate over prebuilt rules on Prebuilt Rules installation page**](#scenario-user-can-paginate-over-prebuilt-rules-on-prebuilt-rules-installation-page)
-[**Scenario: User opening the Add Rules page sees a loading skeleton until the package installation is completed**](#scenario-user-opening-the-add-rules-page-sees-a-loading-skeleton-until-the-package-installation-is-completed)
51
55
-[**Scenario: User can navigate from the Add Rules page to the Rule Management page via breadcrumbs**](#scenario-user-can-navigate-from-the-add-rules-page-to-the-rule-management-page-via-breadcrumbs)
@@ -108,79 +112,6 @@ Previewing properties of a prebuilt rule before installing it:
108
112
- If user chooses to preview a prebuilt rule to be installed, we currently show this preview in a flyout.
109
113
- In the prebuilt rule preview a tab that doesn't have any sections should not be displayed and a section that doesn't have any properties also should not be displayed.
110
114
111
-
Examples of rule properties we show in the prebuilt rule preview flyout:
112
-
113
-
```Gherkin
114
-
Examples:
115
-
| rule_type | property | tab | section |
116
-
│ All rule types │ Author │ Overview │ About │
117
-
│ All rule types │ Building block │ Overview │ About │
118
-
│ All rule types │ Severity │ Overview │ About │
119
-
│ All rule types │ Severity override │ Overview │ About │
120
-
│ All rule types │ Risk score │ Overview │ About │
121
-
│ All rule types │ Risk score override │ Overview │ About │
122
-
│ All rule types │ Reference URLs │ Overview │ About │
123
-
│ All rule types │ False positive examples │ Overview │ About │
124
-
│ All rule types │ Custom highlighted fields │ Overview │ About │
125
-
│ All rule types │ License │ Overview │ About │
126
-
│ All rule types │ Rule name override │ Overview │ About │
127
-
│ All rule types │ MITRE ATT&CK™ │ Overview │ About │
128
-
│ All rule types │ Timestamp override │ Overview │ About │
129
-
│ All rule types │ Tags │ Overview │ About │
130
-
│ All rule types │ Type │ Overview │ Definition │
131
-
│ All rule types │ Related integrations │ Overview │ Definition │
#### **Scenario: User can search prebuilt rules by rule name, index pattern or MITRE ATT&CK™ tactic or technique on the Prebuilt Rules installation page**
353
+
354
+
**Automation**: 1 e2e test with mock rules
355
+
356
+
```Gherkin
357
+
Given multiple prebuilt rules available for installation
358
+
When user opens the Prebuilt Rules installation page
359
+
Then the available prebuilt rules should be shown
360
+
When user enters <text> in the search field
361
+
Then only the available prebuilt rules matching the <text> should be shown
362
+
```
363
+
364
+
**Examples:**
365
+
366
+
-`<text>`
367
+
- rule name or its part
368
+
- index pattern
369
+
- MITRE ATT&CK™ tactic or technique
370
+
371
+
#### **Scenario: User can filter prebuilt rules by tags on the Prebuilt Rules installation page**
372
+
373
+
**Automation**: 1 e2e test with mock rules
374
+
375
+
```Gherkin
376
+
Given multiple prebuilt rules available for installation
377
+
When user opens the Prebuilt Rules installation page
378
+
Then the available prebuilt rules should be shown
379
+
When user filters the available prebuilt rules by one or more tags
380
+
Then only the available prebuilt rules having these tags should be shown
381
+
```
382
+
383
+
#### **Scenario: User can sort prebuilt rules on Prebuilt Rules installation page**
384
+
385
+
**Automation**: 1 e2e test with mock rules
386
+
387
+
```Gherkin
388
+
Given multiple prebuilt rules available for installation
389
+
When user opens the Prebuilt Rules installation page
390
+
Then the available prebuilt rules should be shown
391
+
When user clicks on <field> header by picking the sorting direction
392
+
Then the available prebuilt rules should be sorted by <field> in the expected order
393
+
```
394
+
395
+
**Examples:**
396
+
397
+
-`<field>`
398
+
- rule name
399
+
- risk score
400
+
- severity
401
+
402
+
#### **Scenario: User can paginate over prebuilt rules on Prebuilt Rules installation page**
403
+
404
+
**Automation**: 1 e2e test with mock rules
405
+
406
+
```Gherkin
407
+
Given multiple prebuilt rules available for installation
408
+
When user opens the Prebuilt Rules installation page
409
+
Then the available prebuilt rules should be shown
410
+
When user picks the desired number of <rows_per_page>
411
+
Then the <rows_per_page> of the available prebuilt rules should be shown on the page
412
+
When user navigates to the next pages
413
+
Then the next page of the available prebuilt rules should be shown
0 commit comments