CristianE
Occasional Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Navigate to page taking a long time
I don't know if I understood your scenario. But here are some suggestions: - after using the navigate method, you can add a new line to wait for the new popup window, or a child element, or a property from the newly loaded page - maybe the page is hidden in the background but the automation-driver (the one that sees the Tree elements) can see the elements and 'bypass' your assertion'. In this case, try to find an element from your page after is loaded and use WaitProperty method on it, for VisibleOnScreen property. - try another way to assert your step (not based on navigate result method)ClickItem selecting wrong value / Chrome 115 Support
Hello, Starting direct with the question: When will the next version of TestComplete be released (that will support Chrome 115.0.x)? My problem below: Recently, the Chrome browser from my environments were updated to the latest version (115.0.x) and I encountered some issue when selecting values from a dropdown using the ClickItem method (the wrong value is selected, even if I use the name or the index). Firstly, I updated the TC to latest version (as I saw in the change logs, an issue related to ClickItem was resolved in the latest release), but it didn't solve my problem. It even behaves worse than before (there were some 'extra actions' in the ClickItem process) With TC 15.50 and Chrome 111, the ClickItem method is working fine. Attached some videos with before update, and now with Chrome 115. Is there any chance that the next version of TestComplete will solve my problem? I would like to know when the new version of TC is scheduled for release, to know if it's better to wait a couple of days/weeks for it or if I have to downgrade Chrome and block the updates on all my environments. Thanks!Re: DCOM Issue: TestComplete with HP ALM on Windows Server 2019
Hi Marsha_R, Before writing, I also looked at the instructions and tried to troubleshoot the problem. In the end, I found a solution that worked for me: In TestExecute Options I had to disable the Enable support for testing Windows Store applications. On Windows Server 2016, it works even if I have the option enabled. Hope this will also work for others Regards, Cristian
