[Bro-Dev] [Bro-Commits] [git/bro] topic/robin/parallel-btest: Adding group "comm" to communication tests for parallelizing execution with new btest version. (32cb6d6)
gc355804 at ohio.edu
Fri Sep 9 10:32:18 PDT 2011
On 9/9/2011 1:07 PM, Robin Sommer wrote:
> On Fri, Sep 09, 2011 at 12:56 -0400, you wrote:
>> @TEST-PROFILE dataseries sql
> Ah, then I misunderstood how you trigger activating a profile. I was
> assuming there would be something like a command line argument to run
> all tests with, say, profile "dataseries". Wouldn't that be better?
> Then one wouldn't need to add a line to pretty much all tests (nor
> touch them all when adding a new profile).
Yeah, but a lot of alternative logging targets would only really use a
subset of the tests. Testing log rotation, for example, wouldn't make
sense when dealing with an SQL backend. We could use groups to specify
different classes of tests. . . but I'm afraid we'd run into granularity
issues if we went that route (which is the reason I went with tags instead).
So, how about this: in each profile directory, we add a 'tests' file.
This file contains a list of all the tests corresponding to a given
profile. The exception here would be the default profile, for which the
tests file would list all tests that *would not* run (since e.g. some
SQL-specific tests might not make sense when dealing with vanilla log
files, but it would be tedious to manually update this file every time
we added a new test).
And yeah, you're right; there definitely needs to be a command line
option to only run tests associated with a certain profile.
More information about the bro-dev