Testing framework

Last modified: September 6, 2008 - 17:30

Motivation

Testing framework can be a very useful tool for Drupal developers. A powerful framework would greatly simplify otherwise a very tedious procedure and help developers focus on more important matters.

Objectives

The goal is to build a framework that would be capable of catching drupal patches from different sources test them and store test results somewhere were they could easily be accessed. System should be able to get patches from user submitted form or directly from Project module.

Another way of running the tests should be with prescheduled automatic runs. This would test the patches already commited daily or on some other preset time.

Workflow that should be automated:
- get the patch from form or Project module in case of scheduled test there is no patch
- install Drupal
- install any additonal modules
- apply patch
- run the test script
- save the results

It is important that the procedure of submitting a patch to test system is as simple as possible

Approach

Some of the functionality already exists in Simpletestauto module. Most importanly the system needs some thoughts how patches arrive into the system and how the results are logged. This should be done right so we can later expand it.

Comments on this proposal

Frando - March 15, 2007 - 07:10

Merlin has laid out some great ideas on the topic, and there was some good discussion about it.
So this is a must-read: http://drupal.org/node/52709

 
 

Drupal is a registered trademark of Dries Buytaert.