[TIP] Test reporting in unittest (and plugins)

jason pellerin jpellerin at gmail.com
Mon Aug 2 13:39:40 PDT 2010

On Mon, Aug 2, 2010 at 10:51 AM, Michael Foord <michael at voidspace.org.uk> wrote:
> Hello all,
> My proposal is that we add a new method to the TestResult addDetail (or
> similar) that stores a data structure representing the outcome. The default
> data structure will be available in the stopTest event for plugins to
> modify. The textual parts of the result, like the description, will have a
> list for extra bits to be prepended / appended so that plugins can add extra
> information without stomping on information added by other plugins.


This will make supporting custom outcomes like nose does even easier
than it already was. :)  (The poorly-named and -explained errormaster
plugin in my bb repo is a custom outcomes plugin. I had jargon fail in
trying to explain it.)


More information about the testing-in-python mailing list