Most of us have heard of DevOps, but are you familiar with TestOps?
“TestOps as a concept revolves around ensuring product teams have access to any required test infrastructure, platforms and frameworks they require without needing large amounts of time consuming configuration before commencing tests. Any benefit from use of a CI system will be lost if the QA process takes days to complete due to environmental setup and tear down on the part of the QA person on a team.” – Simon Howlett
A tiny but growing number, though, are exploring “TestOps”, which, at its most aggressive, claims that “[t]esters are uniquely qualified to lead the way to a more nimble enterprise.” TestOps remains so small that there is no Wikipedia entry for it as I write this, although I expect that status to change any day; it’s a common term of art within Microsoft and a few other large industry players.
Part of the impetus behind TestOps is the perception that it applies particularly well to provision of software services, as opposed to products. This naturally ties in to the growing importance of cloud computing. Most dramatically, as one commentator expresses the contrast, “On premise you can always scale up, improve the storage i/o, decrease latency by changing the network, or any other infrastructure tweaks available. On the public cloud the only tool that you have is the ability to test continuously in a production environment.” In this view, organizations that choose the advantages of the cloud must also build in performance management practices from the first day.
I highly recommend reading more at the following reference links:
And recommend watching the following video: