SOC 2006: Unit test automation

Hold on, hear me out :o) We're a really focused and strong (and almost too commercial) community, and we really have put our focus on features and output, and we've lacked a lot when it's come to making it all work correctly in every possible case.

That's where quality testing comes in. I've been thinking about Drupal's quality assurance process for a couple years now, but in the last few months it's really come to a head for me. My personal "dam-breaking" moment came when the Batch API in Drupal 6 prevented install, and other tasks depending on the API from running automatically, or in text based browsers, or in browsers were people have been privacy conscious and disabled JS and Meta refresh tags.

Without proper quality trails this will continue to happen. And here's another point I'd like to make:

Continue reading and comment at DrupalFiles >

Hold on, hear me out :o) We're a really focused and strong (and almost too commercial) community, and we really have put our focus on features and output, and we've lacked a lot when it's come to making it all work correctly in every possible case.

That's where quality testing comes in. I've been thinking about Drupal's quality assurance process for a couple years now, but in the last few months it's really come to a head for me. My personal "dam-breaking" moment came when the Batch API in Drupal 6 prevented install, and other tasks depending on the API from running automatically, or in text based browsers, or in browsers were people have been privacy conscious and disabled JS and Meta refresh tags.

Without proper quality trails this will continue to happen. And here's another point I'd like to make:

Continue reading and comment at DrupalFiles >

Hello, the Drupal software project is going to start using unit test automation for Drupal core. We are looking for volunteers, and people looking for full time work who are interested in this project.

• Volunteer to lead the unit tests for Drupal 7
• Volunteer to document installation of automated unit test set up for consultants and customers

Contact us via the contact form at: http://testing.drupal.org

Kieran

Hello, the Drupal software project is going to start using unit test automation for Drupal core. We are looking for volunteers, and people looking for full time work who are interested in this project.

• Volunteer to lead the unit tests for Drupal 7
• Volunteer to document installation of automated unit test set up for consultants and customers

Contact us via the contact form at: http://testing.drupal.org

Kieran

Hello all,
Sorry for cross-posting; but I think people working on different aspects of Drupal may have interest in this idea.

I've submitted a SoC 2007 Drupal proposal on automating the whole process of creating a complete Drupal site with a LAMP stack in a self-contained virtual machine image. A formatted PDF version is here:
http://www.abeharry.info/SoC2007_DrupalAST_FullProposal.pdf
Here is the abstract:

The Drupal automated staging toolkit is a proposed set of code libraries, file schemas and parsers, and code generators, for

Hello all,
Sorry for cross-posting; but I think people working on different aspects of Drupal may have interest in this idea.

I've submitted a SoC 2007 Drupal proposal on automating the whole process of creating a complete Drupal site with a LAMP stack in a self-contained virtual machine image. A formatted PDF version is here:
http://www.abeharry.info/SoC2007_DrupalAST_FullProposal.pdf
Here is the abstract:

The Drupal automated staging toolkit is a proposed set of code libraries, file schemas and parsers, and code generators, for

With Rok's guidance, I tested out the automated patch testing system that he's created. I uploaded a number of patches to his site, which then applied them to either Drupal 4.7 or Drupal CVS, and then ran 16 unit tests against them. We tried patches that applied and contained no errors, patches that didn't apply, and patches that had coding errors. Each time the test suite performed beautifully.

The value of this work is that patches that linger in the patch queue often fall out of sync with a moving HEAD. At the point when that happens, Rok's tests would be able to detect that and notify the patch maintainer. Furthermore, Dries, Neil, Gerhard and Steven would never have to write "patch doesn't apply" (after just having wasted their precious time trying to apply it). Furthermore, people often submit patches without thinking through all of the ramifications that a patch can have. If we were to build up a thorough set of unit tests (I can't imagine 16 tests really cover Drupal), then a lot of these errors would be detected automatically.

With Rok's guidance, I tested out the automated patch testing system that he's created. I uploaded a number of patches to his site, which then applied them to either Drupal 4.7 or Drupal CVS, and then ran 16 unit tests against them. We tried patches that applied and contained no errors, patches that didn't apply, and patches that had coding errors. Each time the test suite performed beautifully.

The value of this work is that patches that linger in the patch queue often fall out of sync with a moving HEAD. At the point when that happens, Rok's tests would be able to detect that and notify the patch maintainer. Furthermore, Dries, Neil, Gerhard and Steven would never have to write "patch doesn't apply" (after just having wasted their precious time trying to apply it). Furthermore, people often submit patches without thinking through all of the ramifications that a patch can have. If we were to build up a thorough set of unit tests (I can't imagine 16 tests really cover Drupal), then a lot of these errors would be detected automatically.

Here you will find all the information you need to setup an environment where you will be able to automatically test patches.

Here you will find all the information you need to setup an environment where you will be able to automatically test patches.

One of the biggest concerns about automatic testing is how to prevent potentially dangerous code to cause harm to the server and other tests.

One of the biggest concerns about automatic testing is how to prevent potentially dangerous code to cause harm to the server and other tests.

Here are short instrucions on how to use this module.

Here are short instrucions on how to use this module.

After some discussions with my mentor Thomas and other people on devel mailling list I have created sort of a first prototype.

How it works

One part of this module is used to catch the patches and submites them to other part of the module via xml-rpc call. The second part receives this call and tests the patch. Results are stored in a new node on test server node address is returend by xml-rpc call response.

After some discussions with my mentor Thomas and other people on devel mailling list I have created sort of a first prototype.

How it works

One part of this module is used to catch the patches and submites them to other part of the module via xml-rpc call. The second part receives this call and tests the patch. Results are stored in a new node on test server node address is returend by xml-rpc call response.