Marco Achtziger shared his experiences with deploying continuous testing in large scale agile project at Siemens Healthcare at the OOP conference. InfoQ interviewed Achtziger about continuous testing and continuous integration, infrastructural and social challenges with continuous testing, testing processes and tools, and improving continuous testing.
In a blog post on bad code and technical debt Steve Freeman described how Chris Matts came up with the metaphor of an unhedged call option for bad code. This post is being intensively discussed on Reddit and on Hacker News recently. InfoQ interviewed Steve and Chris about using metaphors for bad code and code smells, trade-offs and costs of low quality code, and responsibilities for code quality.
Netflix's Failure Injection Testing bridges the gap between isolated testing and unmitigated chaos testing by controlling the impact of the test. FIT establishes a context which other components of Netflix's production testing and infrastructure systems interpret and adjust the behavior of the system accordingly.
Testdroid's maker Bitbar has recently announced the integration of Testdroid mobile app testing products with Atlassian JIRA defect tracking system. InfoQ has interviewed Testdroid technical product manager Ville-Veikko Helppi to better understand how developers and organizations could benefit from it.
There has been significant buzz around microservices lately, enough to generate some hype. After implementing heavy and cumbersome SOA solutions for more than a decade, are microservices the solution the industry has been waiting for? Or, are microservices simpler than monolithic solutions?
PlanOut is Facebook's language for online field experiments supporting "A/B tests," factorial designs, and more. According to Facebook, PlanOut makes possible to separate experimental design from application code and allows experimenters to concisely describe their designs. Facebook claims to be using PlanOut to run over a thousand experiments each day that involve hundreds of millions of people.
The recent security weakness found in both iOS and OS X hints at flaws in coding style guidelines, unit testing, system testing, code review policies, error management strategies, and tools deployment. An overview.
Two recently launched services, Appurify Mobile Platform and Xamarin Test Cloud, promise to help developers and enterprises automate testing and performance optimization of their mobile apps by allowing them to run apps on real iOS and Android devices and supporting automated testing and continuous integration.
Google has open sourced Espresso, an Android automated testing framework that enables one to run tests on x86 machines in the cloud in a multi-threaded environment, solving the concurrency issues associated with UI testing.
Thoughtworks recently released a new installment of their technology radar highlighting techniques enabling infrastructure as code, perimeterless enterprises, applying proven practices to areas without, and lightweight analytics.
Brett Slatkin from Google presented a method for visual regression testing at Velocity 2013 in Santa Clara. Perceptual diff compares screenshots of a release's webpages with its previous versions and detects changes at pixel level, filling an important gap in automated testing for Continuous Deployment. An open source version of the software has been setup on github.
Sauce Labs has extended Appium to support automated testing for Android and Firefox OS applications. Support for iOS was introduced earlier this year.
Earlier this month, SOASTA and CloudBees released a plugin for the Jenkins continuous integration (or CI) server to run automated tests on real physical mobile devices. SOASTA released this plugin with optimizations that were developed by the creator of Jenkins, Kohsuke Kawaguchi. The plugin provides build steps for performing operations and testing mobile devices.
Companies use "Canary Deployments" to test software in production by routing a subset of users to new functionality as part of continuous delivery according to Nolio in their 1st video in a series about DevOps Best Practices. A "Canary Deployment" is a type of incremental release performed by deploying a new version of software side by side with its production version counterpart.