Difference between revisions of "Lack of direction"

Revision as of 10:56, 3 August 2018

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:

Nobody is in charge of test automation, everybody does what he or she thinks best without cooperating with the others
Automation is done ad-hoc without a leading strategy or architecture

More reasons for lack of direction:

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
Automators believe that they have to automate the manual test cases as is. You probably have a case of MANUAL MIMICRY
Testers doing automation don't know how to do it well. The issue LIMITED EXPERIENCE can help you solve this kind of problem
Tool use or testware architecture is different from team to team. Look up the issue LOCALISED REGIMES
The important tests have not been automated, only the easy ones. This could be a case of UNFOCUSED AUTOMATION.

@@ Line 10: / Line 10: @@
 # <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>
-<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>