Difference between revisions of "COMPLEX ENVIRONMENT"
Jump to navigation
Jump to search
| (3 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 [Design Issues]] / Back to [Test Automation Issues]]</span | + | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span> |
| − | =<span style="font-size: 16px">Issue summary</span>= | + | =<span style="font-size: 16px">'''Issue summary'''</span>= |
| − | <span style="font-size: 16px">The environment where the Software Under Test (SUT) has to run is complex</span | + | <span style="font-size: 16px">The environment where the Software Under Test (SUT) has to run is complex</span> |
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
| − | <span style="font-size: 16px">Design</span | + | <span style="font-size: 16px">Design</span> |
| − | =<span style="font-size: 16px">Examples</span>= | + | =<span style="font-size: 16px">'''Examples'''</span>= |
<span style="font-size: 16px"> The problem range is:</span><br /> | <span style="font-size: 16px"> The problem range is:</span><br /> | ||
| − | |||
# <span style="font-size: 16px">Different systems (hardware or software) that interact in some way.</span> | # <span style="font-size: 16px">Different systems (hardware or software) that interact in some way.</span> | ||
# <span style="font-size: 16px">Test data is hard to create due to the number of systems involved or a limited refresh cycle.</span> | # <span style="font-size: 16px">Test data is hard to create due to the number of systems involved or a limited refresh cycle.</span> | ||
# <span style="font-size: 16px">You have to simulate some hardware</span> | # <span style="font-size: 16px">You have to simulate some hardware</span> | ||
| − | + | =<span style="font-size: 16px">'''Questions'''</span>= | |
| − | =<span style="font-size: 16px">Questions</span>= | + | <span style="font-family: Arial; font-size: 16px">Where does the complexity lie? In preparing the initial conditions? Test execution? Checking the results? Dependencies?</span><br /> <span style="font-size: 16px">How do you collect the necessary data?</span> |
| − | <span style="font-family: Arial; font-size: 16px">Where does the complexity lie? In preparing the initial conditions? Test execution? Checking the results? Dependencies?</span><br /> <span style="font-size: 16px">How do you collect the necessary data?</span | + | =<span style="font-size: 16px">'''Resolving Patterns'''</span>= |
| − | =<span style="font-size: 16px">Resolving Patterns</span>= | ||
<span style="font-size: 16px"> Most recommended:</span><br /> | <span style="font-size: 16px"> Most recommended:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">[[DO A PILOT]]: use this pattern to find out what the problems are and ways to tackle them</span> | * <span style="font-size: 16px">[[DO A PILOT]]: use this pattern to find out what the problems are and ways to tackle them</span> | ||
* <span style="font-size: 16px">[[TAKE SMALL STEPS]]: use this pattern to break up the problems in more chewable chunks</span> | * <span style="font-size: 16px">[[TAKE SMALL STEPS]]: use this pattern to break up the problems in more chewable chunks</span> | ||
* <span style="font-size: 16px">[[THINK OUT-OF-THE-BOX]]: try to look at the problem from unusual viewpoints</span> | * <span style="font-size: 16px">[[THINK OUT-OF-THE-BOX]]: try to look at the problem from unusual viewpoints</span> | ||
| − | + | <br /><span style="font-size: 16px">Other useful patterns:</span><br /> | |
| − | |||
* <span style="font-size: 16px">[[KEEP IT SIMPLE]]: this pattern is always helpful</span> | * <span style="font-size: 16px">[[KEEP IT SIMPLE]]: this pattern is always helpful</span> | ||
* <span style="font-size: 16px">[[ SHARE INFORMATION]]: use this pattern for better communication between development, testing and automation </span> | * <span style="font-size: 16px">[[ SHARE INFORMATION]]: use this pattern for better communication between development, testing and automation </span> | ||
| − | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]] | + | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]] |
Latest revision as of 15:43, 27 June 2018
.................................................................................................................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:
- Different systems (hardware or software) that interact in some way.
- Test data is hard to create due to the number of systems involved or a limited refresh cycle.
- 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:
- KEEP IT SIMPLE: this pattern is always helpful
- SHARE INFORMATION: use this pattern for better communication between development, testing and automation
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues