An Doan, AKQA
Are you thinking about starting an automation project? Are you chest deep in test automation? You might not know it yet, but your automation project may be on a collision course with an undodgeable Hadouken Fireball. Certain telltale symptoms can help identify problems early. This paper discusses the key symptoms, what causes them, why they are terminal, and what you can do to diagnose and treat them. These anti-patterns, if left unattended, will degrade the quality and efficiency of your test automation, and may cause hardship and eventual failure of the automation project. As with all illnesses, having a symptom or two does not mean imminent failure. Awareness of the symptoms, however, including how to identify and treat them, can help avoid automation pitfalls.
In the context of a software test automation project, this paper looks at five key symptoms that may be evident, and could cause automation projects to fail.
Target audience: Intermediate