Michael G Schwern wrote:
Another route is to go the "lite" software route. Instead of testing with
Apache and PostgreSQL, test with HTTP::Server::Simple and SQLite. Easier to
install and configure. The downside is you're not testing against your real
production environment so something still
On 3/27/07, Kirrily Robert <[EMAIL PROTECTED]> wrote:
The problem is that all the developer sandbox websites run on one server
that's groaning under the strain. It's in the process of being replaced
but we're not there yet. The upshot of this is that on a good day, the
web tests take ages to ru
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 tes
Kirrily Robert wrote:
> 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 a
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 pro
