Your Best Practice Tips for building reliable scripts.

Over the years I've fallen into some pretty bad habits that I would love to break. One of the things that I always strive for is creating scripts that only fail when there is a problem and never because of some slight change to the SUT or slowness in the SUT. I realize this is an ongoing process as much as it is a goal. I'd like to ping the community to get your best tips in creating bullet proof scripts.

Some ongoing thoughts:

1. Your testing a browser and a page that took 5 seconds to load now takes a minute. Your script fails but there is no bug just because of slow load time. What is the best code for avoiding this?

2. You capture an image to CLICK and a few runs later or a month later the same image which looks perfectly fine is no longer found. How do you avoid this?

I know there are areas of the Manual that cover these things. But I'm curious to see if any of you out there have found other solutions.

Thanks!
Sign In or Register to comment.