sgarcia
Contributor
Joined 16 years ago
User Profile
User Widgets
Contributions
Re: TestComplete not recognizing test extension after update to version 15.59
So I found a solution to get it to work, but now I'm having issues with the ClickItem method. But at least the browsers are recognized now. I'm currently working with support for the ClickItem issue. The last section of this doc helped me find the solution - https://support.smartbear.com/testexecute/docs/working-with/extending/messages/chrome-extension-is-not-installed.html The most important part was to add the Test Extension ID for each browser to the tcCrHost.json file. "C:\Program Files (x86)\Common Files\SmartBear\tcCrExtension\<extension id folder>" The interesting thing was I had two extension Id folders. I had to look in the registry to make sure I was updating the correct file by checking the path it was referring to. For Chrome: "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\TestComplete12.Smartbear.Chrome.Extension" Look for Microsoft\Edge in the same path as above to find that one. They say you only need one of them but if you have it in both I'd recommend checking both just to be sure. The key value will show the path it is pointing to, to find the extension json file. Example json: Hope this helps anyone dealing with this issue.Re: Clickitem not working since update to 15.51.4
I'm having the same issues. The ClickItem method is so flaky now. I have managed to find workarounds for the ones that won't work, but it's far from ideal. And as has been mentioned here, I shouldn't be wasting my time revisiting my tests to fix something that wasn't broken. I was going to push management to look into adding the API tool, but I'm hesitant to do this with all of the issues we're dealing with here.Re: Here we go again - Now EDGE doesn't work
So I read in the post for Chrome 113 that we will not get an update to the Edge issue until early next week. I can tell you we're not happy with this taking so long. We're going to have to release without running automation on our release builds. We only test on Edge because it is the recommended browser for our company. We have a very targeted customer base so cross browser testing is low priority right now. Obviously this issue has shut us down from any automation activity on our web team and it puts our release at higher risk because we don't have the resources to fully cover what automation covers. I'm not sure what the impact will be with decisions on the automation tool we choose to use going forward. TestComplete was chosen because we have an in-house java application that we test as well as the web apps and TestComplete seemed like the perfect solution. In my opinion and, as I've read, others as well, this should've never happened. I sincerely hope there are changes being made to ensure this never happens again.
