Difference between revisions of "Lack of direction"

From Test Automation Patterns
Jump to navigation Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px">Please select what you think is the main reason for the lack of direction</span><br />...")
 
m
 
(3 intermediate revisions by 2 users not shown)
Line 6: Line 6:
  
 
# <span style="font-size: 16px">Management doesn't support automation so it is done underhand by a lonely crusader. ''[[INADEQUATE SUPPORT]]'' is the issue to look up in this case</span>
 
# <span style="font-size: 16px">Management doesn't support automation so it is done underhand by a lonely crusader. ''[[INADEQUATE SUPPORT]]'' is the issue to look up in this case</span>
# <span style="font-size: 16px">Automators believe that they have to automate the manual test cases as is. You probably have a case of ''[[SORCERER'S APPRENTICE SYNDROME]]''</span>
+
# <span style="font-size: 16px">Automators believe that they have to automate the manual test cases as is. You probably have a case of ''[[MANUAL MIMICRY]]'' or ''[[INTERDEPENDENT TEST CASES]]''</span>
 
# <span style="font-size: 16px">Testers doing automation don't know how to do it well. The issue ''[[LIMITED EXPERIENCE]]'' can help you solve this kind of problem</span>
 
# <span style="font-size: 16px">Testers doing automation don't know how to do it well. The issue ''[[LIMITED EXPERIENCE]]'' can help you solve this kind of problem</span>
 
# <span style="font-size: 16px">Tool use or testware architecture is different from team to team</span>. <span style="font-size: 16px">Look up the issue ''[[LOCALISED REGIMES]]''</span>
 
# <span style="font-size: 16px">Tool use or testware architecture is different from team to team</span>. <span style="font-size: 16px">Look up the issue ''[[LOCALISED REGIMES]]''</span>
 
# <span style="font-size: 16px">The important tests have not been automated, only the easy ones. This could be a case of ''[[UNFOCUSED AUTOMATION]]''.</span>
 
# <span style="font-size: 16px">The important tests have not been automated, only the easy ones. This could be a case of ''[[UNFOCUSED AUTOMATION]]''.</span>
 
<br /> <span style="background-color: #ffffff; color: #000000; font-size: 16px">Return to [[Improve or revive test automation]]</span></div>
 
<br /> <span style="background-color: #ffffff; color: #000000; font-size: 16px">Return to [[Improve or revive test automation]]</span></div>

Latest revision as of 14:25, 18 March 2019

Please select what you think is the main reason for the lack of direction

For the following items the issue of choice is AD-HOC AUTOMATION:
  1. Nobody is in charge of test automation, everybody does what he or she thinks best without cooperating with the others
  2. Automation is done ad-hoc without a leading strategy or architecture


More reasons for lack of direction:

  1. Management doesn't support automation so it is done underhand by a lonely crusader. INADEQUATE SUPPORT is the issue to look up in this case
  2. Automators believe that they have to automate the manual test cases as is. You probably have a case of MANUAL MIMICRY or INTERDEPENDENT TEST CASES
  3. Testers doing automation don't know how to do it well. The issue LIMITED EXPERIENCE can help you solve this kind of problem
  4. Tool use or testware architecture is different from team to team. Look up the issue LOCALISED REGIMES
  5. The important tests have not been automated, only the easy ones. This could be a case of UNFOCUSED AUTOMATION.

Return to Improve or revive test automation