I agree. I like take an onioned approach to software quality: * unit tests * release consistency (build artifacts and dependencies tracked as an atomi

I agree. I like take an onioned approach to software quality: * unit tests * release consistency (build artifacts and dependencies tracked as an atomic, reproducible unit) * some type of deployment/startup sanity tests * development environment integration tests * staging environment integration tests * statistical anomaly detection on one production box * application and infrastructure metric monitoring This is not a prescriptive list; just something I've found works well for continually deployed systems.