[TIP] unittest2 and the future of nose
fuzzyman at voidspace.org.uk
Thu Mar 4 15:04:29 PST 2010
On 04/03/2010 22:58, Robert Collins wrote:
> On Thu, 2010-03-04 at 22:29 +0000, Michael Foord wrote:
>> Right - unittest extensibility is the *really* big wart on unittest
>> I would like to address. That means some kind of plugin /
>> mechanism that doesn't suck. It needs a lot of thinking about and
>> a bit (but not too much) talking about.
> I have some experience and a *lot* of interest in this. Please do raise
> specific proposals here...
I will definitely raise issues and specific proposals for discussion.
> as you know I have a few ticking along in
> testtools for betatesting. (testtools is about equal to unittest2, its
> more extensible and has classes demonstrating that, but it doesn't
> support a couple of minor 2.7 stdlib features yet).
> One thing in particular - consider deleting TestRunner at this point:
> I've found, with the startTestRun and stopTestRun methods on TestResult
> that I no longer need a Runner class at all in my front ends.
I'll consider that. Not entirely sure what it gains us - the
functionality currently in TextTestRunner would just need to move into
TestResult.startTestRun / stopTestRun. One less class (and therefore
less confusion - but also more out of date docs / tutorials) but not
much less code.
All the best,
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
More information about the testing-in-python