Specification by Example How Successful Teams Deliver the Right Software

Enjoyed this overview of a testing methodology that brings in BDD principles to automated software testing environments. It's a bit too complex for my needs, yet I love the idea of capturing everyone's opinion in specification (business owners, testers, developers, analysts) — as well as the philosophy of living documentation. Two favorite bits: 1. Functional requirements, specs, and acceptance tests are the same thing. 2. Don't just disable failing tests — either fix the problem or move to a set of low-priority regression tests that don't run as often or alert in the same way. Hat tip: Alister Scott.