Ah. Then I guess Julian is right, and some new GUI would be needed.
Could be nice to have one that shows a heirarchy with the TestSuites,
and in each the tests it corresponds to.

Daniel

Colin Putney <cputney at wiresong.ca> wrote:
> 
> On Friday, August 1, 2003, at 07:18  AM, Daniel Vainsencher wrote:
> 
> > This would require a little supporting UI and process to use, but it
> > doesn't seem to require a lot of work. I don't know but I've been told
> > that TestBrowser allows one to partition the tests more logically. 
> > Maybe
> > it supports TestSuites somehow.
> 
> That might have been me, describing why I prefer TestBrowser to 
> BrowseUnit. As far as I know TestBrowser doesn't do any thing with 
> TestSuites.
> 
> In case any one cares, here's what I was talking about: BrowseUnit 
> requires a 1:1 mapping between TestCases and the classes they test, and 
> uses a class naming convention to figure out the mapping. TestBrowser, 
> on the other hand, just filters out any classes that don't descend from 
> TestCase.
> 
> I prefer to organize my test methods into TestCases according to the 
> set up they require rather than what they test. This works fine in 
> TestBrowser, but not in BrowseUnit.
> 
> Colin