UPDATE: Slides can be viewed at https://docs.google.com/presentation/d/1FLqwAPzUe52HHxuQgo9WwRrdEvpi7hUi...

On October 18th, 2007, Chad Phillips (hummonk) made an initial commit to the ‘Project Issue File Test’ module, with the description “initial commit of an integrated file testing platform for project issue module”. This kicked off the pursuit of automated testing integration between drupal.org and qa.d.o (then referred to as testing.drupal.org). In 2009, Jimmy Berry (boombatower) performed a significant overhaul and redesign of the system with the release of PIFT/PIFR 2.0, introducing a number of structural and architectural changes and improvements.

By the time Drupal 8 is launched, we’ll have been running for 5 years on the current architecture, and almost 7 years on the project. In that time it has served us well; but unfortunately the code has not kept up with technology and the changing needs of the Drupal community. The D8 launch brings with it a host of new requirements, such as an urgent need to test against PHP 5.4, 5.5, and 5.6; while simultaneously supporting PHP 5.3 for legacy D6/D7 contrib projects.

'Modernizing Testbot' is an unofficial community initiative with the ambitious goal of rebuilding Drupal.org's automated testing infrastructure, in alignment with modern technologies and best practices.

This session will explore the history and evolution of the 'Modernizing Testbot' initiative, providing attendees with an introduction to the DrupalCI platform, it's architecture, operation, and features, and a status report on progress to date. Dependent on the initiative's progress this summer, the session may also dive into how the platform may be leveraged by companies and freelancers for use outside of the primary "Drupal.org" use case.