Often we are faced with an issue when QTP cannot identify the objects in a web page.
So, listed below are some of the things we should try (in no particular order). This is not an exhaustive list (yet), but this could give some pointers or options that you may not have tried.
Bear in mind that Uninstall & Re-install should always be the last option - no matter how tempting it is ;-)
• Check the compatibility of QTP with OS and IE.
• IE Browser > Tools > Internet Options > Disable the "Enable Tabbed Browsing" checkbox.
This worked for me on Windows 7 with IE 8 and QTP 11 - Jun2012
• IE Browser > Tools > Internet Options > Disable the "Enable Protected Mode" checkbox. If Protected Mode is required to be set as ON, then a QTP Patch QTPWEB_00073 is needed.
• Sometimes QTP identifies objects on the main browser page but not on the child page. This may happen when web pages have Web 2.0 elements embedded in them. These Web 2.0 apps are not based on new technology but instead on a set of cumulative toolkits or frameworks, like AJAX, Dojo, Yahoo User Interface (YUI) and GWT. In such cases, we have to enable/install Web 2.0 toolkit add-ins in QTP. Refer the following links in such a case:
• UAC (User Account Control) has to be disabled on Vista and for Windows7 has to be set to "Never Notify"
• If QTP's BHOManager Addon is disabled in IE, even this can cause issues, and has to be Enabled.
To enable it go to IE > Tools > Addons > BHOManager Class - Enable
• IE Browser > Tools > Internet Options > Advanced > Browsing > Enable Third Party Browser Extensions
• For FireFox, ensure that QTP Plugin is available in the Extensions section of the Addons in Fox
• Ensure that the Browser is running in 32-bit mode, even if the machine is 64-bit because QTP is a 32-bit app. To ensure this during run-time, pass the complete path for the browser (the one with (x86)) via SystemUtil.Run
So, listed below are some of the things we should try (in no particular order). This is not an exhaustive list (yet), but this could give some pointers or options that you may not have tried.
Bear in mind that Uninstall & Re-install should always be the last option - no matter how tempting it is ;-)
• Check the compatibility of QTP with OS and IE.
• IE Browser > Tools > Internet Options > Disable the "Enable Tabbed Browsing" checkbox.
This worked for me on Windows 7 with IE 8 and QTP 11 - Jun2012
• IE Browser > Tools > Internet Options > Disable the "Enable Protected Mode" checkbox. If Protected Mode is required to be set as ON, then a QTP Patch QTPWEB_00073 is needed.
• Sometimes QTP identifies objects on the main browser page but not on the child page. This may happen when web pages have Web 2.0 elements embedded in them. These Web 2.0 apps are not based on new technology but instead on a set of cumulative toolkits or frameworks, like AJAX, Dojo, Yahoo User Interface (YUI) and GWT. In such cases, we have to enable/install Web 2.0 toolkit add-ins in QTP. Refer the following links in such a case:
- This is a good demo site to check if Dojo toolkit add-in is properly installed and getting recognized by QTP or not - http://demos.dojotoolkit.org/demos/form/
- In such situations we should also explore the option of Extensibility Accelerator Refer this link http://support.openview.hp.com/selfsolve/document/KM998707 and this blog post http://www.quicktest.pro/2012/11/dojo-automation-with-quicktest.html
• UAC (User Account Control) has to be disabled on Vista and for Windows7 has to be set to "Never Notify"
• If QTP's BHOManager Addon is disabled in IE, even this can cause issues, and has to be Enabled.
To enable it go to IE > Tools > Addons > BHOManager Class - Enable
• IE Browser > Tools > Internet Options > Advanced > Browsing > Enable Third Party Browser Extensions
• For FireFox, ensure that QTP Plugin is available in the Extensions section of the Addons in Fox
• Ensure that the Browser is running in 32-bit mode, even if the machine is 64-bit because QTP is a 32-bit app. To ensure this during run-time, pass the complete path for the browser (the one with (x86)) via SystemUtil.Run
No comments:
Post a Comment