Difference between revisions of "DON'T REINVENT THE WHEEL"
m (→Context) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 5: | Line 5: | ||
<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 almost 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> | ||
| Line 20: | Line 21: | ||
=<span style="font-size: 16px">'''Experiences'''</span>= | =<span style="font-size: 16px">'''Experiences'''</span>= | ||
| − | <span style="font-size: 16px">If you have used this pattern and would like to contribute your experience to the wiki, please go to [[ | + | <span style="font-size: 16px">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.</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: 14px">.................................................................................................................[[Main Page]] / Back to [[ Design Patterns]] / Back to [[Test Automation Patterns]]</span></div> | ||
Latest revision as of 10:08, 22 February 2019
Pattern summary
Use available know-how, tools and processes whenever possible.
Category
Design
Context
Use this pattern for efficient automation, but it is almost 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 and would like to contribute your experience to the wiki, please go to Feedback to submit your experience or comment.