[TIP] unitteset outcomes (pass/fail/xfail/error), humans and automation

jason pellerin jpellerin at gmail.com
Mon Dec 14 08:39:23 PST 2009


On Mon, Dec 14, 2009 at 10:59 AM, Olemis Lang <olemis at gmail.com> wrote:
> On Mon, Dec 14, 2009 at 10:46 AM, holger krekel <holger at merlinux.eu> wrote:
>>
>> Do you have interest in trying to standardize some bits across tools
>> and approaches?  I'd see the goal in having tools that process results
>> somewhat uniformly.
>>
>
> +1

Here's how nose approaches the problem of user-defined error handling:

http://somethingaboutorange.com/mrl/projects/nose/0.11.1/plugins/errorclasses.html
http://somethingaboutorange.com/mrl/projects/nose/0.11.1/doc_tests/test_issue142/errorclass_failure.html

If I remember right, this approach was inspired by/stolen from some
work by Colin Winter around refactoring unittest for py3k.

JP



More information about the testing-in-python mailing list