We've got a situation where we have a suite of tests for a web app. It
starts of testing the lib/ and whatnot, but eventually gets to the point
where it uses Test::WWW::Mechanize to go fetch stuff from the
developer's sandbox website and do a sanity check on the web application
itself.
The
On 28 Mar 2007, at 01:46, Kirrily Robert wrote:
[snip]
Any suggestions for how to work around this? All I've got so far
is the
idea of splitting out the web tests into another directory, and
treating
them as functional tests that developers would typically run less
often than the unit
