DON'T REINVENT THE WHEEL

From Test Automation Patterns
Jump to: navigation, search
.................................................................................................................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 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:

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.

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