ContributionsMost RecentMost LikesSolutionsRe: Object showing Visible in Object Browser when set as Invisible in application I'm not sure what Neutrino Framework is, and it's not supported by TestComplete, see Supported Development Tools. I'm guessing, under the hood, the Neutrino Framework is changing the correct property values. However, TestComplete is most likely not able to see this and is only seeing "above the hood". Are there any other properties, that change their values based on the state of your icon? If not, then just verify the Enabled property value. Re: Classname property is missing Is this for Web or Desktop application? Can you provide a screenshot of the issue as well please? Re: Save Log Use Log.SaveToDisk method. Re: Parallel testing for web tests See https://support.smartbear.com/testcomplete/docs/testing-with/running/parallel.html and also take note of the following, Several functional tests cannot share a user session, therefore, only a single test can run on the workstation It's possible to switch between tabs in Edge to test various web pages, but you won't be able to test exactly at the same time. This is deprecated https://support.smartbear.com/testcomplete/docs/testing-with/deprecated/distributed/basic-concepts.html Re: Don't update Chome to v140 It's the same with me, as I work in a corporate environment and our equipment is maintained by the IT department, updates are done automatically which I have no control of. Re: Open log downloaded from AzureDevOps release pipeline It's a Windows security feature called the "Mark of the Web" (MOTW). It flags files downloaded from the internet (or other untrusted zones like network shares) by adding metadata, causing Windows to treat them as potentially unsafe. Usually it's disabled by the IT Team, if you're in a managed corporate environment. However, they can configure Group Policy to allow exceptions. Re: TestComplete multiple inquiries / issues To add, Scroll Bars may not expose properties such as X, Y coordinates. However, there may be methods you can invoke to mimic a scroll. Use the Object Browser to see what Methods are exposed for your Scroll Bar. Alternatively, you could perform a page up/down keystroke. TestComplete command line example, "C:\Program Files (x86)\SmartBear\TestComplete 15\x64\Bin\TestComplete.exe" "N:\Automation\Elink\ELink Automation\ELinkServer1\ELink.pjs" /r /e /p:"ELink" If you are testing a 64-bit application, then use x64 path for TestComplete. Use the appropriate project name for parameter /p:"ELink" Re: TestComplete multiple inquiries / issues Thanks for clarifying; I understand now. It is a bug that was noticed in the post .Click action doesn't release Ctrl | SmartBear Community when using the skCtrl key. It could be related to the bug fix they implemented, which also affects skShift. skCtrl key not functioning as expected. Resolved a bug that prevented simulated skCtrl key presses from selecting multiple items. The fix restores correct multi-select behavior in 32-bit environments. Re: Read text from tooltip on hover Good work 👍 Just remember that the Object Browser is your friend, if Object Spy doesn't work for you. It's also worth familiarising with the browsers' DevTools, and seeing how TestComplete goes about showing the various properties based on the HTML code. Re: Don't update Chome to v140 End-users need to understand, that TestComplete typically supports Chrome and Edge versions that are 2–3 versions behind the latest release due to the following reasons: Browser internals change frequently - each browser update can introduce changes to the DOM, JavaScript engine, and debugging APIs, which may break existing functionality. Stability and compatibility testing - SmartBear needs time to test and validate each new version to ensure stable integration and prevent test failures. Enterprise alignment - many enterprise environments lock browser versions for consistency, so supporting slightly older versions aligns with real-world usage. Reliability over recency - prioritising stability helps avoid flaky tests and ensures a predictable testing environment. Changing APIs (CDP) - Chrome and Edge use the Chromium DevTools Protocol, which evolves frequently. TestComplete must adapt its internal mechanisms accordingly before offering support. In short, this delay is intentional to ensure reliability and consistency across different environments. Many organisations use locked or controlled browser versions in their environments to ensure consistency and compliance. TestComplete’s support for slightly older browser versions aligns with these enterprise practices, ensuring stable, predictable testing across teams. However, it seems like many organisations do not implement to this rule!