COMPLEX ENVIRONMENT

From Test Automation Patterns
Revision as of 15:11, 29 April 2018 by Seretta (talk | contribs) (Topic titles in capital letters)
Jump to navigation Jump to search
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues

Issue summary

The environment where the Software Under Test (SUT) has to run is complex

Category

Design

Examples

The problem range is:

  1. Different systems (hardware or software) that interact in some way.
  2. Test data is hard to create due to the number of systems involved or a limited refresh cycle.
  3. You have to simulate some hardware


Questions

Where does the complexity lie? In preparing the initial conditions? Test execution? Checking the results? Dependencies?
How do you collect the necessary data?

Resolving Patterns

Most recommended:

  • DO A PILOT: use this pattern to find out what the problems are and ways to tackle them
  • TAKE SMALL STEPS: use this pattern to break up the problems in more chewable chunks
  • THINK OUT-OF-THE-BOX: try to look at the problem from unusual viewpoints



Other useful patterns:


.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues