View source for MANUAL INTERVENTIONS

<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution 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">Test automation needs lots of manual handlings to work.</span>
=<span style="font-size: 16px">'''Category'''</span>=
<span style="font-size: 16px">Execution</span>
=<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>=
# <span style="font-family: Arial; font-size: 16px">The initial conditions for a test suite have to be set up by hand.</span>
# <span style="font-family: Arial; font-size: 16px">In some tests there are windows or components that could not be automated and have to be driven by hand.</span>
# Execution times vary greatly and thus test execution is stopped and restarted manually
# <span style="font-family: Arial; font-size: 16px">In order to run a retest all the other tests in the test suite have to be inactivated manually.</span>
# <span style="font-family: Arial; font-size: 16px">Test automation is started manually.</span>
# <span style="font-family: Arial; font-size: 16px">Automated verification is only simple so you can't tell if a test has passed or failed without looking at it.</span>
# <span style="font-family: Arial; font-size: 16px">Reporting of test results requires manual effort.</span>
# <span style="font-family: Arial; font-size: 16px">Integration of tools requires manual effort, and is slow, costly and unreliable</span>
=<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>=
<span style="font-family: Arial; font-size: 16px">Does the current test automation tool drive the Software Under Test (SUT) reliably?</span><br /> <span style="font-family: Arial; font-size: 16px">Are the initial conditions set automatically? If not, why not?</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">[[UNATTENDED TEST EXECUTION]]: Use this pattern for issues like Examples 1. and 5.</span>
* <span style="font-size: 16px">[[ONE-CLICK RETEST]]: this pattern helps solve issues similar to Example 4.</span>
* <span style="font-size: 16px">[[VARIABLE DELAYS]]: use this pattern if you have an issue like Example 3.</span>
<br /> <span style="font-size: 16px">The following patterns will help you solve issues like Example 2.</span><br /> 
* <span style="font-size: 16px">[[MIX APPROACHES]]</span>
* <span style="font-size: 16px">[[RIGHT TOOLS]]</span>
* <span style="font-size: 16px">[[TESTABLE SOFTWARE]]</span>
<br /> <span style="font-size: 16px">Better tool integration will help to solve issue 7. You may need to write some code to coordinate between the tools, an "automated bridge", but this will result in seamless automation rather than manual automation.</span><br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Issues]] / Back to [[Test Automation Issues]]</span></div>