This isn’t something I’ve had a chance to try yet, but after seeing Shawn’s presentation at Drupal Summit, I’m certainly very interested and would like to try setting up a similar CI/automated test framework.
Running tests in the browser is time consuming. In this post we’ll look at ways to automate the testing process. By the time you’re finished reading, you’ll know how to receive notifications with test results for your custom code each time you make a commit to your remote version control repository. And you’ll also know how to configure daily test runs that cover all available tests including core and contrib.
via A Guide to Simplified Automated Drupal Testing | Affinity Bridge | Vancouver Drupal Developers.