On Thu, Sep 23, 2010 at 2:31 PM, Dan Nessett <dnessett(a)yahoo.com> wrote:
Not sure I get this. Here is what I understand would
happen when a
developer checks in a revision:
+ A script runs that manages the various regression tests run on the
revision (e.g., parserTests, PHPUnit tests, the Selenium-based regression
+ The Selenium regression test needs a URL to work with. There are a
fixed set of these defined in httpd.conf.
There's no need to have a fixed set of URLs; just as with Wikimedia's
public-hosted sites you can add individually-addressable wikis dynamically
at whim without touching any Apache configuration. URL rewriting, or
wildcard hostnames, or whatever lets you make as many distinct URLs as you
like, funnel them through a single web server and a single codebase, but
have them running with different databases.
don't need separate entries, and
neither would test1234.r56789.wikimediatesting.org
+ Before assigning one of these to the regression test run, there is a
requirement that it isn't currently busy running a
regression test for a
different revision. So, you need resource access control on the URLs.
If each test run has its own wiki, there's no need to control access -- no
other tests would be trying to access it.