preload

WinRunner to QTP migration notes (3)

Posted by Albert Gareev on Sep 20, 2008
0
Hardware Requirements QTP is much more greedy on resources. Don’t plan to reuse your old WinRunner machines. You’ll have to retire them with WinRunner. Give at least twice as more RAM than recommended by QTP specs, especially for debug and development machines. Changing screen resolution might affect QTP’s GUI recognition. Software Requirements WinRunner had an annoying […] ...

WinRunner to QTP migration notes (2)

Posted by Albert Gareev on Sep 15, 2008
0
Integrity Support of XML, ADO, DotNET, and other services through COM is a greatest advantage of QTP. In WinRunner, there was only an awkward workaround of placing external calls through “dos_system” function and exchanging data through files. Data Model In WinRunner, original data source was text file. Later Excel spreadsheets support was added through “ddt_” […] ...

WinRunner to QTP migration notes (1)

Posted by Albert Gareev on Sep 10, 2008
0
GUI Mapping In general, QTP supports “GUI Map” concept introduced in WinRunner. GUI Maps are called “Object Repositories” and editable in “Object Repository Manager”. “GUI Spy” became “Object Spy”. Two more things about Object Repositories: it’s a real pain to copy/merge GUI objects across checkpoint data included Programming Language C-like TSL used in WinRunner didn’t ...
Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.