It is still very much the words of automated testing tools, possible nor necessary to look at all of the testing tools; personally feel that knowledge when learning of many similar or related topics, go several steps:
1, to learn all the common theoretical knowledge of similar , this is a principle part of the [common]
2, to learn all the unique characteristics of the same kind of knowledge, skills, personality is part of [this]
3, depending on the actual scene, the proper use of the knowledge [that is, the use of knowledge to solve part of the personality problem specific
learning automated testing tools, too, and before not want to learn too much because they are afraid to confuse, now have a certain understanding of the curing existing knowledge [that is] to understand the basic principles, we can learn from the new personalized things; and this step can properly apply the knowledge in the future precisely in order to smoothly carry out the development and implementation of automated testing tasks. The goal of men!
Business Tools:
1, kylinTOP:
This is a home-made automated testing tools, support WEB APP and automated testing, intelligent positioning elements which are the main features of this automation software, the design concept is more advanced testing tools, could be considered in a number of automated testing tools and do a more prominent. Official website: www.70testing.com
2, WinRunner:
known as enterprise-level automation tool, scripting language is more difficult to use, but also very expensive, did not understand it, because it looks like the updated version is not supported
3, Rational Robot
is also known as enterprise-level automated testing tools, IBM-related companies will use, but also very expensive, did not understand it, because the installation file size, but also cracked
4、QTP：
This all know, support recording, support for plug-ins, plug-in extensions support section, currently only used the web plug-in, the windows default functions. Getting nature is very easy to do, just record can have a script out, can be executed, but the real implementation is not the case; qtp personally feel that the deployment of a large number of automated testing is not its advantages, it is no good batch execution management framework even qc is not integrated into the cool, after all is a tool to call another tool, first of all is the question of efficiency and performance, looks very professional; secondly its object library file, there will be executed after each update; test results are separate and there is no single comprehensive evaluation of results; overall, QTP more like a script development and debugging tools, and in test execution, script management, planning in this regard is still inadequate. Usually write their own framework for implementation, interface types have to say here qtp provided, or more, such as: the tool itself provides dom interface also supports dll calls, library calls .net support, support windows api calls, third-party support the dom control calls.
5, SilkTest:
This is relatively a relatively well-known tool, but still did not find out about the same, for the commercial tool because of its large footprint, but also crack and other trouble, the key is to use a small company, so use only over QTP, the other not and will not find out about
Open source tools:
1, the Selenium:
this should most people know, is now most Internet companies use testing framework; selenium only web-UI-level tests, but its advantage is:
A, supports multiple languages written test script, for example: java, python, ruby, perl and so on; also means the subsequent support libraries also a lot of
b, supports multiple browsers, such as: ie, ff, safari, chrome, etc.
c, multi-platform support, such as: windows, linux, MAC, android , iphone etc.
d, support distributed execution, a set of test cases can be distributed to different tester performed simultaneously, but the task can be refined, such as: only linux distribution system for performing liunx use case to be executed next
addition to recording tool support, also said that a simple, web type of test is basically a choice, but support seems not too good for flash
its main points two versions, 1.X version is to drive js automation achieved; 2.X redeveloped webdriver instead js driven, direct calls to the underlying browser interfaces to achieve complete automation of
premises: if the remote or RC, you need to install jre
Download: http://seleniumhq.org/download/
2, EFT easy function testing []:
This package is based on UIAutomatuon of .net3.0 on a dll file, the same package is also part of windows api to achieve mouse and keyboard events. So this can only be called a test library, and supports only windows program, but also supports testing uiautomain supports WPF program.
Prerequisite: installed .net3.0
use: the introduction of the document, uiautomation related dll, writing test cases under the VS environment
3, UIAutomation:
This is the UI automation framework provided by Microsoft, of course, and not just for its original purpose automated test and produce, and its mission is to give more development or application to call the windows UI controls, but can still use automated testing; because ui class operating framework before Microsoft had a similar tool, and this is the redesigned, its purpose is to support the windows family of operating systems compatible with the UI automation [xp, vista, server2003], there is natural support WPF. Of course, the design and automation tools are usually not the same, for example: there is no way to control supports binding on the control object itself, does not provide a dedicated mouse / keyboard events, but provides a specific event monitor and control objects in response to treatment customized approach. The workflow is probably this:
A, first obtain a specific element object, there are a number of ways. Such as: handle, the attribute value
B, the acquisition of the element object model. Mode is at the unique design of this framework, the achievements of its flexibility, unity
c, this mode during the call by specific methods, such as obtaining property values
d, a specific event listener of the specified object, the event is executed specified event handler
4, Robot Framework
Robot Framework is based entirely on a keyword-driven testing framework, ie it can be based on it's certain rules you need to import a test library (for example: it incorporates selenium test libraries, which can be understood as operating web controls the test underlying library), and then based on these test library, you can use HTML, TXT documents and other forms of writing your own keyword (ie those keywords make up your library), and then, and then write test cases (test cases from the test keyword composition) were tested. For example: a simple test of landing: login + password + out three keywords composition may be composed of a keyword landing composition, particle size can be customized keyword itself.
总结
最后才是干货，掌握和了解这么工具为嘛使，不能总是为了好玩，而是为了能在以后的自动化实施过程中用于支持策略的制定；比如新接收了一个测试项目需要进行自动化实施，那么需要考虑哪些点？使用哪个工具，有哪些工具可以作为备选？那么自然就要对常用自动化工具有一个初步的了解，同时对影响自动化过程的其它元素也要有一定的掌握，不过这里可以跳过，这里只是说与工具相关的因素的抉择。大体可以分为如下来考虑：
1、考虑被测试产品的类型，B/S,，C/S，web service，SOAP，SDK或者API；过滤支持某类功能测试的工具
2、考虑是否支持录制，可以录制就相对于说开发效率有较大的提高
3、考虑工具的价格，通常首选开源或免费产品
4、考虑工具扩展性，可能某类工具可以支持现在的业务需求，但日后需求有变化的话，是否有很好的扩展性，支持被测产品的新特性，如flex，flash，wpf等
5、考虑工具的支持性，即后期的升级及版本更新的特性，不要选用即将不再支持的工具
6、考虑工具的广泛性，即这个工具在外部的流行程度，这样以后招人容易，有问题也有较活跃的社区可以求助
7、考虑工具的成熟性，即这个工具不能还在beta版本，需要有一个较稳定的版本，而且估计较长时间内不会有大版本的更迭
8、考虑工具的可开发性，即工具是否提供插件接口，用于可以自定义自己的基础类库和识别机制
9、考虑工具的易用性，即是否有强大的后台支持，如windows、.net、java类库支持
10、考虑工具的适应性，即是否容易被封装，可以很容易被嵌入或引入到其它的框架中，比如：功能框架被引入到执行框架中
11、考虑工具的针对性，即如果有专门的针对性工具可选，自然比那些综合性很强的工具其适用性要高的多了