External lib unittests: they're killin me!

Timothee Cour thelastmammoth at gmail.com
Tue May 21 00:58:04 PDT 2013


On Tue, May 21, 2013 at 12:35 AM, Jens Mueller <jens.k.mueller at gmx.de>wrote:

> Jacob Carlborg wrote:
> > On 2013-05-21 03:52, Nick Sabalausky wrote:
> > >Y'know what we need? This compiler flag:
> > >
> > >    -unittest=pagkage.name.*
> >
> > I wouldn't say no to that flag. Hmm, I'm wondering if it's possible
> > to get the same functionality by implementing your own unit test
> > runner.
>
> It is possible and we shouldn't push functionality into the compiler
> when the issue is solvable in a library.
> https://github.com/jkm/dtest (shameless plug) has the command line
> switch --include to specify which modules should be tested.
>
> Jens
>

That looks good, will try. However it doesn't address the issue of
individual unittests (see 2nd post). Compiler support is needed for named
unittests.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20130521/bd0898b6/attachment.html>


More information about the Digitalmars-d mailing list