My Introduction to test Automation was with an open source program and since then I have been progressively looking at what test automation tools are suitable and easy to use. Later, we were having to test a web application where we used Selenium IDE tool which was very suitable to our skill levels and for testing the Web Application. My initial approach with a new system that we had to test was to use an existing server hosted locally. Using open source tools to automate the testing processes of our Windows application which connected to database servers, web services and windows mobile devices. I created automated tests which gave us considerable coverage, modularising them in order to easily fix tests that were not working. The tests also made it easier to identify bugs. This developed into a successful albeit a large test process which was used mostly for regression testing just before delivering a new release. Later, I used the same automated test tool, “AutoIT” and added the ability to generate emails, sending the test results to the team. Although this worked with a certain degree of success, the problem arose in integrating it with the build stack. We tried several approaches without success and a decision was made to use another test automation tool, “White” which did integrate with our build server “Team City”. My reservation with this software was having to learn to write code and not just scripts, for which I needed a paradigm shift. Once over my initial reservation, I plunged into the deep end, with some help from colleagues. Many of the lessons learnt from the previous Test Tools were invaluable during this phase of the journey. Once the automated tests were created in “White” and at the same point as they were in “AutoIT”, it was time to integrate them with our build server. The first step was to set up the build server to kick off the automated tests after the new build had completed. This meant having to create a clean database and then run the tests on a virtual server. We also needed a dedicated test machine available to run as a virtual user. We have been able to increase the test coverage, fine-tune the automated tests and include integrated tests on the Windows mobile devices. The process we have set in place has reduced our regression testing time from 2 weeks to 2 days. Since then I have been using a multitude of Test Automation Tools including Batch files, DOS scripting, SQL Scripts, AutoHotkey etc. These Test Tools have all added to the value of our Automated Test processes.