From: Eric Leblond <el@stamus-networks.com>
Date: Sun, 18 Apr 2021 10:26:05 +0000 (+0200)
Subject: http-sha256-drop-02: don't use flow_id in test
X-Git-Tag: suricata-6.0.4~92
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=716cbc92c86786d7f0afb18d9c448bc8483a7e85;p=thirdparty%2Fsuricata-verify.git

http-sha256-drop-02: don't use flow_id in test

flow_id has no reason to be fix from a user perspective so we
should not use it in test but use information from the flow
itself.
---

diff --git a/tests/http-sha256-drop-02/test.yaml b/tests/http-sha256-drop-02/test.yaml
index dbdfa31c0..0365fbb23 100644
--- a/tests/http-sha256-drop-02/test.yaml
+++ b/tests/http-sha256-drop-02/test.yaml
@@ -27,10 +27,15 @@ checks:
         alert.signature_id: 2
         pcap_cnt: 103
   - filter:
-      count: 8
+      count: 3
       match:
         event_type: drop
-        flow_id: 746850855319537
+        src_port: 35824
+  - filter:
+      count: 4
+      match:
+        event_type: drop
+        dest_port: 35824
   - filter:
       count: 1
       match:
@@ -43,8 +48,13 @@ checks:
         event_type: drop
         alert.signature_id: 3
         pcap_cnt: 135
+  - filter:
+      count: 1
+      match:
+        event_type: drop
+        src_port: 35820
   - filter:
       count: 7
       match:
         event_type: drop
-        flow_id: 948787333709074
+        dest_port: 35820