External lib unittests: they're killin me!

Kagamin spam at here.lot
Thu May 23 06:47:09 PDT 2013


On Wednesday, 22 May 2013 at 17:06:59 UTC, Timothee Cour wrote:
> it's only module level granularity.
>
> I agree that a library solution is the way to go, however there 
> needs to be
> a way to have finer granularity, ie being able to call 
> individual unittests.
> I gave the reasons in the 2nd post in this thread. Syntax would 
> be:
> unittest(test_fun){...}
> having a short syntax such as this will make people use it.
>
> digressing, I wish there would be a simple non-anonymous way to 
> vote for
> such features, to see whether most people agree/disagree. It's 
> easier than
> voting by email, which invariably gets lost in digressions (as 
> I'm doing
> here).

For a real life project you probably need a unittest framework. 
Current approach is for an optimistic case when you mostly have 
green test runs and just unittests are enough to test the whole 
system.


More information about the Digitalmars-d mailing list