Testing a chrome extension with TestComplete
Hello, I'm trying to use TestComplete to test a Chrome extension that is currently in development. When I click on the icon it will display a popup like so: As far as I know there is no...
Forum Discussion
I tried FindChildByXPath but no luck...
I'm noticed that the SmartBear extension doesn't inject the hidden nodes that it normally does in other pages.
When I right click on the extension while my chrome extension page is open I see:
I think this is a chrome limitation. It doesn't allow us to inject into it's internal pages.
For security considerations Chrome refuses all extensions to inject code into its internal pages (about:*, chrome:*). Because of that, internal pages, like the new tab page, the extension manager, the download manager, the history page and so on, are not accessible to TestComplete.
Source: https://support.smartbear.com/testcomplete/docs/app-testing/web/general/considerations.html
I may need to switch to selenium for this one... It doesn't have this limitation.
Hi thePantz,
Because of the Chrome specifics, TestComplete can only get access to the viewport of the browser - the actual pages you visit. That's why currently there is no way to recognize elements in extension popups. As far as I know, the same goes for Selenium - it only allows you to work with the popup if you open it in Chrome as an individual HTML page, but TestComplete has no issues with this scenario as well.
As a workaround, I can suggest using the image-based approach - finding elements by their images. You can also use Optical Character Recognition to obtain elements by their text (please note that it requires a separate license for the TC IQ add-on).
JuliaBernikova As I explained in my original post, TestComplete cannot locate the elements when you open the popup on an indivudual page. I did not have difficulties when using Selenium so I have gone that route. I will not pay for an Image Recognition module when I can get more reliable results from Selenium.
I should have put it differently: by an individual HTML page, I meant opening HTML locally as a file, not via chrome-extension://. It's good to know that Selenium supports this mode though - the next TestComplete version will introduce a cross-platform web testing feature that allows running tests using Selenium Grid. So, our product team will check if we can make TestComplete work with chrome-extension:// pages too.
