 There are no testers on DevOps teams.
But then how can we achieve the quality our customers expect?
Instead of a tester of old, there will be someone called perhaps a quality engineer, who is particularly experienced in thinking about and working towards good quality.
This quality engineer will advise, direct and coach the entire team on how their activities may lead to high quality products. They will facilitate achieving the desired level of quality.
The quality engineer may sit with the product owner, helping them understand boundaries of the feature, and how to consider quality or testing issues.
The quality engineer may sit with the architect, ensuring that there are adequate interfaces for testing, and to jointly uncover areas that deserve particular scrutiny in test.
The quality engineer may sit with the infrastructure engineer, figuring out the interactions between software and infrastructure.
The quality engineer may sit with the developer, jointly setting up test automation, and discussing how to best write tests for particular situations.
The quality engineer may sit with the build automation engineer, figuring out the best way to architect and harness CI/CD systems.
What the quality engineer happens to do most rarely, or perhaps never – is testing.