LOCALISED REGIMES

From Test Automation Patterns
Revision as of 08:43, 5 April 2018 by Cathal (talk | contribs) (Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues

Issue Summary


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

Category


Management

Examples


  • "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


Questions


Is there an overall strategy for automation?
Is there any person charged with coordinating automation for the company/enterprise?

= Resolving Patterns=


Most recommended:
DESIGN FOR REUSE
DON'T REINVENT THE WHEEL
SET STANDARDS
TEST AUTOMATION OWNER

Other useful patterns:
GET TRAINING
SHARE INFORMATION

................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues