Improving unit tests

Leandro Lucarella llucax at gmail.com
Tue Nov 11 14:51:33 PST 2008


Gide Nwawudu, el  7 de noviembre a las 23:56 me escribiste:
> On Fri, 07 Nov 2008 16:55:14 -0500, Jason House
> <jason.james.house at gmail.com> wrote:
> 
> >Janderson Wrote:
> >
> >>  > Someone who's a big unittesting fan should write up a proposal on
> >>  > this.  I think unittests are neat and all -- I probably don't use them
> >>  > as much as I should -- but I don't really know what's so great about
> >>  > named unittests or other things people mention that D's unittests
> >>  > lack.  I suspect Walter may be in the same boat.  You can't address a
> >>  > problem if you don't really understand it.
> >>  > --bb
> >> 
> >> Its funny, I was just thinking last night of starting a new thread about 
> >> exactly that.  For me I only ever use unit tests in a simple way however 
> >> I'd like to learn about move advanced features that D is missing.
> >> 
> >> I was originally thinking, maybe unit tests shouldn't be part of D to 
> >> allow for innovation. However then I though, what about if D's unit 
> >> tests where extensible though some language syntax?
> >> 
> >> Questions:
> >> 1) What features are missing from D's unit tests that you miss?
> >
> >Named unit tests
> >Reporting individual failures and continuing. Note that you can recover from module testing failures, but not from individual tests.
> >Compile-time unit tests, especially when making release builds.
> >
> 
> Nestable named unittest would be nice. If one group fails, report the
> error and move onto the next.

Also I think a "check" which only report errors but don't stop the current
test could be useful. Most unit testing frameworks provides that.

-- 
Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/
----------------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------------
The diference is simple: hackers build things, crackers break them.



More information about the Digitalmars-d mailing list