From: David Garamond <lists@...6.isreserved.com>
Date: 2004-02-28T22:58:17+09:00
Subject: Test::Unit: multiple level of testing

I'd like to get suggestions on how to use Test::Unit to fulfill the 
following requirement simply and elegantly:

Each component (basically a Class, which most of the time reside in a 
single source file) will have a unit test. There should be three levels 
of unit testing:

1) normal level, which will be executed regularly during development. 
This is basically "the" unit test as we usually understand and use. It 
should do functional and regression testing for each and every method, 
to make sure each functionality is implemented correctly and past bugs 
do not creep in again.

2) diagnostic level, which will usually be executed if there is 
something wrong going on. This level should include all tests from the 
normal level, but the output/error messages should be more verbose than 
level #1 (under normal circumstances, the verbosity of output/error 
messages from #2 is more than necessary). Additionally, this level 
should also include things like memory leak test, some performance test, 
  etc.

3) same as #2, but more verbose and rigorous. We don't normally run 
tests at these level unless there is problem that can't be tracked using 
#1 and #2.

-- 
dave