I'm interested in developing new protocol support for Packetbeat. As such I've followed the beats "CONTRIBUTING.md" guide and the docs on "Adding a New Protocol".
I've set up my Golang environment* and I can successfully run
make integration-tests from the "packetbeat" subdirectory and see all the tests pass.
make system-tests separately (or part of
make testsuite) simply returns "Ran 0 tests in 0.003s".
I can see the "packetbeat/tests/system/" directory contains a variety of tests. If I run
. build/python-env/bin/activate ; nosetests tests/system/* directly I see "Ran 89 tests in 0.027s" but they all fail with "ImportError: No module named beat.beat".
Have I missed a step in configuring my environment for contributing?
*I'm running Ubuntu 16.04 with Golang 1.6.2, Python 2.7.12, and Docker 1.11.2. I initially had some trouble with
go vet in the make scripts as it seems that the go commands do not like symlinks under the GOPATH but rsyncing is fine.