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 tests.
Suggestions:
* Buy some more hardware. Could well be the cheapest and easiest
option :-)
* Tweak T:W:M so timeouts SKIP rather than fail?
* Add some code around the web tests so if more than N folk are
running them they're skipped?
Cheers,
Adrian
