View source for AD-HOC AUTOMATION

<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">Automation is done ad-hoc with no planning or preparation.</span><br /> <br /> <span style="font-family: Arial; font-size: 16px">"Ad hoc" means something created or done only for a particular purpose, impromptu, expedient, improvised, makeshift, "rough and ready".</span> 
=<span style="font-size: 16px">'''Category'''</span>=
<span style="font-size: 16px">Management </span> 
=<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>=
* <span style="font-size: 16px">Management thought that buying a tool was enough. Goals, architecture, resources etc. have not been planned or considered</span>
* <span style="font-size: 16px">Expenses for test automation resources have not been budgeted</span>
* <span style="font-size: 16px">There are not enough machines on which to run automation</span>
* <span style="font-size: 16px">The databases for automation have to be shared with development or testing</span>
* <span style="font-size: 16px">There are not enough tool licences</span>
* <span style="font-size: 16px"> Automation is done "on the side" when one has time to spare</span>
* <span style="font-size: 16px">Support from testers, developers or other specialists has not been planned, so they have no time to help</span>
=<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>=
<span style="font-family: Arial; font-size: 16px">Who is doing automation? Is somebody in charge?</span><br /> <span style="font-family: Arial; font-size: 16px">Does management know about it? Do they support it?</span>
=<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>=
<span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> 
* <span style="font-size: 16px"><span style="font-size: 16px"><span style="font-size: 16px">[[TEST AUTOMATION OWNER]]: </span>Appoint an owner for the test automation effort. If there is already a "champion" give him or her public support. </span>The owner, once test automation has been established, controls that it stays "healthy" and keeps an eye on new tools, techniques or processes in order to improve it.</span>
* <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: you need this pattern in order to be able to apply the other patterns.</span>
* <span style="font-size: 16px">[[DEDICATED RESOURCES]]: helps you get the resources you need.</span>
* <span style="font-size: 16px">[[WHOLE TEAM APPROACH]]: if your developer team uses an agile development process, this is the pattern of choice.</span>
<br /> <span style="font-size: 16px">Other useful patterns:</span><br /> 
* <span style="font-size: 16px"><span style="font-size: 16px"><span style="font-size: 16px">[[SET CLEAR GOALS]]: </span>Define the automation goals from the very beginning </span>and when you want to re-vitalise a stalled automation effort.</span>
* <span style="font-size: 16px"><span style="font-size: 16px">[[DO A PILOT]]: </span>Start a pilot project to explore how to best automate tests for the application.</span>
* <span style="font-size: 16px">[[TEST AUTOMATION BUSINESS CASE]]: this pattern may be needed when you start planning test automation or to justify making changes to existing automation that has stalled or not given sufficient benefit.</span>
<br /> <span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[ Management Issues]] / Back to [[Test Automation Issues]]</span></div>