Sept 2nd, Drupal 7 relase party. How continuous integration testing made this plausible

On September 2nd, 2009 12:01AM at the end of the Drupal 7 development cycle 100% of 12,000 functional test will pass. Over 80% of Drupal 7 will have test coverage. Drupal 7 could conceivably be of high enough quality to ship. We will break out the champagne and celebrate the end of a development cycle with high enough quality to ship.

How did the Drupal community achieve such a great feat? More importantly can you use these same techniques for your Drupal projects so that you can spend more of your time developing new features, and improving your clients websites, instead of fixing bugs and stuck in endless quality assurance release cycles.

In this session we will explain how you can use the back-port of the Drupal 7 simpletest suite, combined with the Automated Testing System used for the development of Drupal 7 to test your Drupal sites. With continuous testing for your Drupal sites you'll spend more time in development, less time in lengthy quality assurance cycles, and you'll be enjoying the wonders of Drupal 7 faster, because you can confidently upgrade from Drupal 6 to Drupal7.

We will cover Drupal 7 and Drupal 6 simpletests briefly. We will talk about how the testing.drupal.org system tests patches, and how your Drupal site modules will need to test thousands of patches from the community before you can push them live.

We will review how you can contribute to core, and contrib module testing and ensure that the modules you rely on are tested. Finally, we will talk about what it is going to take to get 100% test coverage in Drupal core, and how the hundreds of remaining critical issues for Drupal 7 need tests to ensure that Drupal 7 stays stable and releases quickly. In full disclosure, getting the hundreds of critical issues fixed may take a few months past Sept 2nd.