What is devtestops?

Is devtestops a synonymous of continous testing? Or is it something else? Do you have books/articles/videos that explain what is is?
I’m just curious.
Thank you.


It’s simply a combination of DevOps and Continuous testing .
Some reading material: What is DevTestOps | Role of DevTestOps in Continuous Testing

Including Myths!


Without the context of sufficient experience in devops, devtestops makes less sense as a label, not more, in my mind. And that is because the devops scene is seldom including the production and maintenance of the SAAS environments we are typically talking about when we use the term devops. For me, in a SAAS business, Ops is about the firewalls, CDN servers, load balancers, redundancy , updates, deployments and recovery. Not to forget customer lifecycle. Few people who did put devops in their CV spent that much time doing the latter part of the term, unless the company only has 2 employees.

QA do add a oversight to the entire SDLC. I think a lot of people don’t get that in a component architecture and also microservices architectures the pretty diagrams really look like this:


Quoting @kristof link’s:
‘The process involves testing early, testing often, and testing throughout the software delivery pipeline.’ and ’ DevTestOps idea was brought forward in which Continuous Testing was implemented as a major part of the software delivery pipeline.’
So, from my point of view: it’s just a buzz word/label (like @conrad.braam wrote) meaning implements continuous testing :smiley:
Thank you!


Using a single word often helps a lot when we share and all grasp the same meaning. So nothing wrong with trying to gain consensus, I mean that’s a key skill for testers and probably all engineers. I do think it is very important to have people talk about where their responsibility boundaries lie, but also what those responsibilities are. Especially when it comes to making sure we choose people who are most comfortable with a specific part of that development cycle, to go work, in that area of the whole process. It’s a good conversation to have, because the OPS people closer to the customer frontline don’t want to be creating new tests, because their core skills are not going to be in coding, but rather in monitoring and maintaining infrastructure.