Difference between revisions of "EXPECT INCIDENTS"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]]/ Back to [[Test Automation Patterns]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]]/ Back to [[Test Automation Patterns]]</span> | ||
| − | =<span style="font-size: 16px">Pattern summary</span>= | + | =<span style="font-size: 16px">'''Pattern summary'''</span>= |
<span style="font-size: 16px">Automated scripts should be able to react to unexpected incidents without disrupting execution</span> | <span style="font-size: 16px">Automated scripts should be able to react to unexpected incidents without disrupting execution</span> | ||
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
<span style="font-size: 16px">Execution</span> | <span style="font-size: 16px">Execution</span> | ||
| − | =<span style="font-size: 16px">Context</span>= | + | =<span style="font-size: 16px">'''Context'''</span>= |
<span style="font-size: 16px">This pattern is especially useful for long living automation where unexpected changes would otherwise disrupt execution.</span> | <span style="font-size: 16px">This pattern is especially useful for long living automation where unexpected changes would otherwise disrupt execution.</span> | ||
| − | =<span style="font-size: 16px">Description</span>= | + | =<span style="font-size: 16px">'''Description'''</span>= |
<span style="font-size: 16px">Incidents can be:</span><br /> | <span style="font-size: 16px">Incidents can be:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">unexpected windows or pop-ups </span> | * <span style="font-size: 16px">unexpected windows or pop-ups </span> | ||
* <span style="font-size: 16px">windows that sometimes show up and sometimes don't</span> | * <span style="font-size: 16px">windows that sometimes show up and sometimes don't</span> | ||
* <span style="font-size: 16px">actions that take variable time to execute</span> | * <span style="font-size: 16px">actions that take variable time to execute</span> | ||
<span style="font-size: 16px">Your test scripts must be able to react accordingly so that execution can continue.</span> | <span style="font-size: 16px">Your test scripts must be able to react accordingly so that execution can continue.</span> | ||
| − | =<span style="font-size: 16px">Implementation</span>= | + | =<span style="font-size: 16px">'''Implementation'''</span>= |
<span style="font-size: 16px">Depending on the type of incidents, here are some suggestions about how to react:</span><br /> | <span style="font-size: 16px">Depending on the type of incidents, here are some suggestions about how to react:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">Unexpected Windows or pop-ups: modern tools offer the option to just click them off. </span> | * <span style="font-size: 16px">Unexpected Windows or pop-ups: modern tools offer the option to just click them off. </span> | ||
* <span style="font-size: 16px">For windows that don't always show up or actions that take variable time to execute: look up the pattern [[ VARIABLE DELAYS]].</span> | * <span style="font-size: 16px">For windows that don't always show up or actions that take variable time to execute: look up the pattern [[ VARIABLE DELAYS]].</span> | ||
| − | =<span style="font-size: 16px">Potential problems</span>= | + | =<span style="font-size: 16px">'''Potential problems'''</span>= |
<span style="font-size: 16px">Be careful when clicking off an unexpected window: it could be a bug! Instead of ignoring it, write a warning in the log.</span> | <span style="font-size: 16px">Be careful when clicking off an unexpected window: it could be a bug! Instead of ignoring it, write a warning in the log.</span> | ||
| − | =<span style="font-size: 16px">Issues addressed by this pattern</span>= | + | =<span style="font-size: 16px">'''Issues addressed by this pattern'''</span>= |
''<span style="font-size: 16px">[[INEFFICIENT EXECUTION]]</span>'' | ''<span style="font-size: 16px">[[INEFFICIENT EXECUTION]]</span>'' | ||
| − | =<span style="font-size: 16px">Experiences</span>= | + | =<span style="font-size: 16px">'''Experiences'''</span>= |
| − | <span style="font-size: 16px">If you have used this pattern, please | + | |
| + | <span style="font-size: 16px">If you have used this pattern and would like to contribute your experience to the wiki, please go to [[Feedback]] to submit your experience or comment.</span><br /> <br /> | ||
| + | |||
| + | <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]]/ Back to [[Test Automation Patterns]]</span></div> | ||
Latest revision as of 16:02, 21 August 2018
.................................................................................................................Main Page / Back to Execution Patterns/ Back to Test Automation Patterns
Pattern summary
Automated scripts should be able to react to unexpected incidents without disrupting execution
Category
Execution
Context
This pattern is especially useful for long living automation where unexpected changes would otherwise disrupt execution.
Description
Incidents can be:
- unexpected windows or pop-ups
- windows that sometimes show up and sometimes don't
- actions that take variable time to execute
Your test scripts must be able to react accordingly so that execution can continue.
Implementation
Depending on the type of incidents, here are some suggestions about how to react:
- Unexpected Windows or pop-ups: modern tools offer the option to just click them off.
- For windows that don't always show up or actions that take variable time to execute: look up the pattern VARIABLE DELAYS.
Potential problems
Be careful when clicking off an unexpected window: it could be a bug! Instead of ignoring it, write a warning in the log.
Issues addressed by this pattern
Experiences
If you have used this pattern and would like to contribute your experience to the wiki, please go to Feedback to submit your experience or comment.