I don't know what you mean by "using prove"? And, you're right, that is the best way to develop a module I think.
Some tests cannot be run unless certain functions run to setup the state, so I want to formally test the prereq functions to make sure they are returning the correct number of return values etc, in the earlier trivial tests, but in the subsequent tests that concentrate on a different subset of functions they will need to use the previous functions to set up the state, so I only want to test that the function succeeded in setting up the state, but not that it is capable of returning the correct number of return values and working under every imaginable legitimate permutation yet again. I don't know if I'm making sense. ----- Original Message ----- From: "Andy Lester" <[EMAIL PROTECTED]> To: "Tim Harsch" <[EMAIL PROTECTED]> Cc: "Perl Mod Authors" <[EMAIL PROTECTED]> Sent: Friday, April 02, 2004 11:52 AM Subject: Re: running tests > > No. But there are certain classes of functions of the module that don't > > work until others have been run. So others should have been tested > > So some tests are setting up other ones, then? > > One of my goals when writing tests is to make everything as independent > as possible, so that I can run a single test (using prove) as part of my > development process. > > Write the test. > Code the code. > Run the test. > Fix the code. > Run the test. > etc. > > xoa > > > -- > Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
