From: Jim Weirich Date: 2003-07-17T20:27:51+09:00 Subject: Re: Test::Unit no tests specified On Wed, 2003-07-16 at 18:58, Nathaniel Talbott wrote: > [...] at this point the best I can suggest > is to do as Brian mentions in [ruby-talk:76195] and pull your common code in > to a module instead of a superclass. I've done this with great success. When I worked Dave's Kata 2 (binary chop) exercise, I put all his tests in a module called ChopTests. I then wrote several versions of chop (called chop_iterate, chop_recursive, etc). The unit tests looked like this .... class TestChopIterative < Test::Unit::TestCase alias chop chop_iterate include ChopTests end You can see the full example at ... http://onestepback.org/index.cgi/Tech/Programming/Kata/KataTwoVariation1.rdoc -- -- Jim Weirich jweirich@one.net http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)