So, I finally got a break from the long workdays to do a little tinkering with my new Intel NUCs, which I bought to configure a more robust CI environment on my network here at home. All three Intel NUCs are running Debian Jessie, and all are running with static IP addresses assigned on my Intranet here at the house.
This post is part of my "Continuous Integration on a Budget" series, and covers the "whats" of Behat and other tools available to implement Behavior Driven Development as part of your Continuous Integration process.
This post is part of my "Continuous Integration on a Budget" series, and covers setting up a Jenkins Template for Drupal Testing on a Jenkins CI server which, in this series, is set up on a Linode instance running Debian 7
Test Driven Development, Continuous Integration, Automated Testing, Automated Deployment ... sounds wonderful, doesn't it? Perhaps a bit daunting?
"But I'm a small Drupal developer running my own development shop. I don't really have the time or the tools for that."
I thought that too. However, after spending countless hours chasing down obscure bugs in code I (or, in many cases, someone else) wrote weeks (or months) ago that is now behaving badly because recent modifications in the codebase changed its behavior, I began to think, "There has to be a better way".