I mean a way of naming and storing a bunch of related tests. TestSuite
gives you the test composition abstraction, you need to store a
TestSuite for the "expected failures", and then separately run the
"expected failure" and the "regression" (everything else) parts of the
test suite.

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.

Daniel

Julian Fitzell <julian at beta4.com> wrote:
> Can you expand more on what you mean by organizing structure?
> 
> Daniel Vainsencher wrote:
> > I think the need you're addressing could be better met with some
> > organizing structure on top of TestCases... and that would be useful. I
> > remember the mess it was to find a few score of RB TestCases not
> > working, and then finding out that they are actually in implicit layers
> > - the parser should be fixed before the refactorings, and so forth.
> > Would have been nice if the layers were explicit.
> > 
> > Daniel