aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorPeter Wu <peter@lekensteyn.nl>2019-01-24 13:44:49 +0100
committerPeter Wu <peter@lekensteyn.nl>2019-01-24 18:24:00 +0000
commit198c5a2cac3b954c8c3d8357ae9c1070e1eae594 (patch)
tree978783744969713a50b181b49a54c7bcc5f1d857 /doc
parenta946eb3141ce4942852ae8f3c28c5ebfaa6943bb (diff)
test/dfilter: be explicit with the expected error message
Instead of just reporting a mismatching error code, include the program output. This should help tracking down unexpected errors. While at it, check the expected error message too. Change-Id: Ib8fe51cc06b795bb54bfe1e6eaa828c6ba1128ef Reviewed-on: https://code.wireshark.org/review/31714 Petri-Dish: Peter Wu <peter@lekensteyn.nl> Tested-by: Petri Dish Buildbot Reviewed-by: Peter Wu <peter@lekensteyn.nl>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.display_filter8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/README.display_filter b/doc/README.display_filter
index bea42518d2..5d3a76b9bc 100644
--- a/doc/README.display_filter
+++ b/doc/README.display_filter
@@ -574,11 +574,11 @@ checkDFilterCount(dfilter, expected_count)
matches is not the same as failure to compile the display
filter string.
-checkDFilterFail(dfilter)
+checkDFilterFail(dfilter, error)
- This will run tshark with the display filter, and
- assert that tshark fails. This is useful when expecting
- display filter syntax errors to be caught.
+ This will run dftest with the display filter, and check
+ that it fails with a given error message. This is useful
+ when expecting display filter syntax errors to be caught.
To execute tests: