.................................................................................................................Home / Back to Process Patterns / Back to Test Automation Patterns
Pattern summary
Use the same good programming practices for test code as in software development for production code.
The Mind Map shows how this pattern relates to its related issues and patterns.


Category
Process

Context
This pattern is appropriate when you want your automation scripts to be reusable and maintainable, that is when your test automation is to be long lived.
This pattern is not necessary if you only write short disposable scripts.

Description
Scripting is a kind of programming, so you should use the same good practices as in software development.

Implementation
If you don’t have an automation engineer, have developers coach the automation testers. Important good practices are:

Put your best practices in a Wiki so that both testers and developers profit from them.

Potential problems
If the software developers don't use good programming practices, then don't follow them, but investigate good programming outside of your company. (Read books!)

Issues addressed by this pattern
BRITTLE SCRIPTS
DATA CREEP
GIANT SCRIPTS
HIGH ROI EXPECTATIONS
OBSCURE TESTS
SCRIPT CREEP
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!

.................................................................................................................Home / Back to Process Patterns / Back to Test Automation Patterns
B3 11