[TIP] Green and Red bars
olemis at gmail.com
Thu Oct 21 08:01:17 PDT 2010
On Thu, Oct 21, 2010 at 9:52 AM, Michael Foord
<fuzzyman at voidspace.org.uk> wrote:
> On 21/10/2010 15:46, Olemis Lang wrote:
>> On Thu, Oct 21, 2010 at 6:42 AM, Alexandre Fayolle
>> <alexandre.fayolle at logilab.fr> wrote:
>>> On Saturday 09 October 2010 22:37:10 Natalia Bidart wrote:
>>>> The reason of my writing is that I'll be giving a talk about Testing
>>>> at PyCon Argentina 2010, which will take place next October 15th and
>>>> 16th, and I need some input from you all. I'm very fond to the concept
>>>> of "getting a green bar" (ergo also to the concept of "red bar"), but
>>>> I'm finding some problems on actually getting a *green* or *red* bar
>>>> using the unittest runner.
>>> The original pyunit shipped with a tkinter gui (unittestgui) with the
>>> green/red bar. It has not made it to the standard library, but is still
>>> available in the python-unit package in Debian.
>>> See http://pyunit.sourceforge.net/ for sourcecode, screenshots, etc.
>>> Porting to unittest2 should not be too complicated.
>> What's the source of incompatibility ?
>> Is it that unittest2 test suites are different to legacy unittest's ?
>> Or is it about the test runner ?
> Plus it won't know anything about skips or expected failures.
Yes , this is a recent addition, now I get it.
> That may not
> be an issue though. Changing it to import from unittest2 rather than
> unittest would *probably* be enough. unittest itself (on which unittest2 is
> built) has changed a great deal since that code was written though...
Is it a good idea to add a similar Tkinter GUI runner in stdlib (even
if it is outside unittest module , let's say e.g. in unittestgui
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
More information about the testing-in-python