Coding and Development

This session has been canceled due to unforeseen events. I apologize for the inconvenience and hope to present on this topic soon.

-Justus Luthy

Have you ever added some new functionality to a site only to have it break something elsewhere?  Did the customer find out?

Do you ever start writing code for a module; wondering exactly where to start or what it needs to do, exactly?

Do you want full confidence in adding new functionality to (or refactoring) your modules that nothing else will break?


If you answered yes to any of the above questions, the next answer should also be "yes": Are you attending this session?


In this session, I will be covering the following topics:

  • General overview of Test Driven Development, what it is, and why you should care
  • Test Driven development practices and how you can use them with Drupal
  • Writing tests first, code second
  • Refactoring with FULL confidence
  • Moving your business logic so you don't have to rewrite the farm when the Drupal upgrade comes
  • ...and much more!

This session is targeted primarily to Drupal developers, since we will be getting "into the code" a bit. You should have some familiarity with Drupal module development, but it's not required that you be Earl Miles (although he's certainly invited).

The techniques we will be addressing have been in use at our company (and have been enhanced "as we go") for nearly 2 years. After attending DrupalCon Denver, I realized that many Drupal developers are lacking a documented process for test driving their code. Our hope is that this process is adopted (or even something similar) for the Drupal development community to greatly improve the quality of all our code.

Experience level: 
Time slot: 
19 May 14:30 - 15:30