ContributionsMost RecentMost LikesSolutionsRe: WaitForm() method? Hi, As it was suggested by Marsha, check https://support.smartbear.com/testcomplete/docs/app-objects/common-tasks/waiting-process-or-window-activation.html help topic. Maybe something like WaitJavaFXObject() will work for you. Or follow the suggestion by rraghvani Re: Is anyone noticing issues with the Community forum? Anyway, broken links to previous topics is one of the major issues as for me. (Not mentioning worse user experience (convenience for the end-user) when compared to previous forum.) So I am joining nastester Re: The OCR service failed to process the document. Hi Simona, I believe that you are talking about OCR functionality provided by the Intelligent Quality extension in TestComplete, right? If the above is correct, then ocr.api.dev.smartbear.com is just a proxy that forwards data to Google OCR and I think that this is something that should be reported directly to Support via the https://support.smartbear.com/testcomplete/message/ form. Re: Mobile - Swipe to an element Hi, As the initial post mentions FindElementByXpath(), it is my guess that the talk is about web page rendered on mobile. If my guess is correct, than ScrollIntoView() must work as it seems to be supported by all browsers. The case might be that due to lazy-loading of page, sought-for element might not exist in page DOM until this element is not rendered (not requested from the server). If this is the case, then screen-by-screen scroll with the check whether or not the sought-for element appeared in page DOM seems to be the only reliable way of implementation that I know. Re: Accessing parent objects attributes Hi, > For all other attribute accesses, this code works but the "attributes" property doens't exist on the Parent Are you saying that for 'item' element statement, for example, item.Parent.FullName returns some value and only item.Parent.attributes evaluates to null? If the above is true, then this might be a problem in TestComplete. If item.Parent contains only native html properties or evaluates to null, then it might be a case that the span you are looking for was excluded from objects hierarchy in TestComplete (https://support.smartbear.com/testcomplete/docs/app-testing/web/general/object-identification/tree-model-elements.html) and thus FindElement() returned native DOM element but not its TestComplete wrapper (as this happens usually). As a kind of workaround I may suggest: a) either try to use native DOM methods to get item's parent; or b) try to search for the li element that has required child span element and work with found li element. Consider https://copyprogramming.com/howto/how-select-a-parent-node-with-xpath as an example of possible search. Hope this will help. Re: Chromium Embedded Content Detected Hi, Also https://support.smartbear.com/testcomplete/docs/app-testing/web/supported-browsers/index.html for what browsers are supported with current TC version. And you may check https://support.smartbear.com/testcomplete/docs/general-info/version-history/index.html for browsers supported by given previous version of TC. Re: Chromium Embedded Framework Hi, Any more details please about your tested application (WPF or not), CEF version, actual issue? Re: Not able to start chrome in headless Hi, I did not use cloud testing in local mode (this is what you are doing in fact), but as per my memory, you need to do the following: -- Install and setup local Appium; -- Add correct Chrome WebDriver to local Appium; -- Add parameters to capabilities to specify that Chrome is going to be used in headless mode. Check relevant TC documentation topics for more details and to check that my memory does not fail ;) Re: Chromium Embedded Content Detected Hi, As it was already answered by Marsha, TC 15.54 does not support Chrome 120. (Chrome 120 seems to be not supported at all yet. :( ) There was a message on the forum that TC 15.59 works for Edge 120, so you may give it a try if use of Chrome is not mandatory. However, TC 15.59 seems still to have a set of regression problems, so I wouldn't recommend blind update to it, but first give it a try on some non-production test environment. If use of Chrome is mandatory for your testing and you do not have extensive set of tests yet, you may consider cloud testing with BitBar, though this will require BitBar license (free license exists, so you can check if BitBar is something that might work for you). Check relevant documentation sections for more details. Consider this if you decide to consider cloud approach: -- You will need to switch identification of web elements in your test project from 'classic' to XPath/CSS mode - this is a critical step and decision as the 'classic' test code and 'cloud' one are incompatible if relevant test code design is not implemented from the very beginning of the given test project; -- Record/code test using, say Edge, locally as usual; -- Adopt test code for remote cloud execution; -- Execute test in the cloud using Chrome/any other browser provided by BitBar. Re: White popup on the first TestExecute run Hi Simona, > Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE) BTW, just recollected that I had an error with this code for myself. I am not sure if there was this white window, but the root cause was a licensing issue. Here is a quote to Support: To reproduce the problem, I just started TestExecute on some other box so that the only available license is consumed and started the pipeline task. Pipeline fails on Visual Studio Test step which, as per my understanding, internally consumes the functionality provided by TestComplete Test Adapter. Visual Studio Test step fails with the "Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))" message. Pipeline executes without any problem as soon as TestExecute on another box is closed and the license becomes available. In addition: Actually, Silent.log file confirms my statement with this message: "Tried to open the error dialog. Message: All the product instances allowed by your license key are already in use (running).." The strange thing in your case is that it occurs on the first run only, but nevertheless the overall problem looks to me like something related to license access... Try to check silent.log for TE on VM to see if it contains some useful information.