![[Level:23]](http://www.vietnamesetestingboard.org/zbxe/modules/point/icons/default/23.gif "Point:16430point (39%), Level:23/30"){kind=icon}
mathi.7664In this section we consider the aspects influencing the choice of tool automation testing.
First, you should pay attention to how well a tool for automating recognize the controls in your application. In the case when the elements are not recognized should look for plug-in, or the appropriate module. If there is no - the instrument should be abandoned. The more elements can recognize an instrument - the more time you will save on writing scripts and support!
Secondly, we must pay attention to how long it takes to support the scripts written by the selected tool. To do this, write a simple script that selects a menu item, and then imagine that has changed the menu to be selected. If disaster recovery scenario, you have to rewrite the script entirely, the tool is not optimal, since the real scenario is much more difficult. Best of all a tool that allows you to make the button name to the variable at the beginning of the script and quickly replaced by its value. Ideally - to describe the menu as a class.
And the last thing that you want to pay attention - how convenient tool for writing new scripts. How long does it at the time, how to structure code (support for the PLO) as the code reads as convenient development environment for refactoring (refactoring), etc.
It is best to make the right decisions about automation to answer the questions "Why? What? How "in that order. This will help avoid wasted time and nerves of Finance. On the other hand you can get the reliability, speed and quality!
Written by
Mathi,
Testing executive
