TestComplete issues with Chrome 113
Hey, this is a general message about TestComplete issues with Chrome 113 Please note that the current version of our product may experience issues when used with Google Chrome 113. We apologize for any inconvenience this may cause. Our team identified this is Chrome issue and we are working on a permanent fix. We appreciate your patience as we work through this issue. The dev team on our side is already working to solve the problem. We expect the problem to be solved by the middle of next week. More updates will be provided here in this thread. Really appreciate your patience and sorry for inconveniences. Best regards, Pawel Mularczyk Product Manager for TestComplete15KViews6likes139CommentsProblems with TestComplete 15 and Chrome 113
Test Complete Version:15.51.4.7 x64 Chrome Version:113.0.5672.63 Hello, we are having problems running tests after updating Chrome from 112.0.5615.138 to 113.0.5672.63. No more elements are detected in the test and the following error is logged: The window with the handle 0x000000 does not exist. Also no new elements can be mapped in the NameMapping. These are not recognized. The TestExtension in Chrome seems to work, because the test can navigate via URL in the browser. An update to the latest TestComplete version and also a reinstallation of the TestExtension plugin did not solve the problem. Is there any known incompatibility between TestComplete 15.51.4.7 and Chrome 113? Best regards4.1KViews6likes37CommentsTypeError: Sys.WaitBrowser is not a function - Caused by DIsabled Extension
I had something odd happen, and I was able to resolve it, but I am not sure why it occurred. So, I thought I would share it with others who may run across the same issue, since I was not able to find any information in the forums. I restarted my computer, after fully closing out of TestComplete. After I opening TestComplete and my Project file, when I ran a test I had run earlier I got a "TypeError: Sys.WaitBrowser is not a function" dialog as shown here: This particular function has not been changed in years, so it was puzzling why it suddenly stopped working and would not identify my open browser window. Turns out, somehow in the restart of TestComplete or my computer that the Web Module was disabled. After an hour of wasted time, I finally figured out that was the issue. To resolve, go to File --> Install Extensions --> Enable the Web module... This occurred in Version:15.49.6.7 x64633Views4likes2CommentsDo smartbear actually have a support team anymore?
Smartbear actually have a support team these days? Any support ticket that I raise seems to get zero response for weeks other than the initial auto generated confirmation that it's been received. Really frustrating when you have releases coming up that need testing and you can't use the application as their updates have broken things171Views3likes1CommentUpdate Regarding TestComplete Web Issue
Hello, Recently, Chrome and Edge versions 113 caused issues with TestComplete. When this occurred, our development team worked diligently to solve the problem. Google and Microsoft have now released an update to roll back these changes, stabilizing the TestComplete web testing experience. While these changes didn’t stem from TestComplete directly, we do find it of the utmost importance to always provide you with a high performing tool. With additional browser updates planned in the future, we have already taken steps to prevent major outages like this from occurring again. Our teams plan to: Continue to validate beta versions of upcoming browser updates Ensure that breaking issues are always the top priority Release a TestComplete update to ensure upcoming browser versions are not impacted (recently released new version to support Chrome 114 and Edge 114) We’re always committed to delivering the highest quality tools to your team. Thank you for your ongoing patience and continued partnership. Best, The TestComplete Team362Views3likes2CommentsClickitem not working since update to 15.51.4
Since upgrading test complete to 15.51.4 the clickitem action to select options from drop downs is no longer working correctly and is selecting a different value to the one specified in the test. To check its not just how I have created the action I have also recorded the steps and in the test it shows the correct value that I selected but then when you run it you get the tool selecting the wrong option again so testcomplete is obviously having issues with the indexing for the drop downs. To make sure its not our site I have also tried other sites and get the same problem. Has anyone experienced the same issue and know when its likely to be resolved? I raised a support ticket 7 days ago and have had no response at all!!1.2KViews3likes12CommentsSelecting item from drop down list
It seems like some behavior changed when selecting something from a drop down list. The test slowly scrolls through the entire list until it arrives upon the item to select. It definitely didn't use to do this. Was this changed in a recent version? Is there any faster/better way to do this?544Views2likes4CommentsChrome updated, now TC can't find browser
My test won't navigate to the webpage it just says "Waiting for Sys.Browser("chrome")" Anyone else have this problem? Yesterday it worked fine, Today it is broken. Chrome is open on my second screen, and if it wasn't it should open the browser.Solved7.3KViews2likes11CommentsRemove the "improve your test performance" in test log
Hello, After the latest TestComplete update, the testlogs now show the message "Improve your test performance". In those logs TestComplete tells us that we can move our xPath selectors to increase the performance. We are aware of this but do not want to do this. Is there a way to deactivate these messages as we now only get warnings about performance? Kind regards, Luuk1.9KViews2likes7CommentsDetect URL change in TestComplete
I need to assert the contents of a URL as a user navigates through a site. We use Chrome and CANNOT use any other browsers. I initially looked to use events, specifically 'onwebpagedownloaded', to then run some javascript code to execute the content assertions: https://support.smartbear.com/testcomplete/docs/reference/events/onwebpagedownloaded.html However, this is not an option for Chrome: One way to do this would be to inject a script routine for every known page/url change on every keyword test, something I am keen to avoid. Any ideas on what I could try? Custom event? Thanks Dan1.5KViews2likes8Comments