EXPECT INCIDENTS

From Test Automation Patterns
Jump to: navigation, search
.................................................................................................................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

INEFFICIENT EXECUTION

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.

.................................................................................................................Main Page / Back to Execution Patterns/ Back to Test Automation Patterns