Introduce basic test triggering when zeek -r triggers script errors

I wonder if there's another one that covers errors during a basic zeek -r,
but didn't seem like.
This commit is contained in:
Arne Welzel 2022-09-08 18:32:13 +02:00
parent d5cd023dff
commit 700a9a4f37
4 changed files with 28 additions and 0 deletions

View file

@ -0,0 +1,2 @@
### BTest baseline data generated by btest-diff. Do not edit. Use "btest -U/-u" to update. Requires BTest >= 0.63.
<...>/basic-no-errors.test, line 13: Hello, Zeek!

View file

@ -0,0 +1 @@
### BTest baseline data generated by btest-diff. Do not edit. Use "btest -U/-u" to update. Requires BTest >= 0.63.

View file

@ -0,0 +1,11 @@
### BTest baseline data generated by btest-diff. Do not edit. Use "btest -U/-u" to update. Requires BTest >= 0.63.
#separator \x09
#set_separator ,
#empty_field (empty)
#unset_field -
#path reporter
#open XXXX-XX-XX-XX-XX-XX
#fields ts level message location
#types time enum string string
XXXXXXXXXX.XXXXXX Reporter::INFO Hello, Zeek! <...>/basic-no-errors.test, line 13
#close XXXX-XX-XX-XX-XX-XX