On Tue, 10 Mar 2015, Tyler Palsulich wrote:
Or, do enough parsers have overlapping test resource dependencies where it makes sense to have them _all_ under one directory?
I believe that most of the test files get used for both detection and parsing unit tests
It would be nice to easily know which files are used for which tests.
5 lines of perl should give you that, or fewer if you don't want to be able to understand the perl... ;-)
Many, but not all of the test files are of the form test<filetype>.<ext> or test<filetype>_<special type/description>.<ext>, which I find makes it fairly easy to spot what files go with what. Not all though. Would fixing the few files not in that format help, or hinder do you think?
Nick
