Re: Possible solution for export : `unittest export`?

[Dominikus Dittes Scherkl via Digitalmars-d]

What I meant is, of course you cannot test everything with 
unittest. It has a reason that there exist other types of test. 
But that should not hold anybody back from unit-testing as much 
as possible. If nothing else this is useful because unit-tests 
are by far the cheapest tests. And within a library, it should 
always be possible to reach a 100% code coverage with unit tests 
alone.
For a program with much user interaction this may not be 
possible, but that is pretty much out of scope for exported 
templates.