WinQuick is a comprehensive HP WinRunner to QuickTest Pro migration platform that converts over 90% of the WinRunner code to QTP automagically. It is the fastest, most comprehensive and cost effective technology to re-architect and migrate WinRunner based code and artifacts to QTP.

WinQuick is the only HP validated solution with proven customer track record. Please refer to the Features Tab for a complete listing of WinQuick features.

WinQuick is HP PSO’s recommended tool/service offering for WR to QTP migration.

QTP is HP’s next generation functional test automation platform with superior functionality and features. Here is a small set of benefits realized by moving to QTP

• Improved enterprise adaption
• Increased run-time performance (up to 2 times with most of our clients)
• High level of reliability
• Support for emerging technologies such as Mozilla Firefox and .Net
• Zero-configuration keyword support
• Infinitely extendable VBScript base languagesupport

WinQuick is the only tool in the market to be thoroughly validated and approved by HP. Based on an extensive HP/Gallop workshop result, WinQuick meets or exceeds all of HP’s requirements for a WinRunner to QTP migration platform.

WinQuick is offered as a service by Gallop Technologies and its partner channel. HP Professional Services Organization (HP PSO) is one of its key partner channel. WinQuick implementation team uses the tool to speed up the migration process substantially and pass on the benefit to the customer directly.

Customer is charged only for the manual part of the work. This model is very prudent as the customer does not have to go through the learning curve of the tool/migration intricacies and does not have to suffer the business distraction. We offer onsite and offsite service models.

Gallop’s migration service employs WinQuick platform to automatically migrate over 90% of the code. Here are a few reasons why WinQuick solution is superior to manual

• Speed: As 90% of the code is automatically converted, only 10% of code migration needs to be handled manually. Less than 9 times the time it takes to migrate everything manually.

  There is also an element of debugging involved in manual or WinQuick based migrations. WinQuick leaves code level comments to readily identify problem areas, so the debugging is much faster and smoother. Overall, WinQuick saves over 80% of the effort in an end-to-end migration.

• Reliability: Gallop’s team has extensive expertise and processes put in place exclusively to solve migration related problems. Our solutions are time tested and reliable.

• Cost: WinQuick based migrations save over 80% of the effort involved otherwise in a manual migration. Complete project is implemented in less than 20% of the effort, so the total cost of implementation is proportionately lower by a factor of 3 to 6 times compared to manual migration. WinQuick is used as part of the Professional Services engagement.

• Business Distraction: Minimal to Zero. Migration happens so fast that your regular Automation development schedules don’t need to take a hit. For your team, it is business as usual while the migration is happening.

No, WinQuick is offered as a service to provide a complete end-to-end solution and is not licensed as a tool. Effort spent in training on the tool and learning the intricacies of going from WinRunner to QTP is not a whole lot relevant after the migration is completed and the customer does not have to go through it.

Gallop employs WinQuick as part of the migration engagement to deliver a complete working QTP setup, in the most cost efficient manner with no business distraction to your team. Over 80% of the migration happens automatically by the tool and you only pay for the manual component of the work.

Trial version is not offered at this point. However, a customized demo is available upon request from our website or by calling 1-469-223-9733

Absolutely! Gallop can perform a pilot in your own environment with your own source code. Please call us for details

Yes, please call us for references. Please click here for some success stories with our clients.

Typical migration process starts with a client interview to understand the setup and architecture. Gallop’s team understands the requirement, analyzes the code and offers a proposal with the cost and timeline. Gallop’s team can work in onsite and offsite models. A fully functional QTP source code is delivered with a customized sign-off presentation to your team. Refer to the WinQuick data sheet for further insight into this process.

At the end of the migration implementation, Gallop’s team conducts a customized sign-off session with the client’s team.

As in most cases, the client’s team is venturing into QTP for the first time, this session explains the intricacies involved in using QTP on a day to day basis. Especially for the teams with expertise in WinRunner, the sign-off also touches upon aspects that you should avoid in QTP environment. A good design decision in WinRunner is not necessarily the best in QTP.

This presentation is prepared exclusively for the client, with tips developed based on your usage model and code base. It also helps the teams be self sufficient and imparts ability to maintain and enhance the scripts as you move forward.

Part of the process also includes a high level code walk through of the new QTP based code.

Please note that the sign-off presentation is not a substitute to a formal QTP training.

Yes, Gallop also offers complete offsite service model to the customers. We also offer 24 hour development work cycles to substantially cut down on the migration duration.

No, Gallop works onsite or offsite models as convenient to you. It is not required to ship/ftp the code to Gallop. Our team can implement the solution completely on your site or if working offsite, we will establish a secure remote connectivity.

Yes, Gallop’s WinQuick migration service is available across the globe through our partner channel. Gallop also services all of HP PSO’s clients through the partner channel. Please talk to us for details about your specific location and need.

Though it might sound like an attractive option, there are several drawbacks with this approach. All the perceived benefits of coding from scratch can be easily realized through a properly executed migration, that too at a much lower investment and time. Please refer to our white paper, “Moving from WinRunner to QTP – Re-architect as you migrate"

Yes, WinQuick can handle complex frameworks and migrate appropriately to QTP. WinQuick migration process is not rigid. It allows for flexibility to tweak the architectures so the final design is compatible with QTP. Gallop's consultants have the expertise to guide you through the process.

Gallop can help evaluate your current setup to design an efficient migration path. Please call us.

Gallop Technologies can help you setup QTP framework from scratch and provide consulting services to get a jump start with your Automation initiatives.

No, WinQuick based migration will generate functionally equivalent code that is completely native to QTP, with no traces of WinRunner origins.

WinQuick supports all the application user interfaces that WinRunner and QTP support together. These include Java, Web, VB, ActiveX, TE, Oracle, Windows, PowerBuilder, Delphi and others.

WinQuick has seamless connectivity with your QC server. Source scripts and GUI files stored in QC can be migrated either to the file system or directly to a folder/project of your choice on the Quality Center.

All existing versions of WinRunner and QTP are supported. However, Gallop strongly recommends migrating to the latest version of QTP

WinQuick converts over 85 to 95% of the code auto-magically. Rest of the cleanup along with necessary debugging is handled by Gallop’s consultants, so the client gets the final working version of the code base as a deliverable.

Same as the minimum requirements for installing QTP. If you can install QTP on the machine, so can WinQuick be.

Yes. WinQuick is based on a Knowledge Driven Framework that allows for human expertise to work in conjunction with the tool's speed and quality. Re-architecting is an integral part of all the migration implementations.

The final output of the process is a completely functional QTP setup. This output is fully native to QTP, with no traces of WinRunner origin. QTP code will be exactly the way it will be if you write from scratch. Guaranteed!

Absolutely! Resulting QTP code is native in all aspects.

Yes, WinQuick uses QTP’s internal API to generate binary artifacts that includes check points. Result of migrating a check point in WinRunner is completely native to QTP, in its own proprietary binary format.

Absolutely. All the regular expressions in the code and GUI files are converted to their QTP equivalent. Physical descriptions in WinRunner code are converted either into Description objects or to in-line object descriptions.

Yes, all the test level parameters in WinRunner translate to QTP’s action level parameters. It is possible to tweak this default behavior.

All the add-ins necessary to run WinRunner and their counter parts in QTP are required to successfully execute the scripts in QTP. Please refer to QTP’s documentation for add-in information relevant to your environment.

Most of the missing features in VBScript language are simulated through equivalent data structures and idioms. There may be some hard limitations that need manual intervention. But this is very rare.

WinQuick fills the missing functional differences between WinRunner and QTP through its supporting function libraries. These libraries are implemented in VBScript and are delivered to the client as part of the service.

All the CSO libraries are migrated to VBScript. Individual functions may translate to one of WinQuick’s support library functions or a native VBScript/QTP function.

Yes, all the external functions utilizing external dll files are directly migrated to QTP.

Yes, all the library functions are converted to equivalent VBScript functions.

Comments are retained as-is in the resulting QTP code.

Yes, WinQuick’s advanced Hierarchy Sniffer module in conjunction with the extensive heuristics, sort out the hierarchy differences. QTP’s multi level hierarchy is reflected in the final output.

WinQuick works on your existing code base as-is. No special preparation or marinating is required.

WinQuick generates in-line code comments at the exact point where there was an issue with automatic translation. It is easy to browse through the resulting code and find problem areas just by searching for a pre-defined pattern. High level view of problem scripts can be obtained using WinQuick’s reports.

No such limitations. WinRunner source code is handled as is and no changes are required for migration.

Generated VBScript is accurately indented even if the original WinRunner code is not.

WinQuick generates various reports during the process of migration. In addition to providing statistical data, these reports are of a great help to understand the migration activity from a high level and a good source to learn QTP platform.