On Tuesday 08 May 2007 17:39:14 James Keenan wrote: > In my never-ending quest for complete code coverage, I had to devise > a way to test both branches in that return statement, i.e., test > under circumstances in which 'DEVELOPING' both does and -- here's the > tricky part -- does not exist. The only way I could do the latter > was to copy the relevant files into a temporary directory and, for > certain tests, not copy 'DEVELOPING' along with them. It's very > hackish, but it did enable me to get to full coverage of that statement.
If the test has to be that complex, we can easily live with less than full coverage. If file tests in Perl don't work, we have bigger problems than less than full coverage. -- c
