zeek/testing
Robin Sommer 0767598771 GH-293: Protect copy() against reference cycles.
Reference cycles shouldn't occur but there's nothing really preventing
people from creating them, so may just as well be safe and deal with
them when cloning values. While the code is a bit more cumbersome this
way, it could actually be bit faster as well as it no longer caches
non-mutable values. (I measured it with the test suite: That's about
the same in execution time, maybe tiny little bit faster now;
definitly not slower).
2019-06-03 15:20:30 +00:00
..
btest GH-293: Protect copy() against reference cycles. 2019-06-03 15:20:30 +00:00
coverage More bro-to-zeek renaming in the unit tests 2019-05-16 02:27:54 -05:00
external Rename all BRO-prefixed environment variables 2019-05-22 00:12:31 -05:00
scripts Merge remote-tracking branch 'origin/topic/dnthayer/gh-339' 2019-05-23 20:23:14 -07:00
.gitignore
Makefile Added coverage to .PHONY in Makefile due to testing/coverage 2018-07-30 12:17:40 -07:00
README More bro-to-zeek renaming in the unit tests 2019-05-16 02:27:54 -05:00

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.