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.
Selecting an item from List box based on the name using
Hello, I am fairly new to Test Complete and just learning, can someone show me using my example I provided here on selecting the specific item (see screenshot) from the web List box that I show highlighted in the Element screen ? What is the best method to use to search and select (click) the item as the current item in the menu? I would also like once I get the basic to search the item in the list box that I have stored in the patient variable where I would get from another screen (another script test/keyword test) so I can look for it. Here are two methods I found;page.NativeWebObject.FindandaqObject.CheckProperty but not sure which is best to use in this case.If you know something better and please if you can provide it with this example. I would also like once I get the basic to search the item in the list box, I would like to reuse the patient variable where I would get from another screen (another script test/keyword test) and apply it to the search item on the list. Can someone show me how to apply it in JavaScript using the sample I provided? ELEMENT SCREEN: SPY TOOL:
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 1
Running tests by tag name in specific order
Hello, I will be running my suite of tests in a CI/CD pipeline (Jenkins) but I realized from the documentation that running tests by tag name (following the CLI commands) does not guarantee the tests will be run in a certain order. (Note:The tests that match the specified tag will be run in an arbitrary order.) While trying to find a workaround to this inconvenience, I realized that it does indeed follow a specific order. The order is given by how the test files are sorted in the file script.tcscript. So, for whoever needs to run their tests using tag names, and also wants to run a "pre-step test" or something like that, all you have to do is open that file on any text editor, and move the row where your test file is, up to the place first place, or at whichever place you want it to be executed. Example: # Assuming all tests have the tag "@Smoke" <folder name="MaiGroup"> <folder name="Group1"> <child name="TestMethod1" key="ZZZZ-YYYYY-VVVVV}" path="File1.js" /> <child name="TestMethod2" key="ZZZZ-YYYYY-VVVVV}" path="File2.js" /> <child name="TestMethod3" key="ZZZZ-YYYYY-VVVVV}" path="File3.js" /> </folder> </folder> # Test run for the @Smoke tag will look like: TestMethod1 TestMethod2 TestMethod3 ----------------------------------------------------------- # Now, if we want to run TestMethod3 first, all we have to do is open the script.tcscript file and move the TestMethod3 to the first place: <folder name="MaiGroup"> <folder name="Group1"> <child name="TestMethod3" key="ZZZZ-YYYYY-VVVVV}" path="File3.js" /> <child name="TestMethod1" key="ZZZZ-YYYYY-VVVVV}" path="File1.js" /> <child name="TestMethod2" key="ZZZZ-YYYYY-VVVVV}" path="File2.js" /> </folder> </folder> # And now, the test run for the @Smoke tag will look like: TestMethod3 TestMethod1 TestMethod2 ----------------------------------------------------------- Hope this helps someone, and maybe the TestComplete team can now update the documentation. Regards.
Error when executing tests on my primary monitor - "The tested window (or control) has been deleted"
Hello, TestComplete Version:15.58.9.7 Chrome Version:119.0.6045.160 When executing the script below on my primary monitor, I get error "The tested window (or control) has been deleted". When executing on my secondary monitor, it works just fine. function PrimaryMonitorTest() { Browsers.Item('chrome').Run('https://www.google.com'); let searchBar = Aliases.browser.Page("*").FindElement("//textarea[@title='Search']"); searchBar.Click(); } When the script fails, I also notice the browser Page object is not present in the Object Browser: Anyone else experiencing similar issues in the latest TC release (15.58.9.7) ?
