Browse Prior Art Database

More flexible and smarter enabler for automation tool Disclosure Number: IPCOM000199292D
Publication Date: 2010-Aug-30
Document File: 2 page(s) / 58K

Publishing Venue

The Prior Art Database


With information industry development, more and more softwares are developed for improving human efficiency and build smarter planet. These softwares' quality are one of the essential factors to impact reality's productivity. How to ensure software's high quality with less workload and less labour? The exact answer is to use automation in testing domain. Talk about automation, we definitly have to mention some well-known and powerful automation too, which can provide many good benefits, and it is also widely used in testing domain. However, automation tool has a limitation, the automation projects developed by auto tool are too dependent on automation tool, that means automation can't run without automation tool, automation is too dependent on automation tool. So under this background, this article will try to solve this limitation by creating an enabler in automation tool.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

More flexible and smarter enabler for automation tool

Currently, many test teams have addressed these problems by abandoning the record-playback model and writing test cases manually instead. The success of this approach has varied, depending on the model the automation tool uses for object recognition. In some tools, the object recognition algorithms are complex and inaccessible, making updates to the scripts extremely tedious and in some cases impossible. In other tools, the object recognition algorithms are exposed and simple,

which makes updates much more manageable

, but which also has the unfortunate side effect of making object recognition less reliable.

In contrast to these popular auto tools, some automation tool's object recognition algorithms are both complex (making object recognition quite robust) and accessible (via the object map). This unique object recognition scheme, coupled with tool's support of Javaas a scripting language, has enabled -- for the first time -- a truly object-oriented (OO) approach to writing GUI automation. This approach enables you to generate scripts early in the development process, based on project requirements or developer specifications, instead of waiting until an application is complete and then using record-playback. Additionally, tool' s OO design, and the reusable code that it promotes, makes it easy for you to update object recognition properties to reflect changes in the evolving application without touching other parts of the code. Using auto tools, then, you are able to write flexible, reusable Java code that is both robust and easy to maintain.

Some popular auto tools are well-known automation tools with many good benefits such as Automation testing, Object pickup, more framework. However,

when we enjoy the benefit from auto tool


when we more and more apply auto tool in o...