On Tue, Mar 26, 2002 at 01:47:38PM +0900, Curt Sampson wrote:
> On Mon, 25 Mar 2002, Michael G Schwern wrote:
>
> > > 2. Skip test of code where dependencies have been tested and found
> > > to be failing. For example, if the test for the database connection
> > > module fails, nothin
On Mon, 25 Mar 2002, Michael G Schwern wrote:
> > 2. Skip test of code where dependencies have been tested and found
> > to be failing. For example, if the test for the database connection
> > module fails, nothing that uses that module should have its test
> > run. (The tests sho
On Mon, Mar 25, 2002 at 04:35:52PM +0900, Curt Sampson wrote:
> I'm setting a unit testing system for a pile of code right now which
> is going to expand into hundreds of tests. I've currently got a simple
> program that finds all of the tests in the system and hands this list to
> Test::Harness t
I'm setting a unit testing system for a pile of code right now which
is going to expand into hundreds of tests. I've currently got a simple
program that finds all of the tests in the system and hands this list to
Test::Harness to be run.
However, I'd like to be able to do two things:
1. Run
