Mirror/zeek
1
0
Fork 0
mirror of https://github.com/zeek/zeek.git synced 2025-10-02 14:48:21 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Checkpoint.

Browse source
This commit is contained in:
Robin Sommer 2011-06-25 21:06:19 -07:00
parent ff331763ef
commit c2524b995b
2 changed files with 8 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

4
testing/external/Makefile vendored
View file

@ -1,8 +1,8 @@
PUBLIC_REPO=/home/robin/tmp/bro-tests PUBLIC_REPO=git://git.bro-ids.org/bro-testing
all: all:
@for repo in *.git; do ( cd $$repo && btest ); done @for repo in *.git; do (echo "==== $$repo" && cd $$repo && btest ); echo; done
init: init:
git clone $(PUBLIC_REPO) public.git git clone $(PUBLIC_REPO) public.git

15
testing/external/README vendored
View file

@ -38,7 +38,7 @@ test repository:
.. console: .. console:
> cd public.git > cd bro-testing.git
> btest > btest
All the standard ``btest`` options can be used to run individual All the standard ``btest`` options can be used to run individual
@ -51,7 +51,7 @@ To update a test's baseline, first run ``btest`` in update mode:
.. console: .. console:
> cd public.git > cd bro-testing.git
> btest -U tests/test-you-want-to-update > btest -U tests/test-you-want-to-update
Then use ``git`` to commit the changes and push the changes upstream Then use ``git`` to commit the changes and push the changes upstream
@ -66,19 +66,16 @@ public one. A helper script is provided to set up such a repository:
.. console: .. console:
> ./scripts/create-new-repo private-repo /home/git/bro-private-repo > ./scripts/create-new-repo <repo-name> <repo-url>
The first argument is the local name of the repository (it will be The first argument is the local name of the repository (it will be
cloned into ``<name>.git``); and then second is the path to the (bare) cloned into ``<repo-name>.git``); and then second is the path to the
git repository. The repository will be initialized with a few standard git repository. The repository will be initialized with a few standard
directories as well as a skeleton test in ``<name>.git/tests``. You directories as well as a skeleton test in ``<name>.git/tests``. You
can then edit files as needed (and in particular add traces to can then edit files as needed (and in particular add traces to
``<name>.git/traces``). ``<name>.git/traces``).
If you want the repository to be located somewhere else than the local If you already have such a private test repository that you want to
machine, just push the created local repository to the right place,
delete ``<name>.git``, and clone from the remote location. Likewise,
if you already have such a private test repository that you want to
include into the test suite, clone it directly into include into the test suite, clone it directly into
``<name>.git/tests``. ``<repo-name>.git``.