Reducing time of test maintanence

to add to Marsha_R & tristaanogre

In my case I keep layers of scripts.

for eg to interact with GUI I have separate layer and test steps to interact with data in separate layer.

so ones GUI changes I have to only change GUI interaction layer 

If need a new test using same GUI can re-use GUI interaction layer 

It's not TDD but bit close to that concept...

different environment (for eg test running machines) have different speeds. 

Your waiting time for objects should be planed and suits for slower environment still run faster in others.

Always do mapping manually , select properties carefully.

Get to know best practice of your selected language and better if you know bit of project management.

(test automation is a software project it self)

test should be as much as independent. If test A fails still you may need to run test B.

(think of senarion, if test A fails all the test from B..to Z fails  )

use KISS philosophy

If you can use test management tool that also would be help if testes are going to grow. 

always think in long term perspective, most automation would need some time to return the investment.   

Also I recommend to read ISTQB documents if you have enough time