On Fri, Mar 12, 2010 at 3:48 PM, Ryan Lane <rlane32(a)gmail.com> wrote:
For the grid setup, we were exploring the possibility
of a test runner
that automatically tests commits, and reports them to Code Review,
like the parser tests do now. For the most part, people shouldn't be
hitting the grid, only bots, unless we have a QA team that is doing
something special.
Unless it's very easy to set up Selenium on localhost on all platforms
(is it?), committers should be able to submit code to run on the test
servers. Otherwise, there's no way to tell if your code causes no
regressions without committing it -- and code should be tested
*before* commit. (As well as an automatic run after commit, since we
don't know if people actually did test before committing.) As far as
I know, projects with test servers tend to also allow committers to
submit code changes to them for testing.