[TIP] Test discovery for unittest

[Michael Gratton]

On Fri, 2009-04-03 at 19:27 -0700, C. Titus Brown wrote:
> -> Michael Foord wrote:
> -> > For those who might be interested I've been playing with test discovery 
> -> > for unittest. I have a simple working prototype in about 80'ish lines of 
> -> > code.
> -> >
> -> > http://code.google.com/p/unittest-ext/source/browse/trunk/discovery.py
> -> >
> -> > I'll be using  this sandbox to turn unittest into a package as well.
> 
> Then Ned Batchelder wrote:
> -> This sounds like what nose does.  Are you taking a different approach?
> 
> I hope he is; now that nose and py.test have converged on both test
> discovery and plugin running, there's room for another unit test
> discovery framework.  I'd prefer something as different as possible, in
> fact; while I'm a huge fan of the simplicity and readability of nose
> test files, I know that some people really like e.g. deep inheritance
> hierarchies of test code.  A test discovery framework that supported a
> much more complicated test layout would really fill an unoccupied niche,
> I feel.

What about using decorators:
<http://lists.idyll.org/pipermail/testing-in-python/2009-April/001418.html>?

/Mike

-- 
Michael Gratton <michael at quuxo.com>     
Quuxo Software <http://web.quuxo.com/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.idyll.org/pipermail/testing-in-python/attachments/20090404/45bcba54/attachment.pgp