[TIP] unittest2 discovery / doctest integration?

Michael Foord fuzzyman at voidspace.org.uk
Thu Apr 29 07:27:05 PDT 2010

On 28/04/2010 22:51, Jim Fulton wrote:
> [snip...]
> Talking about unittest is rather hard because there are so many ways
> to use it and the docs are rather challenging.

I'm hoping to improve the documentation before the 2.7 final release.

> When we create
> TestCase classes, they typycally define many methods that are run as
> individual tests. I have no idea whether these become individual test
> cases or not, and I'm too lazy to look. :)

Individual test methods are run as individual TestCase instances.

All the best,


> The various test finders have
> no trouble finding these classes and doing the right thing with
> them. It would be easy enough to create a TestCase subclass that
> handled multiple doc tests in much the same way that TestCase
> handles multiple test methods.
> If I was thinking in a test-case centric rather than suite-centric
> way, I'm sure that I could come up with a different API that handled
> multiple doctests just fine.
> Jim
> --
> Jim Fulton
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python


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 mailing list