[TIP] unittestgui (was: Green and Red bars)

Mark Roddy markroddy at gmail.com
Wed Oct 27 18:33:27 PDT 2010

On Thu, Oct 21, 2010 at 7:54 PM, Mark Roddy <markroddy at gmail.com> wrote:
> On Thu, Oct 21, 2010 at 5:44 PM, Michael Foord
> <fuzzyman at voidspace.org.uk> wrote:
>>  On 21/10/2010 21:44, Mark Roddy wrote:
>>> [snip...]
>>> If anyone's interested, I did a small proof of concept on converting
>>> the gui to use test discovery instead of a user specified callable and
>>> posted it to bitbucket.  I'll look into how bad the Python 3
>>> conversion would be, though I think it might make more sense to iron
>>> out what changes need to be made to better support discover before
>>> doing a fork to support 3.x (if necessary).
>>> https://bitbucket.org/markroddy/unittestgui
>> That's actually *really* nice. :-)
>> Feature requests (all of which are easy individually except the last
>> one...):
>> * Fix the width of the window so it doesn't jitter around when displaying
>> different length test names at the bottom
> Actually having a little problem w/this one, due largely to not having
> worked with tk before.  Will keep banging on this one till I figure
> out unless someone else is more familiar.  Seems the status frame is
> expanding based on the length of the test name.  I can't seem to
> figure out how to prevent this.
>> * Support for *showing* numbers of skipped and expected failure tests
> Done.
>> * When test discovery starts perhaps print a message to the window showing
>> the directory discovery was started in
> Done.
>> * Help and about are wrong and can probably just go...
> Done.
>> * An 'advanced' panel that lets you parameterise the discovery (change the
>> glob pattern for finding tests for example)
> Not done, but high on my priority list. The naming convention used
> where I work doesn't follow the default globbing pattern so I need to
> override this myself.

I've added the last two of Michael's feature requests (fix window
resizing issue and ability to set advanced discovery options).
They're in my bitbucket repo now:

Questions/comments/feedback are welcome and appreciated.


More information about the testing-in-python mailing list