Difference between revisions of "DON'T REINVENT THE WHEEL"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
(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 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 [[Design 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">Use available know-how, tools and processes whenever possible.</span> | <span style="font-size: 16px">Use available know-how, tools and processes whenever possible.</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">Context</span>= | + | =<span style="font-size: 16px">'''Context'''</span>= |
<span style="font-size: 16px">Use this pattern for efficient automation, but it is always useful!</span> | <span style="font-size: 16px">Use this pattern for efficient automation, but it is always useful!</span> | ||
| − | =<span style="font-size: 16px">Description</span>= | + | =<span style="font-size: 16px">'''Description'''</span>= |
<span style="font-size: 16px">Use available know-how, tools and processes whenever possible. Reuse available data. Reuse scripts or libraries: you save lots of effort because you can just use testware that has already been tested and implemented.</span><br /> <br /> <span style="font-size: 16px">'James Tony': Duplication is to be avoided! Copy and paste is (usually) the wrong thing to do – repeated cloning and tweaking of tests can lead to high technical debt and having to make the same change in many places when the requirements change</span> | <span style="font-size: 16px">Use available know-how, tools and processes whenever possible. Reuse available data. Reuse scripts or libraries: you save lots of effort because you can just use testware that has already been tested and implemented.</span><br /> <br /> <span style="font-size: 16px">'James Tony': Duplication is to be avoided! Copy and paste is (usually) the wrong thing to do – repeated cloning and tweaking of tests can lead to high technical debt and having to make the same change in many places when the requirements change</span> | ||
| − | =<span style="font-size: 16px">Implementation</span>= | + | =<span style="font-size: 16px">'''Implementation'''</span>= |
<span style="font-size: 16px">Some suggestions: </span><br /> | <span style="font-size: 16px">Some suggestions: </span><br /> | ||
| − | |||
* <span style="font-size: 16px">[[GET TRAINING]]: you don’t have to invent everything yourself!</span> | * <span style="font-size: 16px">[[GET TRAINING]]: you don’t have to invent everything yourself!</span> | ||
* <span style="font-size: 16px">[[PREFER FAMILIAR SOLUTIONS]]: take advantage of what know-how is already available in your company</span> | * <span style="font-size: 16px">[[PREFER FAMILIAR SOLUTIONS]]: take advantage of what know-how is already available in your company</span> | ||
* <span style="font-size: 16px">For ''[[REPETITIOUS TESTS]]'' implement [[ DATA-DRIVEN TESTING]]</span> | * <span style="font-size: 16px">For ''[[REPETITIOUS TESTS]]'' implement [[ DATA-DRIVEN TESTING]]</span> | ||
* <span style="font-size: 16px">Look for common keywords and implement [[KEYWORD-DRIVEN TESTING]]</span> | * <span style="font-size: 16px">Look for common keywords and implement [[KEYWORD-DRIVEN TESTING]]</span> | ||
| − | =<span style="font-size: 16px">Recommendations</span>= | + | =<span style="font-size: 16px">'''Recommendations'''</span>= |
<span style="font-size: 16px">[[DESIGN FOR REUSE]]: Write scripts so that they can be reused and reuse them. </span><br /> <span style="font-size: 16px">Create generalized data that can be reused and reuse it</span> | <span style="font-size: 16px">[[DESIGN FOR REUSE]]: Write scripts so that they can be reused and reuse them. </span><br /> <span style="font-size: 16px">Create generalized data that can be reused and reuse it</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">Experiences</span>= | + | ''<span style="font-size: 16px">[[ LOCALISED REGIMES]]</span>''<br /> ''<span style="font-size: 16px">[[REPETITIOUS TESTS]]</span>''<br /> ''<span style="font-size: 16px">[[TEST DATA LOSS]]</span>'' |
| + | =<span style="font-size: 16px">'''Experiences'''</span>= | ||
<span style="font-size: 16px">If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[ Design Patterns]] / Back to [[Test Automation Patterns]]</span></div> | <span style="font-size: 16px">If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[ Design Patterns]] / Back to [[Test Automation Patterns]]</span></div> | ||
Revision as of 08:47, 30 April 2018
.................................................................................................................Main Page / Back to Design Patterns / Back to Test Automation Patterns
.................................................................................................................Main Page / Back to Design Patterns / Back to Test Automation Patterns
Pattern summary
Use available know-how, tools and processes whenever possible.
Category
Design
Context
Use this pattern for efficient automation, but it is always useful!
Description
Use available know-how, tools and processes whenever possible. Reuse available data. Reuse scripts or libraries: you save lots of effort because you can just use testware that has already been tested and implemented.
'James Tony': Duplication is to be avoided! Copy and paste is (usually) the wrong thing to do – repeated cloning and tweaking of tests can lead to high technical debt and having to make the same change in many places when the requirements change
Implementation
Some suggestions:
- GET TRAINING: you don’t have to invent everything yourself!
- PREFER FAMILIAR SOLUTIONS: take advantage of what know-how is already available in your company
- For REPETITIOUS TESTS implement DATA-DRIVEN TESTING
- Look for common keywords and implement KEYWORD-DRIVEN TESTING
Recommendations
DESIGN FOR REUSE: Write scripts so that they can be reused and reuse them.
Create generalized data that can be reused and reuse it
Issues addressed by this pattern
LOCALISED REGIMES
REPETITIOUS TESTS
TEST DATA LOSS
Experiences
If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!.................................................................................................................Main Page / Back to Design Patterns / Back to Test Automation Patterns