From 98181dd67cce4916da00fc4148fa40f225372b28 Mon Sep 17 00:00:00 2001 From: Jon Siwek Date: Tue, 2 Oct 2018 16:05:10 -0500 Subject: [PATCH] Update testing/btest/README --- CHANGES | 4 ++++ VERSION | 2 +- testing/btest/README | 7 ++----- 3 files changed, 7 insertions(+), 6 deletions(-) diff --git a/CHANGES b/CHANGES index 57525ad3da..1aca9c47b3 100644 --- a/CHANGES +++ b/CHANGES @@ -1,4 +1,8 @@ +2.6-beta2-17 | 2018-10-02 16:05:10 -0500 + + * Update testing/btest/README (Jon Siwek, Corelight) + 2.6-beta2-14 | 2018-09-25 16:38:29 -0500 * Add some missing @TEST-REQUIRES to a few tests (Daniel Thayer) diff --git a/VERSION b/VERSION index 6174f5ca99..11e036dcbc 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -2.6-beta2-14 +2.6-beta2-17 diff --git a/testing/btest/README b/testing/btest/README index a635251939..037fc42647 100644 --- a/testing/btest/README +++ b/testing/btest/README @@ -1,7 +1,7 @@ This a test suite of small "unit tests" that verify individual pieces of Bro functionality. They all utilize BTest, a simple framework/driver for writing unit tests. More information about BTest can be found at -http://www.bro.org/development/btest.html +https://github.com/bro/btest The test suite's BTest configuration is handled through the ``btest.cfg`` file. Of particular interest is the "TestDirs" settings, @@ -61,7 +61,7 @@ Adding Tests ============= See either the `BTest documentation -`_ or the existing unit +`_ or the existing unit tests for examples of what they actually look like. The essential components of a new test include: @@ -80,6 +80,3 @@ If you create a new top-level testing directory for collecting related tests, then you'll need to add it to the list of ``TestDirs`` in ``btest.cfg``. Do this only if your test really doesn't fit logically in any of the extant directories. - -Note that any new test you add this way will automatically be included -in the testing done in the NMI automated build & test environment.