[TIP] unittest & TDD

Laura Creighton lac at openend.se
Sun Mar 11 08:30:12 PDT 2007

In a message of Sun, 11 Mar 2007 08:35:32 EST, "Atul Varma" writes:
>On 3/4/07, Bob Ippolito <bob at redivi.com> wrote:
>> I agree that unittest is straightforward, but it's annoying (on its
>> own). Too much unnecessary cruft.
>I agree.  Out of curiosity, is there any movement towards making
>py.test or nose a part of Python's standard library?  The main reason
>my company used unittest is, quite honestly, because we didn't look at
>any other testing options when we started writing our unit tests,
>assuming that the testing framework that shipped with Python was just
>"the one way to do it" (a la Python's motto).  We weren't huge fans of
>its complexity (or rather, the boilerplate cruft caused by said
>complexity), but we dealt with it.  The fact that unittest was pretty
>well documented helped a lot, too, but as soon as I saw py.test I had
>wished I'd known about it before I started writing unit tests.
>- Atul

I've written a nice tool that automatically converts your
unittests into py.tests.  It's part of the py.test distribution.


More information about the testing-in-python mailing list