![]() Read more about how script debugging works: How Does Script Debugging Work Internally? ![]() While working on a client’s lab computer, it is extremely unusual to work in an environment where both QTP and VS is installed. The screenshot examples below show the object properties and methods for a QTP WebList objectĮnhanced Debugging w/ PDM.dll (9.1) – VariablesĮnhanced Debugging w/ PDM.dll (9.1) – Watch (Methods Expanded)Įnhanced Debugging w/ PDM.dll (9.1) – Watch (.Object Expanded)Īfter further research, I found this is the result of an updated PDM.dll version that is installed and registered with VS 2008/2010. Utilizing the Watch tab of the Debug Viewer provides even more detailed information, including the object’s available properties and methods. Object types were also explicitly defined. ![]() Limited Debugging w/ PDM.dll () – VariablesĪfter installing Visual Studio 2008 and Visual Studio 2010, I noticed that the Debug Viewer pane ( Watch and Variables tabs) contained additional information (“”) in the place of the usual “” values. Objects, like Object Repository objects and VBScript objects, do not have their properties and methods exposed. An automation engineer does not have the ability to view the properties/methods of variables/objects in their full extent. Out of the box, QTP provides limited VBScript debugging capabilities. Microsoft Script Debugger ships with an archaic version () of Process Debug Manager (PDM). Without the debugging engine, all of the QTP debug features are unavailable. ![]() QTP 11 (and versions 9-10) installs Microsoft Script Debugger to provide the debugging features in QuickTest Pro scripts. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |