TestComplete detects the table control itself, but none of the internal row/cell objects are exposed
I have a table-like control similar to the one in the screenshot. Using "Add Object" in TestComplete, I can capture the main table object. (object: Aliases.Icad.dlgAECStylesManager.Item.SysListView32) However, when I explore it in the Object Browser, the table exposes only one child object — the header. There are no row objects, no cell objects, and no data nodes visible under the table. Because of this, TestComplete cannot interact with the table using the normal object model (such as row/cell access, FindChild, ClickCell, etc.). My goal is to automate editing based on the row index. For example: Update the “Name” column for the row where Index = 101 (change it to "Testing1"). Has anyone encountered this type of control or found a reliable solution for automating tables that do not expose row/cell objects? Any suggestions would be greatly appreciated. Thanks!Object Brower : annoying behavior
Hi everyone ! I have a very annoying issue. Sometimes, the object browser load the DOM in the same manner than "legacy features". The normal behavior is this : Custom Angular components are properly detected, like "AppSignRoot" in this example. But sometimes, the tree look like this : Custom components are not properly detected. Here, the "AppSignRoot" node is "Panel(4)". If I hit the refresh button, everything gets back to normal like the first screenshot. But, calling the Refresh() method on the page object or browser object (in my script and / or test item) does nothing. The DOM is randomly not detected properly. And I'm out of solutions. Any idea ?
Object Recognition Challenges? Help Us Understand Your Use Cases
Hello TestComplete Community! We’re working on a new Visual Object Detection (VOD) capability powered by AI, designed to make it easier to test applications where traditional object recognition struggles. This feature aims to help you reliably identify visual elements that are hard to detect today. To make sure we’re building this in the most useful and relevant way, we’d love to learn more about your current challenges and use cases related to visual or hard-to-recognize objects. Your real-world scenarios will help shape how we design and prioritize VOD. Feel free to share your thoughts by replying directly to this post, or send me a private message if you prefer. Thank you in advance for your feedback we truly appreciate it! Temil Sanchez Product ManagerGeneral issues interacting with Desktop/Web app
Main Question: Does anyone else use TestComplete to test a C++ MFC (Rogue Wave + Stingray) application? If so, are you able to see the MSVC attributes when using TestComplete version 1577 and/or 1578? Background: Today I've spent testing out different versions of TestComplete. Version 15.68 through 15.76 have no issues accessing the MSVC properties (attributes) of the C++ application. However, version 15.77 can no longer see certain attributes for the C++ application. However, version 15.77 is the first version that can successfully interact with dropdowns in a browser (chrome 141). I cannot downgrade the version of Chrome. Currently I am forced to use version 15.76 or earlier for testing the desktop application and version 15.77 or later to test the web applications. This is not optimal and am concerned about the more recent versions not able to access the MSVC properties.
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!
Windows form not always recognized in property checkpoint
I have added existing tests from one project into a second project. I run a test that includes one of the tests from the 1st project. In this test I first do a WaitAsChild operation witha 90 second timeout and I can see that the form is open in lest than the 90 seconds. Then I run a property checkpoint to check if a form is VisibleOnScreen. Sometimes TestExecute will give an error that it can't find the Aliases.AppName.FormName. Other times it works fine. After a failure if I readd the tests to the 2nd project it works fine. NameMapping is the same in both projects. Any suggestions how to prevent this problem?
