Difference between revisions of "MANUAL INTERVENTIONS"
Jump to navigation
Jump to search
m (Topic titles in capital letters) |
|||
| Line 21: | Line 21: | ||
* <span style="font-size: 16px">[[VARIABLE DELAYS]]: use this pattern if you have an issue like Example 3.</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 /> | <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">[[MIX APPROACHES]]: Don’t be afraid to use different tools or approaches</span> |
| − | * <span style="font-size: 16px">[[RIGHT TOOLS]]</span> | + | * <span style="font-size: 16px">[[RIGHT TOOLS]]: Select the right tools for your application, environment, people, budget and level of testing</span> |
| − | * <span style="font-size: 16px">[[TESTABLE SOFTWARE]]</span> | + | * <span style="font-size: 16px">[[TESTABLE SOFTWARE]]: Locate what kind of implementations in the Software Under Test (SUT) may make test automation difficult or impossible and find a solution as early as possible</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> | <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> | ||
Latest revision as of 16:35, 27 June 2018
.................................................................................................................Main Page / Back to Execution Issues / Back to Test Automation Issues
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.
.................................................................................................................Main Page / Back to Execution Issues / Back to Test Automation Issues
Issue summary
Test automation needs lots of manual handlings to work.
Category
Execution
Examples
- The initial conditions for a test suite have to be set up by hand.
- In some tests there are windows or components that could not be automated and have to be driven by hand.
- Execution times vary greatly and thus test execution is stopped and restarted manually
- In order to run a retest all the other tests in the test suite have to be inactivated manually.
- Test automation is started manually.
- Automated verification is only simple so you can't tell if a test has passed or failed without looking at it.
- Reporting of test results requires manual effort.
- Integration of tools requires manual effort, and is slow, costly and unreliable
Questions
Does the current test automation tool drive the Software Under Test (SUT) reliably?
Are the initial conditions set automatically? If not, why not?
Resolving Patterns
Most recommended:
- UNATTENDED TEST EXECUTION: Use this pattern for issues like Examples 1. and 5.
- ONE-CLICK RETEST: this pattern helps solve issues similar to Example 4.
- VARIABLE DELAYS: use this pattern if you have an issue like Example 3.
The following patterns will help you solve issues like Example 2.
- MIX APPROACHES: Don’t be afraid to use different tools or approaches
- RIGHT TOOLS: Select the right tools for your application, environment, people, budget and level of testing
- TESTABLE SOFTWARE: Locate what kind of implementations in the Software Under Test (SUT) may make test automation difficult or impossible and find a solution as early as possible
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.
.................................................................................................................Main Page / Back to Execution Issues / Back to Test Automation Issues