"I joined the Forecasting project in early 2002; this was quite early in the development stage for a brand new version of Sage’s Forecasting product. This new product was to be our first release to use .NET technologies. At this stage no test scripts existed let alone any automated test cases, so it was more or less a clean slate that we had to work with. I already had some experience using automated tools from working on previous products and projects within Sage and initially I tried to amend the tools we already had to work with the new product. Unfortunately the existing framework had been developed using what was then a rival tool and this tool was not designed to be used with .NET products. Since the existing tools could not give us enough control over the product to satisfy what we wanted from automated testing, we decided that it would be beneficial to carry out research into some of the other tools on the market, and this is when we found TestComplete," said Peter Yates, Senior Testing Technician from Sage.
Standard Languages Save Time
Peter described why TestComplete's supported scripting languages are so important to them. "When we looked at some of the other tools they used their own proprietary development languages but with TestComplete being based around existing scripting technologies this meant a reduced learning curve. Also, since the testing phase of a software release always feels the pinch any time savings we could obtain were important."
Far Beyond Black Box Testing
"One of the main things I liked about TestComplete was its ability to allow the test developer access to any of the properties and methods available on the controls. This is invaluable when testing things like grids. The framework that had been used on previous com projects was very limited in how it could handle certain controls. We often had to write code to use simulated key presses to move to what we thought would be the correct position in the grid and then process the cell. With TestComplete we no longer have this problem and it is much easier to work with grid cells," said Peter.
Robust Control Handling
Peter explained how important it is for them to have a tool that frees them from having to use a control's ID. "The tool we had prior to TestComplete, the one which had been used on previous projects, used IDs to specify which control was to be processed. This approach meant every time a form changed we were having to change the IDs to ensure the correct control was being manipulated. Thankfully TestComplete has the ability to use the name of the control, so the only time we need to amend the code is if the control's name is changed."