Forum Discussion
ArtemS
13 years agoSmartBear Alumni (Retired)
Hello,
The production version of TestComplete 8.70 featuring Google Chrome support was officially released. The online help was also updated and now contains information related to specifics of Chrome support.
I'd recommend that you read the Specifics of TestComplete Support for Google Chrome topic as there are certain aspects you should know prior to testing web pages in Google Chrome.
Namely, it gives answers to some of your questions.
In order to avoid recording and playback issues of TestComplete tests, Chrome should be launched with the --disable-hang-monitor command-line switch. See the Disabling Chrome Hang Monitor section in the Preparing Web Browser online topic.
TestComplete Chrome support is implemented as a Chrome extension. And Chrome's security model does not allow any extensions to interact with its internal (about:*, chrome:*) pages or other extensions. Therefore, TestComplete can access only the web pages displayed in Chrome, but not other extensions or browser settings pages.
Each page opened in a Chrome tab is represented as the Page object among children of the main instance of chrome.exe. See the Google Chrome section of the Access to Web Pages online topic. Actions with the tab controls, like opening a new tab, or closing a tab, in all of the supported browsers are interpreted as mouse actions.
You need to switch the project's Tree model option to DOM. In this mode, the hierarchy of the respective Page object corresponds to the DOM structure of the web page.
Thank you for your interest in Chrome support.
The production version of TestComplete 8.70 featuring Google Chrome support was officially released. The online help was also updated and now contains information related to specifics of Chrome support.
I'd recommend that you read the Specifics of TestComplete Support for Google Chrome topic as there are certain aspects you should know prior to testing web pages in Google Chrome.
Namely, it gives answers to some of your questions.
1. When I try to record a script with Chrome browser, it always shows a popup saying "Chrome has not been launch with command-line parameters".
In order to avoid recording and playback issues of TestComplete tests, Chrome should be launched with the --disable-hang-monitor command-line switch. See the Disabling Chrome Hang Monitor section in the Preparing Web Browser online topic.
2. I am specifically looking if TC can handle any extensions/plug-ins. I tried a couple of plug-ins (viz. Reload All Tabs) and it does not recognize the objects.
Is the Chrome support limited to only web-testing ?
3. Can I manipulate the browser settings by script ?
TestComplete Chrome support is implemented as a Chrome extension. And Chrome's security model does not allow any extensions to interact with its internal (about:*, chrome:*) pages or other extensions. Therefore, TestComplete can access only the web pages displayed in Chrome, but not other extensions or browser settings pages.
4. How to handle tabbed browsing scenarios in Chrome ?
Each page opened in a Chrome tab is represented as the Page object among children of the main instance of chrome.exe. See the Google Chrome section of the Access to Web Pages online topic. Actions with the tab controls, like opening a new tab, or closing a tab, in all of the supported browsers are interpreted as mouse actions.
5. How to access DOM of a web-page in Chrome ?
You need to switch the project's Tree model option to DOM. In this mode, the hierarchy of the respective Page object corresponds to the DOM structure of the web page.
Thank you for your interest in Chrome support.