How to Build and Maintain Quality Drupal Sites with Automated Testing

Building better websites with automated quality assurance Cheaper, Faster, more Reliable

Agenda
Introductions
Drupal SimpleTest
Drupal.org usage
Drupal.org Future
Business Value of Quality
Assurance
Examiner Development
Examiner Development - Selenium
Examiner Benefits
Testing in the Wild
Contributed Module
Development
Tools for Site Owners
ReviewDriven.com
Contributed Back
Demo

Introductions
Jimmy Berry is the lead developer for the automated quality assurance platform used in the Drupal core development process. Jimmy works for Examiner.com where he develops automated quality assurance tools for examiner.com's migration to Drupal 7.

Kieran Lal is the project manager for the quality assurance platform. Kieran is the Drupal community adventure guide for Acquia where he helps organizations understand the benefits of Drupal and Acquia's products to be successful with their Drupal sites.

Drupal SimpleTest
Based on SimpleTest.org API
Provides seemless integration with Drupal
Extensive Drupal core suite
Provides many examples
~19,000 assertions
Introduction - http://drupal.org/simpletest
Primarily used for "functional" testing
Simulate user
Start from scratch environment

Drupal.org Usage * http://qa.drupal.org/pifr/statistics Number of tests reviewed 24,840 Number of reviews performed 132,773 Average number of times a test is reviewed 5

Business Value of Quality Assurance
Confidence to make large changes and refactor as needed.
Can prevent bugs from reoccurring.
Provides the confidence to know the system is ready to deploy.
Removes the need to for large scale human testing with every change set.

Drupal.org Future
Drupal 8
Clean code to perfection early in cycle
Combination of manual cleanup and automated tools like the (PHP) Grammar Parser.
Remove any false positives from Coder
Enable Coder review on all patches
Code coverage reports on commit
Additional automated reviews
Textual analysis
Security reviews

Examiner Development
On commit
Coder reviews - e-mail results to developers
Daily
Pre-configured tests against shared dev database
Import clone of dev database.
Additional copies made during testing
Atomic tests that require no database
Run against an external server such as production or staging
Ensure that rolled out code is functioning properly
Could be used for Drupal.org

Examiner Development - Selenium
Selenium IDE
Workflow
Record test "marcos"
Export as PHP Selenium output
Convert using simpletest_selenium (d.o project)
Benefits
Distribute test writing workload by allowing non-tech savy users to record tests
Lower initial learning curve requird to include testing into a development process

Examiner Benefits
Code review
Makes it code reviews second nature
Encourages developers to clean up code
Testing
Lighten manual test load
Still fairly early in development cycle to access benefit

Testing in the Wild
Project Issue File Request (PIFR)
ClassicGraphics
Drupal.org
Examiner
Non-PIFR
Consumersearch.com
Economist - Hudson
myLifetime - Script

Contributed Module Development
SimpleTest documentation
365 contributed modules that already have
46 contributed modules on http://qa.drupal.org
Assistance in writing tests
Infrastructure issues
Finish info file parsing update*
Allow any project maintainer to enable testing
Provides mechanism to specify dependency versions
Interface improvements to enhancing integration
Links to related review results
Aggregation of summary results on project pages
Coverage ratings for projects
Project specific filters and settings
http://drupal.org/project/project_issue_file_review
http://drupal.org/project/project_issue_file_test
* http://drupal.org/node/102102

Tools for Site Owners
SimpleTest
Works with Drupal 6 & 7
Clone of a database
Drupal 6 module - simpletest_clone
Drupal 7 patch - node #666956
Atomic tests – node #758662
PIFR 2
Automate running of tests and reviews
Used with trigger script or project management integration
Works with any combinations of version control systems
Currently supported: bzr, cvs, git, svn

ReviewDriven.com
QA as a service
Add site repository
Schedule reviews
Define triggers
Configure notifications
Make QA as easy as possible to improve the Drupal ecosystem as a whole
Focus on enhancing tools available to Drupal developers
Public beta coming soon

Contributing Back
Write tests for core
Write tests for contrib and custom modules
Run tests for your modules
Run tests for your site
Run tests for your development process
Write the testing framework
Drupal.org Project module integration (PIFT)
qa.drupal.org (PIFR)
SimpleTest testing framework
Drupal core
6.x-2.x backport

Demo
class DrupalRedesignTestCase extends DrupalStageTestCase {
[...] protected function setUp () { $this -> stagingUrl = 'http://staging6.drupal.org' ; $this -> httpauth_credentials = 'drupal:drupal' ; parent :: setUp (); } protected function testFoo () { $this -> drupalGet ( 'about' ); $this -> assertText ( 'Documentation' ); } }
* http://drupal.org/node/758662

QA Sprint Drupalcon SF
Sunday 9AM, April 18th
Coder Lounge
Learn how to write tests for Drupal core
Learn how to contribute tests to modules you use
Learn how to write tests for your contrib modules
Learn how to run simpletest for your custom site

Contributing to the QA project
Add features to the QA platform for core
E.g. Load testing
Add features that your consulting company needs for clients
Add features that your company needs for it’s QA process
Add features to integrate with your development and test workflow
Contact: http://qa.drupal.org/contact

Appendix

How to Reach Our Audience
Developers - front page
Coder reviews
Involve most popular module developers
Assemble knowledgeable QA team
[Dave Reid]
[List of people who have corresponeded]
[List of projects with SimpleTests]
Site owners
Maintainable benefit that will increase in value
Additional plugins and services

Schedule for Webinar and Sprint
Announce Webinar and Sprint on March 22nd
Practice run on the March 25th
Webinar on March 31st
Sprint on April 18th

Business Value of Quality Assurance
Confidence to make large changes and refactor as needed.
Frees developers to focus on features and functionality instead of ensuring that functionality is not broken.
Helps prevent changes from having a cascade effect.
Can prevent bugs from reoccurring.
Provides the confidence to know the system is ready to deploy.
Removes the need to for large scale human testing with every change set.
Provides a consistent mechanism to ensure the system is in a certain level of stability.
Ensures that testing is not neglected, but instead occurs on a regular basis.
Provides a way to ensure that configuration changes specific to one site do not have unwanted effects.

http://acquia.com	302
http://www.acquia.com	154
https://www.acquia.com	16
http://www.slideshare.net	12
https://acquia.com	11
http://webcache.googleusercontent.com	1

How to Build and Maintain Quality Drupal Sites with Automated Testing

by Acquia

Accessibility

Categories

Upload Details

Usage Rights

6 Embeds 496

Statistics