There are plenty of books, blogs, talks etc. that teach how to do good test automation. The problem comes when trying to convince management to support these efforts. Showing them that what is being done right now in their company is exactly one of the disruptive methods I describe, usually gives them a beneficial jolt! By describing seven proven methods to destroy test automation I give managers, testers and automators not only the means to recognize early on if their automation is in danger, but by ‘warning’ against possible defences I will actually give them the tools to counter and solve such issues.
Solutions to most test automation issues have already been found and applied by experienced practitioners. Together with Dorothy Graham, we have collected such solutions (Patterns) in a public wiki (the Test Automation Patterns wiki) and in this e-book I will point out which patterns to apply to solve the presented methods (Issues).
Some examples of the ‘methods’:
- Let a lone champion keep all important knowledge to himself or herself.
- Develop all your scripts or keywords exclusively within a specific tool.
- Ignore good programming practices.
- Set impossible goals.
- Recognize test automation issues before they can do real harm
- Get a set of proven solutions to those same issues
- Know how to access and use the test automation patterns wiki