Drupal Quality Assurance

The bot needs to retrieve files for review from drupal.org. Since the drupal.org servers are being upgraded to Drupal 6, among other things, the bot will be disabled until the upgrade is complete.

It has been a while since the last update so I figured it is time for one. I lost my login credentials for testing.drupal.org during my graphics card failure and thus was not able to make an updates until a few days ago.

After a lengthy catch up period the bot is now caught up with the issue queue and has some impressive statistics to show for it.

• The event log contains over 40,000 logged events.
• The test suite has been run over 11,800 times.
• Over 3,500 patches has been processed by the system at least once (most is 26).
• The Drupal core SimpleTest suite of tests now contains over 9,000 assertions. (not bot related)

Work has begun on the next generation of the testing framework that will be easier to manage, self correcting, and offer more features. Along with my blog posts regarding the development I have created more specific issues for PIFR 2.0 and PIFT 2.0.

Development is currently postponed until Project has been ported to 6.x and drupal.org port to 6.x is secured. Once completed work will focus on PIFT 6.x upgrade and then 2.x development.

Any donations to the development of the automated testing system are much appreciated and let us know that you value the increased quality assurance that the framework brings to the Drupal community.

An endless loop in a test is keeping the testing bot off-line. SimpleTest needs to be patched in order to set a timeout, hopefully something like 30 minutes.

Thanks,

boombatower

For the past two days patches have been ignored by testbot due to an issue with the key sent to confirm access to add patches to the queue. In some course of events this key changed and thus the testbot denied patches.

This issue has been fixed and the testbed is now active. All patches that still meet the criteria are resent after 72 hours. Any patches that were denied will be resent via that method.

Thanks,

boombatower

The testbed has been disabled since yesterday and has just been re-enabled.

The Node revisions test fails if admin has a personal timezone offset patch was committed to Drupal 7 core in order to correct the problem created by Move node links into $node->content.

The duplicate testing issue that occurs rarely was remedied by increasing the memory limit on the testing servers and applying a preventative patch, just to be extra sure.

Thank you for your patience,

boombatower

There were reports of false failures (http://drupal.org/node/345866, http://drupal.org/node/346285) of the testing bot.

Details of the failing test are remove $op from hook_block().

The testbed will be offline for a couple of days until we can bring it back online. If you want to help with the testbed we need help with the following:

1) System administrators who can help administer almost a dozen servers that have been loaned for testing.
2) Documentation help to document how the testbed infrastructure works.
3) Donate a server or Virtual Machine so we have more testing slaves available.

Contact me if you are able to help.

Cheers,
Kieran

The previous issues have been fixed and the bot is now active!

The fleet of testing servers has been updated which should fix a couple of bugs. Please report any issues to the project issues file review issue queue.

If anyone is interested in developing, or knows of an existing one, a "bot like" theme for testing.drupal.org please make a comment.

The bot needs a bit of pizazz. (Drupal 6.x)

The testing bot has been disabled due to two issues with Drupal 7 HEAD:

• Failures in node.test with assertFieldByXPath
• SimpleTest: correct assertTitle logic

The issue should be fixed shortly. The testing fleet will then be upgraded to the latest version of the testing software and then be re-enabled.

Thank you for your patience,

boombatower