The decision to rewrite our PhantomJS content testing pipeline yielded a dramatic 90% reduction in our content testing duration–slashing our lengthy 11+ hour testing time down to just 30 minutes! This latest pipeline development has now left us with a total build process time of just 2 hours.
The decision to rewrite our PhantomJS content testing pipeline yielded a dramatic 90% reduction in our content testing duration–slashing our lengthy 11+ hour testing time down to just 30 minutes! This latest pipeline development has now left us with a total build process time of just 2 hours.
In this post, I'll look at how DesignHammer improved our Jenkins build process by adding a testing workflow and setting up a parallel Build Flow job.
In this post, we'll look at how we can implement a testing framework for ongoing imports of data into Drupal using some of our favorite tools: CasperJS, Migrate module, and Jenkins.
This post examines how to use CasperJS, Drush, and Jenkins to implement an automated, behavior driven development testing cycle for your Drupal site.
If you are developing a content-based iPhone or iPad app that connects to the internet you have to be prepared for real-world networking. The fast hard-wired connection you have on your development machine and the strong wi-fi signal you get on your device are great for testing things quickly, but they don't prepare your app for what it will face in the hands of iPhone users all over the world. Your app will have to handle network dropouts, packet loss and high ping times without crashing and while maintaining a good user experience.