From: Suraj N. Kurapati [mailto:skurapat / ucsc.edu]
Sent: Tuesday, May 30, 2006 5:22 PM
> Victor Shepelev wrote:
> > 4. optional code speed analysis (like benchmarking "how long it rans",
> > profiling "what rans so long") after each test
> 
> See the 'profile' library provided in Ruby core.
> 
> ruby -r profile

No-no :)
I know, how to do it _technically_.
What I what to know is how to _organize_ all the task.
Just for now I do only unit-tests, but _when_ to run benchmarking /
profiling / coverage analysis / dependency analysis and so on? Must those
tasks be ran automataically? When (after any code change, like unit tests?)
This is a question.

V.