Difference between revisions of "Testers think that the Software Under Test is too complex for automation"

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">To solve this problem you can look up one or more of the following issues:</span><br /...")
 
m
 
Line 4: Line 4:
 
# <span style="font-size: 16px">''[[INADEQUATE COMMUNICATION]]'': if testers just have no idea what automation can or cannot do for them</span>
 
# <span style="font-size: 16px">''[[INADEQUATE COMMUNICATION]]'': if testers just have no idea what automation can or cannot do for them</span>
 
# <span style="font-size: 16px">''[[INADEQUATE TOOLS]]'': if the testers justly notice that the available tools are inadequate for the job</span>
 
# <span style="font-size: 16px">''[[INADEQUATE TOOLS]]'': if the testers justly notice that the available tools are inadequate for the job</span>
<br /> <br /> <span style="background-color: #ffffff; color: #000000; font-size: 16px">Return to "[[Testers don't help the automation team]]"</span></div>
+
<br /> <br /> <span style="background-color: #ffffff; color: #000000; font-size: 16px">Return to [[Testers don't help the automation team]]</span></div>

Latest revision as of 14:30, 25 June 2018

To solve this problem you can look up one or more of the following issues:

  1. UNREALISTIC EXPECTATIONS: if testers believe that you are supposed to automate everything and don't realize that even automating only a small area of the Software Under Test (SUT) would take away some of their load
  2. INADEQUATE COMMUNICATION: if testers just have no idea what automation can or cannot do for them
  3. INADEQUATE TOOLS: if the testers justly notice that the available tools are inadequate for the job


Return to Testers don't help the automation team