Having been involved in software testing for some 20 years and witnessed the land-grab for customer attention and market share, the varying mathematical ROI calculations, the year 2000 doomsday forecasters and the rise of the dominant players today, I thought it may be helpful to note a few of the key points to watch for. This is by no means a complete list however I hope you’ll find it a useful read or a memory jogger for those who’ve been there before.

1. Changes to the UI. Whilst naturally frequently necessary, these typically break automation scripts and mean the script needs fixing. This isn’t a problem and of course is expected but it’s worth considering this in your time planning and writing the scripts with maintainability in mind.

2. Exploratory testing. Too often there’s not sufficient time. Remember that users don’t always do what you’d like them to with your software, so if you can find time for this type of testing it will pay you back.

3. Make sure your test scripts cater for unexpected events like pop-ups either in the System Under Test (SUT) or another application.

4. With the scripts, try to separate assets such as data, logic, test conditions and environments, reducing dependencies.

5. Do try to create smaller, modular reusable scripts rather than single monolithic test scripts. Lightweight reusable assets can be shared between test cases, reducing your scripting time and subsequent risk of failures.

6. Build automation is steps, prioritising a few test cases initially and then adding more in phases.

7. Do share as much of the automation ownership as you can. Nobody wants to be reliant on one or two key individuals.

As I said, by no means an exhaustive list but we hope you find this useful. Please do contact us if you feel we may be able to help.