[TIP] Test reporting in unittest (and plugins)

Michael Foord fuzzyman at voidspace.org.uk
Tue Aug 3 08:02:52 PDT 2010


On 03/08/2010 15:52, Jonathan Lange wrote:
> On Tue, Aug 3, 2010 at 3:28 PM, Michael Foord<michael at voidspace.org.uk>  wrote:
> ...
>    
>>>> What is the mechanism (and use cases) for custom outcomes?
>>>>
>>>>          
>>> To be honest, I don't need custom outcomes, so I don't know the use
>>> cases. But here's what you could do.
>>>
>>>        
> [snip mechanism]
>    
>>>        
>> Ha, just like a programmer. I ask for use case and you suggest
>> implementation. :-)
>>
>>      
> Actually, you asked for mechanism. What I gave was not my
> recommendation (although I incorrectly implied so), but rather, it's
> how testtools works now.
>
>    

Ah, I thought you were just suggesting an implementation - and yes I did 
ask for mechanism. My apologies. :-)

Michael Foord

> jml
>
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python
>    


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

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