[TIP] The role of nose2 in relation to unittest2

Arve Knudsen arve.knudsen at gmail.com
Sun Sep 26 11:43:57 PDT 2010


As I've been tinkering with nose2 and unittest2, and got to know the two
better, the question has emerged as to exactly which role nose2 is meant to
fulfill on top of unittest2.

With the original unittest, nose's raison de vivre is pretty clear; seeing
as unittest is rather an archaic/inflexible framework, there is an obvious
need of a more modern, practical alternative. nose offers such an improved
alternative. unittest2 on the other hand changes the game, as it is being
designed with today's needs in mind, and is plugin-based (like nose). That
unittest2 is a sound design is evidenced by the fact that nose2 implements
its functionality as unittest2 plugins.

Given that the meat of nose2 (excepting the runner) is already unittest2
plugins, how does one define nose2's role? Why is there even a nose2 runner,
can't one simply develop plugins to integrate with the unittest2 runner?
More to the point, when now wanting to extend unittest2, why write plugins
for nose2 rather than unittest2 itself?

Hope these questions make sense :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20100926/d8e982b8/attachment.htm>

More information about the testing-in-python mailing list