From: nathaniel@...
Date: 2002-12-20T01:05:19+09:00
Subject: Re: [ANN] Test::Unit 0.1.5

Matt Armstrong [mailto:matt@lickey.com] wrote:

> <nathaniel@NOSPAMtalbott.ws> writes:
> 
> > What with all the holiday cheer going around (who can't be cheerful 
> > with a preview of 1.8 by Christmas?!?) I had to make my own little 
> > contribution to the glee...
> 
> Thumbs up.  I ran the gamut of my existing tests with no 
> problem. They make use of the RubyUnit compatibility layer, 
> which I guess isolates me from setup -vs- set_up issues, etc 
> (wasn't there a HUGE thread on the relative merits of each 
> name?  :-) ).

Yeah. I don't want to talk about it.

;-)


> Running with RubyUnit natively runs roughly 2.5 times faster 
> than with Test::Unit's RubyUnit compatibility layer.  20 -vs- 
> 54 seconds under ruby CVS.  Is this a known issue?  Do you 
> think this is the compatibility layer being inefficient, or 
> is Test::Unit just slower?

Probably Test::Unit being slower. I've never run a profiler on it, as
I've been more concerned with getting the API right than in making it
fast. However, it's about time to make it fast, so I've added something
to the TODO regarding optimization.


> It bothers me only slightly to know that most of the time I 
> spend waiting for Test::Unit to finish is time spent in 
> Test::Unit and not my tests.  Optimization can come later.

Indeed. "Make it run, make it right, make it fast, in that order." I
daily wish that all programmers would make that their mantra.

Thanks for the feedback,


Nathaniel

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