Difference between revisions of "TOOL DEPENDENCY"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (Put topic titles in capital letters) |
||
| 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-family: Arial; font-size: 16px">Issue summary</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Issue summary'''</span>= |
| − | <span style="font-family: Arial; font-size: 16px">Test automation is strongly dependent on some special tool. </span | + | <span style="font-family: Arial; font-size: 16px">Test automation is strongly dependent on some special tool. </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=" | + | =<span style="font-size: 16px">'''Examples'''</span>= |
| − | |||
| − | |||
# <span style="font-family: Arial; font-size: 16px">You have written all the automation scripts in the proprietary language of a particular capture-replay tool</span> | # <span style="font-family: Arial; font-size: 16px">You have written all the automation scripts in the proprietary language of a particular capture-replay tool</span> | ||
# <span style="font-family: Arial; font-size: 16px">You have to change to a different tool, but now you can't run any of your existing scripts without major work.</span> | # <span style="font-family: Arial; font-size: 16px">You have to change to a different tool, but now you can't run any of your existing scripts without major work.</span> | ||
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Questions</span>= | + | <span style="font-family: Arial; font-size: 16px">How to make sure that if and when the tool will have to be changed, you don't have to start again from scratch?</span> |
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Resolving Patterns</span>= | ||
<br /> <span style="font-size: 16px">Most recommended:</span><br /> | <br /> <span style="font-size: 16px">Most recommended:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">[[RIGHT TOOLS]]: use this pattern if your present tool doesn't fit the Software Under Test (SUT) well enough</span> | * <span style="font-size: 16px">[[RIGHT TOOLS]]: use this pattern if your present tool doesn't fit the Software Under Test (SUT) well enough</span> | ||
* <span style="font-size: 16px">[[TOOL INDEPENDENCE]]: this is the pattern of choice to solve this issue</span> | * <span style="font-size: 16px">[[TOOL INDEPENDENCE]]: this is the pattern of choice to solve this issue</span> | ||
<br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | <br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">[[ABSTRACTION LEVELS]]: this pattern helps you separate the technical tool layer from the functional test cases</span> | * <span style="font-size: 16px">[[ABSTRACTION LEVELS]]: this pattern helps you separate the technical tool layer from the functional test cases</span> | ||
* <span style="font-size: 16px">[[ OBJECT MAP]]: use this pattern with all tools </span> | * <span style="font-size: 16px">[[ OBJECT MAP]]: use this pattern with all tools </span> | ||
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span></div> | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Latest revision as of 08:47, 4 May 2018
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues
Issue summary
Test automation is strongly dependent on some special tool.
Category
Design
Examples
- You have written all the automation scripts in the proprietary language of a particular capture-replay tool
- You have to change to a different tool, but now you can't run any of your existing scripts without major work.
Questions
How to make sure that if and when the tool will have to be changed, you don't have to start again from scratch?
Resolving Patterns
Most recommended:
- RIGHT TOOLS: use this pattern if your present tool doesn't fit the Software Under Test (SUT) well enough
- TOOL INDEPENDENCE: this is the pattern of choice to solve this issue
Other useful patterns:
- ABSTRACTION LEVELS: this pattern helps you separate the technical tool layer from the functional test cases
- OBJECT MAP: use this pattern with all tools
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues