The second edition of Stephen Nelson-Smith's book "Test-Driven Infrastructure with Chef" covers the principles behind "Infrastructure as Code", provides an introduction to Ruby, Chef, and important Tools. The main part consists of detailed examples on how to use the tools required to write fully tested infrastructure code.
“ATDD By Example” value proposition was to be an introductory hands-on guide to implementing and successfully applying Acceptance Test Driven Development (ATDD) from zero. Despite doing a reasonable job of summarizing and/or pointing to several test-related practices required for any successful agile tester, the book ends up trying and failing to be all things to all readers.
In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development. 9
In the last couple of months several online discussions took place about test first or test last, code-to-test ratios or whether BDD is really just TDD. InfoQ asked the opinion of BDD and TDD experts. 3
Developers using TDD need the customer to provide a set of examples linked to the Business Value they provide. This article introduces Feature Injection which is a process to provide just this. 2
InfoQ have talked to Dan North, Gojko Adzic, Elizabeth Keogh and Matt Wynne about Specification by Example, Executable Specifications and Feature Injection and how they relate to BDD. 1
This is the third and final part of the late Jamie Phillip’s exploration into the world of coding kata’s and Behavior Driven Design. 1
In part 2 Jamie Phillips introduces behavior driven development and explains how it can improve the effectiveness of unit testing. 1
Regardless of experience there are always opportunities to strengthen one’s skills. Jamie Phillips demonstrates how he used coding katas to improve upon his skills after 8 years of writing C# code. 2
Jian Fang describes the The Tellurium Automated Testing Framework he created which uses a novel approach to try and improved the robustness of automated testing scripts for web applications. 11
Outside of a certain Agile sweet-spot, there are more barriers and costs to applying Agile techniques. None of these obstacles prevents Agile in itself but each increases the cost of getting to Agile. 4