One of the most common stories about test automation at companies is that testers in the team start creating test automation project in a very small scale, and with time, evolving it, growing it, patching it, and… failing the project.
In the presentation, we will discuss the steps of evolution for that common failing story, and propose a set of indicators (“traffic lights”), course-change options (“exit points”) and mitigations (“rescue guidelines”), that can be used by test managers and test engineers to steer clear from the pitfalls of a runaway automation project