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 should of course be reported as skipped.) > > Not really a Test::Harness thing, it's up to your test program to do > this. Test::More has facilities to skip blocks of tests or whole test > files. They're explained in the Test::Tutorial.
Hmm. So you're saying that I should modify my tests to skip themselves when they get information that a module they depend on has failed its tests? How do you propose I get that information to the test? > You can use the callback interface, but it's not stable and is subject > to change. In fact, it probably will. I still encourage people to > use it. Well, since I need it for my current method of working, I'll just use it and be aware that it will change. cjs -- Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org Don't you know, in this new Dark Age, we're all light. --XTC
