* Added more output options to the console test runner.
  * Changed Object#id calls to Object#__id__ to remove deprecation
warnings under 1.7.
  * Did a little performance tuning.
  * Fixed a problem in stack trace filtering in Error.filter.
  * Added the ability to pick the runner when running automatically
(thanks to Eivind Eklund).
  * Fixed debugging support in unit.rb.
  * Made the failure caused by running an empty suite clear, consistent,
and changeable.
  * !Removed the return value from Assertions#assert_match.
  * Modified tests to make sure all assertions are returning nil unless
they're explicitly supposed to do something else.
  * !Made TestCase#initialize throw :invalid_test if the test method
specified does not exist (this is in addition to the arity check that
was already in place).
  * !Changed #assert_match to use #=~ instead of #match; it can now
handle strings as patterns, too.
  * Fixed warnings under 1.8 caused by not using a 0 before the decimal
point of floats.

Notes:
  * Test::Unit has been imported in to ruby 1.8. If you're running
against the latest CVS, you shouldn't need to download this!

README:
Unit testing is making waves all over the place, largely due to the fact
that it is a core practice of XP. While XP is great, unit testing has
been around for a long time and has always been a good idea. One of the
keys to good unit testing, though, is not just writing tests, but having
tests. What's the difference? Well, if you just _write_ a test and throw
it away, you have no guarantee that something won't change later which
breaks your code. If, on the other hand, you _have_ tests (obviously you
have to write them first), and run them as often as possible, you slowly
build up a wall of things that cannot break without you immediately
knowing about it. This is when unit testing hits its peak usefulness.

Enter Test::Unit, a framework for unit testing in Ruby, helping you to
design, debug and evaluate your code by making it easy to write and have
tests for it.

Grab the fun at http://www.*-*-*.com/

Happy testing,

Nathaniel

<:((><
+ - -
| RoleModel Software, Inc.
| EQUIP VI

What does this have to do with XP? Do you mean Windows XP?  If so, what makes it
different from the test suites that I've been using before XP came out?

eXtreme programming-- follow the link below:

http://www.xprogramming.com/xpmag/whatisxp.htm

| I'm not familiar with Test::Unit.  I'm certainly familiar with software
| source comming with a set of tests that you are supposed to run.  Is that
| what this is?

You'll notice TDD (Test Driven Development) listed in the list of XP practices
via the link.

Hope this helps-- // Bruce

--
Bruce R. Williams :: [iusris/#ruby-lang] :: http://www.codedbliss.com

  'It does not require a majority to prevail, but rather an irate,
  tireless minority keen to set brush fires in people's minds.'
  -- Samuel Adams

--
Daniel Carrera
Graduate Teaching Assistant.  Math Dept.
University of Maryland.  (301) 405-5137

I have two suggested patches to the console ui.  The "Finished in
<foo> seconds" includes to much precision in the seconds (nobody cares
if it finished in 10.3234323 rather than 10.3234322 seconds), and the
console runner never flushes io when it prints out the progress dots
so they don't function as progress indicators.

--- lib/test/unit/ui/console/testrunner.rb      Tue Feb 11 21:22:33 2003
+++ /home/matt/pkg/stow/ruby-cvs/lib/ruby/1.8/test/unit/ui/console/testrunner.r

           def finished(elapsed_time)
             nl
-            output("Finished in #{elapsed_time} seconds.")
+            output("Finished in %.2f seconds." %
+                   [ elapsed_time ])

               nl

           end

           def output_single(something, level=NORMAL)

+            if (output?(level))


+            end
           end

           def output?(level)

--
matt

Actually I do: that is the only way I can tell that it re-ran sometimes
when I use \C-c \C-c in emacs to re-run the tests.  Otherwise, I'll need
a date stamp or some such.

--
Bil Kleb
NASA Langley Research Center
Hampton, {*filter*}ia, USA

Nathaniel

<:((><
+ - -
| RoleModel Software, Inc.
| EQUIP VI

Nathaniel

<:((><
+ - -
| RoleModel Software, Inc.
| EQUIP VI

--
matt