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 TestComplete
TypeError: 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 x64Update 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 TeamIn Headless Testing some of the priority values are different compared to regular GUI Testing
TestComplete Object SPY - The difference will be seen in properties and property values for same object in Local and Remote Browser(Headless Testing). We have a project which we are trying to convert into Headless Testing Mode in local computer by using edge webdriver. But scripts are failing due to difference in Property and Property Values in remote browser when compared with regular GUI testing. Example1 : childcount is 0 in Headless Childcount is 11 in Regular GUI Testing Example2 : Intertext, OuterText, and textcontent like this many properties are not available in Headless Mode. However all these properties are available in regular GUI testing.
Qt6-Objects are not recognized
Hello, After Qt6.5-Upgrade of the software any Qt-Objects are not recognized by TestComplete (15.54, neuest at this moment) any more. The TestComplete Tests worked with the software with Qt6.2 or Qt5 without problem. Is there any way to make it work, other than waiting for TestComplete update? We are also wondering if we can find the Qt6.5(LTS)-Support plan somewhere. Thank you.
Enabling Default Print Dialog in MS Edge \ Chrome
I am just posting this info for others to be able to be able to use. As I have been automating lately against the MS Edge and Chrome browser, when it comes to handling the print window that the browsers displays, ObjectSpy cannot work with it easily or at all?. I just needed a Print window to deal with easily, so I looked up how to use the System Default Print Dialog like IE presented. I have provided the the Windows Registry settings for both MS Edge and Chrome: Enable Default Print Dialog in MS Edge: ----------- \HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge Add UseSystemPrintDialog - REG_DWORD (32-bit) Value with value 1 Enable Default Print Dialog in Chrome: ----------- \HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome. Add DisablePrintPreview - REG_DWORD (32-bit) with value 1Crossbrowser Object mapping: Object correctly detected in one browser not detected in the second
Hi all, just a post about something I've noticed when working with mapped object between Firefox and Chrome. I was having issues getting some mapped objects to be detected in the second browser having mapped successfully in the first. In all cases I was using some text property, e.e. innerText, to identify the object and there appeared to be no difference in the text property between the two browsers, when I examinded using object spy etc., and hence no obvious reason why the mapped object could not be found by testcomplete in the second browser What I have discovered after trial and error is that there appear to be unseen/invisible characters within the text property itself and that this is why testcomplete cannot identify the object in the second browser. Workaround I have found is to delete the extra invisible characters and also to wildcard the beginning and end of the text string. In namemapping editor select the object and open the edit object properties dialog, select the property and click the edit icon, object property edit dialog is presented. Click at the start of the string and use the "Delete" button on keyboard to remove any unseeen characters that may be occurring at the start of the string. (presence of unseen chars at start of a string is noticeable in that the cursor does not move even though the key has been pressed, until all unseen chars have been deleted at which point the string characters will then start to be deleted) Click at the end of the string to move the cursor and use both the Delete and Backspace keys to remove any potential unseen chars at the end of the string. (presence of unseen chars at end of a string is most noticeable when using Backspace, the cursor does not move even though the key has been pressed, until all unseen chars have been deleted at which point the text string characters will start to be deleted) e.g. I have a dialog with titie bar text Add task, which was not being detected by testcomplete in the second browser. I edited the innerText property value, performed the deletion and saved the changes. The dialog was then detected in the second browser. Ocassionally deletion of the unseen/invisible chars does not work and the object still cannot be found by testcomplete in the second browser. In these cases I also add wildcards to the beginning and end of the text string, after performing the deletion steps, and the mapped object is then correctly detected in the second broswer. For example: *Addtask* Hope this is of help to someone out there trying to figure out why your mapped objects are not being detected between different browsers. And if anyone can shed some light on what exactly is happening to create the unseen/invisible characters in the mapped object property I'd love to hear about it. Regards Tom.Issue with 'Keys' Operation
I just updated to Chrome version 140.xx and the keys operation has stopped working like it did before. When trying to enter text into a text box it targets the tab groups button in the upper left hand corner of the browser, beneath the 'go back' button. The test seems to work if I remap the object and replace it with the 'Set Text' operation. I am running on the patched version of TestComplete 15.76 and I am waiting to upgrade to the latest release. I am wondering if anyone else is having this issue with 15.77? Thanks for your time!Unable to identify WPF object in Test complete release version 15.65.12
Unable to identify WPF object in Test complete release version 15.65.12 but its working as expected in 15.64.3 I have a test written in test complete for WPF application. Post installation of updated test complete version the wpf object is not getting identified correctly Its showing as window instead of WPF object in version 15.65.12. But same is working as expected in 15.64.3 Am I missing any settings in the updated version for the WPF application will appreciate help in this
