On Mon, Oct 20, 2003 at 10:47:02AM -0700, Ovid wrote: > The way we're doing tests is simply foolish and we could experience some significant > productivity > gains if we were to improve the test performance. Of course, I think it's fair to > point out that > much of the performance is due to a poorly thought out testing strategy. If the > tests were > designed better, I'd have less room to complain about how long they take to run.
One other interesting idea I had, although I have no idea how practical it is at all really, it to have some way of telling from the Devel::Cover reports (or otherwise) what tests aren't actually adding any value as the stuff they're testing is already adequately tested elsewhere. Now, yes, I know this is pretty much impossible as you need to take into account that they may be testing with different values of data that might be important, but I can't help feeling there's _something_ that could be worked out. Even if all it's doing is giving a pointer to potential areas that could be re-examined... Tony
