"CloseAllModalDialogs()" Script Built-In Function
If a Desktop test fails, it can leave modal dialogs open, which will then block any future interactions with the main application window (or other app-owned windows). It would be nice to have a function that can be called at the start of each test that would ensure that all modal dialogs belonging to the application are closed (including system modals opened by the app, e.g. "Open File" or "Open Folder"). (And something like this would be valuable in Keyword Testing as well.)
.NET 9 Support
Hello, Our application needed to update to .NET 9 and since then there has been an error that has become much more prevalent in TestComplete. Here's my original post about it. I've been in contact with support and they had mentioned that .NET 9 wasn't fully supported by TestComplete yet. Is there any way this support could get added to your backlog?
Implementation of Built-in RightClickNextTo Function in OCR Module
We propose the addition of a new built-in function called RightClickNextTo in the OCR module of TestComplete. This function would work similarly to the existing ClickNextTo but would simulate a right-click action next to an identified text element based on its coordinates. Currently, we have implemented a custom RightClickNextTo function by leveraging the x1, y1, x2, y2, height, and width coordinates obtained from the Bounds function of the OCR object. After identifying the text, the function calculates the necessary offset and direction to perform the right-click action. However, we initially encountered challenges when applying this function to the BlockByText object due to coordinates errors. After further experimentation, we realized that the coordinates should be applied directly to the ClickR in the image object or the screen object identified through the TestComplete Object Spy, bypassing the OCR object's bounds error. While this solution works, we believe that incorporating this functionality as a native built-in feature within the OCR module would streamline the process and make it more accessible to all users. The RightClickNextTo function could be used for more precise interaction with text elements based on their coordinates, particularly for scenarios where right-clicking actions are needed, improving the flexibility and usability of the OCR module for automated testing. By making this a built-in function, TestComplete users would save time and avoid errors when trying to implement similar solution manually, improving overall productivity and reducing complexity in the automation process. Code Snippet: [ Refer the attached image] This code snippet demonstrates how the custom RightClickNextTo function calculates the coordinates and applies a right-click at the identified text's location using the image or screen object. We truly appreciate your consideration of this suggestion, as making it a built-in function would greatly enhance the usability of the OCR module for right-click action, benefiting users and simplifying the automation process.Desktop Testing Parallelization for CI/CD
Right now, when we want to parallelize our desktop tests with TestComplete, we assign tags to various groups, then use GitHub Actions to run the various tags in parallel. While this works, it's also a very manual process that requires rebalancing test groups by hand. It would be ideal if there was some way to have TestComplete split groups of tests for running in batches, that I could then feed into our CI/CD Actions. This could work for non-Desktop tests as well, but I'm focusing on Desktop testing since there is at least some parallelization for web and mobile.
TestComplete not recognizing object after updating of Component One control to latest version
TestComplete (ver 15.66.7) is not recognizing an grid objects after updating Component One Control to the latest version (2023.3.1.0). Looks like TestComplete supports ComponentOne C1Command for .NET 2.0.2. Lots of tests are failing because of this and we have release next week..NET Core 8 Support
Hi, I wanted to ask when .NET assemblies with .NET Core and .NET 8.0 applications will be supported. https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core Because the versions currently supported by TC are officially outdated and are no longer supported. Thanks and best regardsOCR Recognize DetectTable enhancements
// Specify the preferable search area var searchPref = spLargest; var table = OCR.Recognize(Grid).DetectTable(searchPref, hasHeader); I have above code, and depending on what is configured in the searchPref variabele, it detects or leaves out certain columns for the same Grid. I feel it's not that robust. 1st NF: perhaps some preview window could be opened to actually see at which columns it looks when using DetectTable, because now you don't have such an overview and you hope for the best and try different options, spLargest etc... 2nd NF: Behaviour like the Table Checkpoint wizard. In the Table Checkpoint wizard you could drag and specify your table area to let OCR take a look at and pull data from non-supported grids/tables. So you can be more specific than the standard DetectTable functionality.
