Right, the test site exists in our case because we (try at least to) organize our development around a test driven approach. Which involves an iterative approach. The test site is there and is tested incrementally with several versions. Victor Kane http://awebfactory.com.ar On 8/17/07, Earnie Boyd <earnie@users.sourceforge.net> wrote:
Quoting Victor Kane <victorkane@gmail.com>:
Everything ought to go through a test site, of course, but this becomes a potential point of failure if urgent work is needed and the test site is underused
The only solution is that someone (usually me where I am) has to serve as "head cook and bottlewasher" integrator in the test site.
Scheduling testing is a large complication that should not be avoided just because a deadline is near or past. Testing must be planned in the schedule.
The plot also thickens when customer needs to get content up in parrallel with old version...
But manageable none the less.
Earnie