Tool use or testware architecture is different from team to team
This issue is closely related to the failure pattern FRAMEWORK COMPETITION from Michael Stahl
- "everyone will do the sensible thing": most will do something sensible, but different
- "use the tool however it best suits you": ignores cost of learning how best to automate
- effort is wasted by repeatedly solving the same problem in different ways
- no re-use between teams
- multiple learning curves
Is there an overall strategy for automation?
Is there any person charged with coordinating automation for the company/enterprise?
- DESIGN FOR REUSE: Design reusable testware
- DON'T REINVENT THE WHEEL: Use available know-how, tools and processes whenever possible.
- SET STANDARDS: Set and follow standards for the automation artefacts
- TEST AUTOMATION OWNER: Appoint an owner for the test automation effort
Other useful patterns:
- GET TRAINING: Plan to get training for all those involved in the test automation project
- SHARE INFORMATION: Ask for and give information to managers, developers, other testers and customers