mirror of
https://github.com/zeek/zeek.git
synced 2025-10-07 09:08:20 +00:00
![]() We previously used the Spicy plugin's `Spicy::available` to test for Spicy support. However, having Spicy support does not necessarily mean that we have built Zeek with its in-tree Spicy analyzers: the Spicy plugin could have been pulled in from external. The new BIF now reliably tells us whether the Spicy analyzers are available; its result corresponds to what `zeek-config --have-spicy-analyzers` returns as well. We also move the two current checks over to use this BIF. (Note: I refrained from renaming the CMake-side `USE_SPICY_ANALYERS` to `HAVE_SPICY_ANALYZERS`. We should do this eventually for consistency, but I didn't want to make more changes than necessary right now.) |
||
---|---|---|
.. | ||
benchmark/broker | ||
btest | ||
coverage | ||
external | ||
scripts | ||
.gitignore | ||
CMakeLists.txt | ||
Makefile | ||
README |
This directory contains suites for testing for Zeek's correct operation: btest/ An ever-growing set of small unit tests testing Zeek's functionality. external/ A framework for downloading additional test sets that run more complex Zeek configuration on larger traces files. Due to their size, these are not included directly. See the README for more information. scripts/ Helpers scripts used by some tests.