“Another common mistake is trying to get testers to do both jobs, so when management gives the go ahead for automation testing, any QA related job these days requires some level of automation and testers might get excited about the potential for test automation. But these are both full-time jobs, so often times [these] teams struggle with deciding what to spend limited time on.”
In a traditional environment, testing gets completed at the end of a development cycle. But as more and more companies move toward a DevOps and continuous delivery model in which software is constantly in development and must always be deployment-ready, leaving testing until the end no longer works. That’s where continuous testing comes in — to ensure quality at every stage of development.
This article uses the term “tester” to refer to the person involved in testing software with automation tools. It is not meant to distinguish by job title or technical proficiency. Jim Hazen describes himself as a hybrid, or “technical tester,” because he can write test scripts and develop what he refers to as “testware.” The trend is to hire for multiple skillsets, but that does not mean the non-technical stakeholders involved in software development don’t benefit from automation testing.