I would use a continuous integration server like Jenkins . Typically, CI servers are used to create an application for every commit in the repository, but itโs just as easy to manually run the โbuildโ, which is only to run all your tests (and record the results and run code coverage if you want, etc.) e).
I found that Jenkins is very easy to set up (I followed a good tutorial at http://blog.jepamedia.org/2009/10/28/continuous-integration-for-php-with-hudson ) is the only extra work I besides creating the build script you had to make sure that Selenium RC was running on the test machine, and it looks like you already did it.
To make it even easier, if you configured Jenkins (or any other CI server, I'm sure) to build a commit in your repository, then you donโt even need to go into the test machine to edit the tests - anyone can run the tests, the CI server will run tests, and everyone can see the results. Not so important if you are developing a solo, but still a convenient trick.
source share