> I'm a big fan of testing units in isolation. It's easier, faster, and tends to
> more comprehensive and detailed tests. The problem is, if the unit being
> tested has a legitimate dependency on another unit in the suite, isolation
> testing cannot identify interface changes.
I've been vaguely reading the Schwernomatic commentary, and most of it
doesn't interest me directly. I'm not enough of a module-writin' guy to
see how it's gonna help me at all.
Here are my two concerns:
* Please don't make dependencies on *.t as the filenames involved. I'm
personally using Test::Harness to run tests on other files as well.
* Dependencies should be optionally based on something other than just
the timestamp of a file. For instance, I suspect I'd like to be able to
make the date dependency on "SELECT MAX(DateUpdated) FROM Foo".
xoxo,
Andy
--
'Andy Lester [EMAIL PROTECTED]
Programmer/author petdance.com
Daddy parsley.org/quinn Jk'=~/.+/s;print((split//,$&)
[unpack'C*',"n2]3%+>\"34.'%&.'^%4+!o.'"])
