DrupalCI is the next generation testing infrastructure for Drupal. After years of development, DrupalCI has been rolled out for testing Drupal 8 Core and Contrib projects - and will soon be taking over testing Drupal 7 Core and Contrib as well and for Drupal 6 for the duration of its long term support window.

But we need your help!

At this time, DrupalCI is running in parallel with the existing PIFT/PIFR testing architecture. Before we retire the old testing infrastructure we want to ensure that there are no feature regressions in the new DrupalCI system, and that core and contrib developers have had time to learn the new testing architecture and try it out thoroughly.

If you are a maintainer of a contrib module with testing enabled, we will enable DrupalCI testing for your project. At this time, DrupalCI supports testing in D8 Core and Contrib, but D7 and D6 testing will be enabled soon. If you see that DrupalCI testing has been enabled for your project, please provide your feedback in the issue linked below.

To learn more about how to use DrupalCI for automated testing of your project on Drupal.org, please consult this documentation page.

How can you provide feedback?

We are collecting feedback on the new testing architecture in this issue: #2534132 - Disable Legacy Testbots and use drupalCI as our testing infrastructure. Please focus your feedback on:

  • Feature regressions from current testbots
  • Unexpected test failures
  • User interface issues
  • Test result parsing and display

Though DrupalCI is a more flexible and extensible testing architecture, we are not collecting additional feature requests at this time.

If you are a module maintainer, and you are a satisfied that the new DrupalCI tests are meeting your testing needs, you can return to the Automated Testing tab for your project and choose to disable PIFT/PIFR testing, by deleting the specific releases you no longer need tested in the old system:

Delete unneeded release from old testbots

Learn how to add automated testing to your project…

If you would like to add automated testing to your projects on Drupal.org you can learn more about writing tests with this tutorial.

Comments

sheldonkreger’s picture

Once somebody grants me permission to submit new modules, I will be happy to test the new infrastructure. https://www.drupal.org/node/2560149#comment-10375319

davidstorm’s picture

Automated testing is a great time saver

http://www.hadash-hot.co.il