zeek/testing
Johanna Amann 58613f0313 Introduce new c$failed_analyzers field
This field is used internally to trace which analyzers already had a
violation. This is mostly used to prevent duplicate logging.

In the past, c$service_violation was used for a similar purpose -
however it has slightly different semantics. Where c$failed_analyzers
tracks analyzers that were removed due to a violation,
c$service_violation tracks violations - and doesn't care if an analyzer
was actually removed due to it.
2025-06-04 12:07:13 +01:00
..
benchmark/broker
btest Introduce new c$failed_analyzers field 2025-06-04 12:07:13 +01: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 Settle on analyzer.log for the dpd.log replacement 2025-06-03 17:33:36 +01:00
scripts Settle on analyzer.log for the dpd.log replacement 2025-06-03 17:33:36 +01:00
.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.