Last updated November 19, 2015. uses an automated testing system to test both new commits and patches to the Drupal project and to other projects that choose to use it.

This section describes the details of that system and how to maintain it.

Maintainers and contributors to projects see FAQ: Frequently Asked Questions about Automated Testing and Drupal CI aka testbots.

Note: Automated Testing is transitioning from the PIFR/PIFT testbot to DrupalCI. Some projects are running both the legacy and the new testing. Passes and fails are counted differently on the two systems, the old testbot counts each assertion as a pass, the new testbot counts one test as one pass (not each assertion). See issue: Expose Assertion Count to Jenkins for progress on the difference in counting passes and fails.