[
https://bro-tracker.atlassian.net/browse/BIT-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Siwek updated BIT-671:
--------------------------
Resolution: Rejected
Fix Version/s: (was: 2.4)
Status: Closed (was: Open)
I think this approach may complicate the unit test framework more than it's
worth -- there's already a not-negligible maintenance cost of Bro's unit
testing that will continue to grow as we add tests and I think they currently
do well enough at detecting potential problems.
> Test Bro core and script layer simultaneously
> ---------------------------------------------
>
> Key: BIT-671
> URL: https://bro-tracker.atlassian.net/browse/BIT-671
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: BTest
> Affects Versions: git/master
> Reporter: Matthias Vallentin
>
> If we record all events during testing, say by adding {{events.bst}} to each
> Bro run, we can simultaneously test the core. Moreover, we instantly know
> whether a bug manifests at script land or at the core.
--
This message was sent by Atlassian JIRA
(v6.4-OD-15-055#64014)
_______________________________________________
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
