We have extensive experience in working with a variety of tools, such as Rational Robot, Segue's SilkTest, Mercury Interactive's WinRunner and QuickTest Pro, Rational Visual Test, Worksoft's Certify, Seapine's QA Wizard, etc.

Knowing when automation will be cost-effective, and recognizing when it is likely to turn into a boondoggle, is at least as important as knowing how to write maintainable and reusable, extensible, and robust automation code. Because of the tremendous efficiencies introduced by automation, its deficiencies are often overlooked.

We design the Test Automation Plan. Defining a Test Automation Plan is an important step because here we define how the data will be passed to test cases, how test scripts will be grouped together, and how we can group common code in modular functions so as to enable rapid accommodation of changes across product builds, minimizing the cost of script maintenance.

We have ascertained with:

1. How to write re-usable code, making automation extensible.
2. What parameters to monitor in Stress and Performance testing.
3. When to use which automation tool.
4. Which logging standards are the most informative and the easiest to parse.

Once we have defined the Test Automation Plan, and our client has approved it, we begin coding. We strictly follow our coding standards. Our rigorous Code Reviews ensure that we observe coding guidelines, handle data correctly, avoid logical errors, and generate fully informative logs.
We test our own automation scripts. We pass various types of data to the scripts, if test cases are data driven, and execute them on the platform or product under test to make sure that the automation is working as expected and failures are not due to errors in coding.

Our purpose is to ensure efficient automation for our customer's specific needs.