Skip to content

Commit 48f1a42

Browse files
dplumleedplumlee
committed
adds more specific examples
1 parent 4a2b9df commit 48f1a42

1 file changed

Lines changed: 15 additions & 15 deletions

File tree

‎x-pack/plugins/security_solution/docs/testing/test_plans/detection_response/prebuilt_rules/installation_and_upgrade.md‎

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -837,9 +837,9 @@ Then the merged output should be the current verison of <field>
837837
And there should be no conflict
838838
839839
Examples:
840-
| field |
841-
| name |
842-
| risk_score|
840+
| field | base_version | current_version | target_version |
841+
| name | "A" | "A" | "A" |
842+
| risk_score | 1 | 1 | 1 |
843843
```
844844

845845
#### **Scenario: Rule field doesn't have an update but has a custom value**
@@ -856,9 +856,9 @@ Then the merged output should be the current verison of <field>
856856
And there should be no conflict
857857
858858
Examples:
859-
| field |
860-
| name |
861-
| risk_score|
859+
| field | base_version | current_version | target_version |
860+
| name | "A" | "B" | "A" |
861+
| risk_score | 1 | 2 | 1 |
862862
```
863863

864864
#### **Scenario: Rule field has an update and doesn't have a custom value**
@@ -875,9 +875,9 @@ Then the merged output should be the target verison of <field>
875875
And there should be no conflict
876876
877877
Examples:
878-
| field |
879-
| name |
880-
| risk_score|
878+
| field | base_version | current_version | target_version |
879+
| name | "A" | "A" | "B" |
880+
| risk_score | 1 | 1 | 2 |
881881
```
882882

883883
#### **Scenario: Rule field has an update and a custom value that are the same**
@@ -897,9 +897,9 @@ And there should be no conflict
897897
CASE: should work the same if rule does not have an existing base version
898898
899899
Examples:
900-
| field |
901-
| name |
902-
| risk_score|
900+
| field | base_version | current_version | target_version |
901+
| name | "A" | "B" | "B" |
902+
| risk_score | 1 | 2 | 2 |
903903
```
904904

905905
#### **Scenario: Rule field has an update and a custom value that are NOT the same**
@@ -919,9 +919,9 @@ And there should be a conflict
919919
CASE: should return target version if rule does not have an existing base version
920920
921921
Examples:
922-
| field |
923-
| name |
924-
| risk_score|
922+
| field | base_version | current_version | target_version |
923+
| name | "A" | "B" | "C" |
924+
| risk_score | 1 | 2 | 3 |
925925
```
926926

927927
### Rule upgrade workflow: viewing rule changes in JSON diff view

0 commit comments

Comments
 (0)