Elisabeth Hendrickson is the Director of Quality Engineering for Cloud Foundry at Pivotal Labs. She is the award winning author of "Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing" and tweets as @testobsessed. 20min video interview & transcript. interview 
_For six months, the small dev team I led tried to build a replacement suite of integration tests. This is one reference I collected in 2014 to inform our effort._
# The whole team owns quality. Starts with stories, requires BDD and CI and automated regression and full integration tests and all the way to DevOps. Quality starts with the stories -- being super explicit about the expected effect of each story Quality also means fitness for use: did we achieve the business objective? We need acceptance criteria on our stories that reflect what we expect to be true in the product, and a notion of what we expect to be true with our users or our market after we've implemented this thing Extreme Programming practices for fast feedback cycles to verify we built what was intended and that we didn't break anything else in the process * lowest level are unit tests verifying code behaves as intended * continuous integration to verify the system behaves as intended through fully automated regression tests, full integration tests, and... * "DevOps is basically second decade Agile" ultimately being able to do multiple deployments to a production-like environment daily Tool Suggestions * Go CD: http://www.go.cd/ (ThoughtWorks opensourced continuous delivery system -- better at build pipelines than Jenkins) * Bosh: http://docs.cloudfoundry.org/bosh/ (Cloud Foundry tool. similar niche to chef except better at full VM lifecycle management. Similar to juju except not specific to ubuntu)