zeek/testing
Arne Welzel 7b4b1779bf Event: Use -1.0 for undefined/unset timestamps
This can happen if either there's no network timestamp associated with
an event, or there's currently no event being dispatched. Using 0.0
isn't great as it's the normal start timestamp before reading a network
packet. Using -1.0 gives the caller a chance to check and realize what's
going on.
2025-06-02 17:31:36 +02:00
..
benchmark/broker
btest Event: Use -1.0 for undefined/unset timestamps 2025-06-02 17:31:36 +02:00
builtin-plugins CI: Add external plugins to builtin plugins task 2025-03-31 14:19:18 +02:00
coverage Swap pre-commit yapf for ruff/ruff-format, fix findings 2024-12-11 11:08:37 -07:00
external Merge remote-tracking branch 'origin/topic/awelzel/4405-quic-fragmented-crypto' 2025-05-05 14:40:59 +02:00
scripts External tests: add removed logs to CT list to prevent baseline changes 2025-04-28 16:42:52 +01:00
.gitignore
CMakeLists.txt Integrate the Spicy plugin into Zeek proper. 2023-05-16 10:17:45 +02:00
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.