"value":"\n <p>In my <a href=\"\/presentations\/tdd-test-driven-drupal\">talk about automated testing and test-driven development<\/a>, I speak about a custom module I wrote for a client's Drupal project.<\/p>\n\n<p>It was to integrate with a third-party job application system that they would log into and enter information via a form (similar to Drupal's node forms) that they wanted to appear on the Drupal website.<\/p>\n\n<p>Once submitted, the system would send a POST request to an endpoint provided by the custom module. The module would process it and create the job node with the appropriate field values.<\/p>\n\n<p>I wrote automated tests and did test-driven development.<\/p>\n\n<p>Everything worked great for a few weeks or months.<\/p>\n\n<p>Later, we had a message from the client saying the integration was broken and we needed to fix it.<\/p>\n\n<p>I don't think I'd worked on this module for a while, but I was concerned that a Drupal core update or another change could have caused a regression.<\/p>\n\n<p>The first thing I did was run the tests I'd written and verify they still passed, which they did.<\/p>\n\n<p>This confirmed that as long as the data was being sent in the expected format, the node would be created and the integration would work.<\/p>\n\n<p>Due to an upstream issue, the data was no longer in the expected format, which meant the node could not be created.<\/p>\n\n<p>Once it was fixed, everything started working again.<\/p>\n\n<p>My debugging time was practically zero as I was able to rely on my tests and that they were still passing.<\/p>\n\n<p>I could confidently tell the client that the issue wasn't with our code and must've been an third-party issue.<\/p>\n\n<p>Writing tests takes some time, but having tests saves time.<\/p>\n\n ",
"processed":"\n <p>In my <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">talk about automated testing and test-driven development<\/a>, I speak about a custom module I wrote for a client's Drupal project.<\/p>\n\n<p>It was to integrate with a third-party job application system that they would log into and enter information via a form (similar to Drupal's node forms) that they wanted to appear on the Drupal website.<\/p>\n\n<p>Once submitted, the system would send a POST request to an endpoint provided by the custom module. The module would process it and create the job node with the appropriate field values.<\/p>\n\n<p>I wrote automated tests and did test-driven development.<\/p>\n\n<p>Everything worked great for a few weeks or months.<\/p>\n\n<p>Later, we had a message from the client saying the integration was broken and we needed to fix it.<\/p>\n\n<p>I don't think I'd worked on this module for a while, but I was concerned that a Drupal core update or another change could have caused a regression.<\/p>\n\n<p>The first thing I did was run the tests I'd written and verify they still passed, which they did.<\/p>\n\n<p>This confirmed that as long as the data was being sent in the expected format, the node would be created and the integration would work.<\/p>\n\n<p>Due to an upstream issue, the data was no longer in the expected format, which meant the node could not be created.<\/p>\n\n<p>Once it was fixed, everything started working again.<\/p>\n\n<p>My debugging time was practically zero as I was able to rely on my tests and that they were still passing.<\/p>\n\n<p>I could confidently tell the client that the issue wasn't with our code and must've been an third-party issue.<\/p>\n\n<p>Writing tests takes some time, but having tests saves time.<\/p>\n\n ",