In <47BF980E.3070506 / gmail.com>
  "Re: Test::Unit maintainer" on Sat, 23 Feb 2008 12:50:34 +0900,
  Phlip <phlip2005 / gmail.com> wrote:

> > I'll do so. And some property set methods will be added. e.g.:
> > 
> >   class MyGenericTestCase < Test::Unit::TestCase
> >     setup # or other name
> >     def my_setup
> >       ... # will be called even if #setup is overrode.
> 
> I suspect folks typically use 'super' there, right?

Do your test cases call super in setup? It's difficult to
force users to call super because TestCase#setup has not
been forced to call super.

> That's why I said "like"! Folks will need many hooks into the system.
> 
> In general, RubyUnit's innards remind me of "Java-style Ruby". Nothing personal. 
> But Ruby generally lets us extend so much more subtly, without all those hooks 
> hanging out.

What are 'those hooks'? Broken down methods or
setup/teardown methods?


Thanks,
--
kou