Disclaimer: this is not an attempt to replace any existing DevOps community, nor to silo off testers or testing from Dev and Ops!
Rather, it will be a place to share ideas, techniques, resources about all the testing activities needed to feel confident about delivering value to our customers frequently and sustainably. DevOps is a whole-team effort. Testing is at its heart. Testing specialists add much value.
DevOps evolved from agile development’s whole team approach to building quality in. Testers and QA professionals are part of cross-functional software delivery teams that practice DevOps. Every conversation -- from building shared understanding as new features are planned, to managing the delivery pipeline, to monitoring and observing production usage, to shortening the mean time to recover from production issues -- includes discussions about testing. The goal of DevTestOps is not to silo "Test" from Dev and Ops, but simply to raise the visibility of testers and testing as integral parts of the DevOps quality culture.
Paying homage to the Agile manifesto, we’ve developed a set of guiding principles for testing software comprehensively, and at scale. We started to call these principles the DevTestOps Manifesto. After talking to more practitioners, we realize, there's not one way to "do" testing in DevOps. So we're keeping these as principles:
The term DevTestOps is intended to better reflect the central role that testing plays in the modern software development lifecycle.
Teams that support DevTestOps understand that testing is intrinsic and essential to all aspects of the DevOps culture. DevTestOps holds the promise of making testing a continuous activity, performed by all throughout the software development process, and of fostering the unity that teams need in order to make software that matters.