GOOD PROGRAMMING PRACTICES

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

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
BUGGY SCRIPTS
DATA CREEP
GIANT SCRIPTS
HIGH ROI EXPECTATIONS
OBSCURE TESTS
SCRIPT CREEP
TEST DATA LOSS
TOOL-DRIVEN AUTOMATION

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 Process Patterns / Back to Test Automation Patterns