The setup

Recently, I did some pro-bono consulting work for a client. As part of our agreement I made it clear that I would retain the rights to the code I wrote. The reason I did this is because I wanted to be able to give back to the community, and now I am going to do that. The work was made up of six tasks, ranging from trivial to complex. I intend to write six articles based on these tasks. This is the first.

The lists below may seem sparse. This is deliberate. I could give you a laundry lists of every programming language, software package, operating system, and technology buzzword that I have ever worked with. I won't subject you to that. I will just tell you my greatest strength:

I find solutions.

What is Unit Testing?

In simple terms, unit testing is a definition of tests to run on your code. Usually, these tests are automated. The "unit" in unit testing means that the tests should test the smallest functional units, like functions or methods. However, unit testing does not have to be limited to only testing small parts; it can also test interactions between parts with complex combinations and variables, and even test some visual elements, like whether or not a certain image is actually shown or if a class was applied to an XHTML tag.

Below you will find my description of how I made a new component for Drupal's webform module that dynamically displays a selection of checkboxes. I will go over why I made it. Then I will explain the code step by step. I have also attached a copy of the file for download.

Recently, I had trouble with the Mambo contact component. Sometimes, the emails would get through, and other times they would not. There did not appear to be any discernable pattern. In the end, I discovered that an innocent looking word in the subject of the email was causing the message to be blocked by some spam filters.