Separate unit tests and integration tests

[jblachly]

Rough heuristics:

Uses external file (BAM, etc.) => integration test

[charlesgregory]

@jblachly Do you have a proposed way to do this? Should we run place all integration tests under the test folder? How would this affect coverage metrics?

[jblachly]

well from software eng perspective i may be wrong, but I think it is up to the unit tests to exercise all the lines of code and thereby contribute to the coverage metric; wouldn't worry about how integration tests affect this.

I would make a separate dub package and put it under test/ (currently I have a bunch of random source files there already as a start). You could either do a single dubfile (which requires alternate configuration block for each test program), or separate dubfiles for each, or forget dub and use Makefile possibly.