Easy. It must be the QA team, the responsibility of the QA manager surely?
Mind you, the QA team are not usually responsible for bug creation, so the developers must play a role. And the Shift Left argument proposes that if we did enough testing early on, we would not need a QA team, so maybe we should just make developers responsible for quality.
But in the end, the users have to use it, to know how to use it, to have a good user experience (UX) and to be able to do their jobs well. So maybe they are the most important group, they certainly will be in a cloud testing scenario. In this case, they will need testing tools designed to support UAT. That might include automation, or a process of getting to automation by making manual testing and documentation easier in the first instance. This is much more Shift Right than Shift Left.
We created TestDrive-UAT with this need in mind and because this area often consumes more resource than any other whilst having until now, any technology aimed at helping solve the problem, a growing problem. If you take a bigger view of the problem, you might see areas of synergy and mutual gain. For example, for a change or a new system to be rolled out successfully users need to understand how to perform tasks.
This is why TestDrive-UAT and other parts of the solution such as TestDrive-Assist create documentation and ‘how to’ videos as a by-product of the testing process. Is it part of software testing? Perhaps traditionally not, but it is part of getting a successful deployment.
Ah, so it is everyone’s job in some ways.
This is an extract from a whitepaper entitled “The Test Automation Silver Bullet, Myth or Reality?” You can read the complete article here.