Difference between revisions of "LOCALISED REGIMES"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[ Management Issues]] / Back to [[Test Automation Issues]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[ Management Issues]] / Back to [[Test Automation Issues]]</span> | ||
| − | =<span style="font-family: Arial; font-size: 16px">Issue Summary</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Issue Summary'''</span>= |
| − | + | <span style="font-size: 16px">Tool use or testware architecture is different from team to team</span><br /> <span style="font-size: 16px">This issue is closely related to the failure pattern [[FRAMEWORK COMPETITION]] from Michael Stahl</span> | |
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
| − | + | <span style="font-size: 16px">Management </span><br /> | |
| − | =<span style="font-family: Arial; font-size: 16px">Examples</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= |
| − | |||
| − | |||
* <span style="font-size: 16px">"everyone will do the sensible thing": most will do something sensible, but different</span> | * <span style="font-size: 16px">"everyone will do the sensible thing": most will do something sensible, but different</span> | ||
* <span style="font-size: 16px">"use the tool however it best suits you": ignores cost of learning how best to automate</span> | * <span style="font-size: 16px">"use the tool however it best suits you": ignores cost of learning how best to automate</span> | ||
| Line 12: | Line 10: | ||
* <span style="font-size: 16px">no re-use between teams</span> | * <span style="font-size: 16px">no re-use between teams</span> | ||
* <span style="font-size: 16px">multiple learning curves</span> | * <span style="font-size: 16px">multiple learning curves</span> | ||
| − | + | =<span style="font-size: 16px">'''Questions'''</span>= | |
| − | =<span style=" | + | <span style="font-size: 16px">Is there an overall strategy for automation?</span><br /> <span style="font-size: 16px">Is there any person charged with coordinating automation for the company/enterprise?</span><br /> |
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= | |
| − | <span style="font-family: Arial; font-size: 16px">Resolving Patterns</span>= | + | <span style="font-family: Arial; font-size: 16px">Most recommended:</span> |
| − | + | * <span style="font-size: 16px">[[DESIGN FOR REUSE]]: Design reusable testware</span> | |
| + | * <span style="font-size: 16px"> [[DON'T REINVENT THE WHEEL]]: Use available know-how, tools and processes whenever possible.</span> | ||
| + | * <span style="font-size: 16px"> [[SET STANDARDS]]: Set and follow standards for the automation artefacts</span> | ||
| + | * <span style="font-size: 16px">[[TEST AUTOMATION OWNER]]: Appoint an owner for the test automation effort</span><br /><br /> | ||
| + | <span style="font-size: 16px">Other useful patterns:</span><br /> | ||
| + | * <span style="font-size: 16px">[[GET TRAINING]]: Plan to get training for all those involved in the test automation project</span> | ||
| + | * <span style="font-size: 16px"> [[SHARE INFORMATION]]: Ask for and give information to managers, developers, other testers and customers</span><br /> <br /> | ||
| + | <span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[ Management Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Latest revision as of 16:39, 26 June 2018
................................................................................................................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: 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