Despite the agile methodology having been around for almost 20 years, many people consider testing specialists as an unessential part of a project. With the arrival of Dev-Ops, automation and CI/CD, the time for thorough exploratory testing is often diminished. In many companies, the heavy coding skill set is being favoured to help deliver software, and there is even an adage that devs can do it, so why would they need testers?
The decision to exclude testers often stems from the lack of understanding as to what a tester really does and the value they can bring to a project. In the short term, they can help projects to establish a quality focus with different techniques and processes. Long term, they can coach and empower teams to implement better testing strategies in their day to day delivery. In order to truly understand the significance of testers, this blog focuses on their role on a project, the cost of not having testers on projects and looks at the argument as to why automation couldn’t and shouldn’t replace test engineers.