Hover Button...
When using the TestComplete Desktop module for record‑based automation testing, there are cases where a button is not visible and therefore cannot be clicked. This happens when the button only appears on mouse hover. When the mouse is manually moved to that position, the button becomes visible, but during the recorded automated test the button does not appear and the test cannot proceed. What is the best way to hover over a button that is not visible during the test and then click it? <<= Look !!!
Testcomplete issue with Java17 ( Javax Swing applications)
My desktop Javax Swing applications were recently upgraded from Java 8 to Java 17, and since then I’ve been experiencing an intermittent issue where the main parent object is not recognized, causing repeated failures. Has anyone else encountered this when using TestComplete with Java 17?I am using TestComplete version is 15.76.5.7 (x64).
Test Complete does not locate my Desktop app
Hi everyone, when I run every test, Test Complete does not minimize, so it does not locate my desktop app, this behavior happens 7 or 8 times, then it does minimize and locate my desktop app and the test runs. I want to mention that (on my properties project, on Playback) I do have the option: Minimize Test Complete clicked, but even though it takes so much time to run correctly, so I have to wait 7,8 or sometimes even 10 times for Test Complete to minimize and run my tests. Is there any solution for this issue? Thanks in advance Best regards
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 ManagerBeating SAP Testing Bottlenecks with TestComplete
Testing SAP is hard for all the familiar reasons, complex UIs, transports that tweak screens, sensitive data, and heavy audit needs. Below are the common bottlenecks and how TestComplete helps you cut through them. Fragile object locators in SAP GUI The bottleneck: SAP GUI controls can be tricky to identify reliably minor UI changes or different dynpro states can break scripts. How TestComplete helps: It provides native support for SAP GUI for Windows with extended objects (buttons, edit fields, grids, etc.), so you work with properties and methods not coordinates. Pair that with Name Mapping (a central, alias-based object repository) to make tests readable and resilient. 2) UI drift after transports equals flaky tests The bottleneck: After a support pack or transport, object properties change and tests fail even though the flow still works. How TestComplete helps: Self healing tests automatically look for close matches when an object isn’t found, reducing “false red” failures and maintenance. 3) “Hard” screens, canvas elements, or remote sessions The bottleneck: Custom controls or canvases don’t expose stable object trees. How TestComplete helps: Use AI-powered OCR (and the OCR Action in Keyword Tests) to find text on screen and create easy validation as a fallback when classic object IDs aren’t reliable. 4) Test data sprawl (pricing, partners, plants…) The bottleneck: You need many variants to cover conditions, taxes, partners, plants, and languages without hand cloning tests. How TestComplete helps: Built-in data driven testing lets you drive one test with rows from Excel/CSV/DB, multiplying coverage while keeping scripts lean. 5) Audit evidence for SOX/GxP The bottleneck: Auditors want traceable, reviewable evidence: who ran what, where it clicked, and what was on screen. How TestComplete helps: Test Visualizer captures step-by-step screenshots during record/playback; Video Recorder can capture full-run videos; detailed logs tie everything together. These are ideal for defect triage and audits. 6) CI/CD traceability (and repeatability) The bottleneck: Manual runs don’t scale; teams need runs linked to commits/builds. How TestComplete helps: Use the Jenkins plugin to trigger suites in jobs or Pipelines and view results in Jenkins, creating a clean chain of custody for each build. Final thought SAP is always changing, your tests shouldn’t break every time it does. TestComplete’s native SAP GUI support, Name Mapping, self-healing, OCR fallback, and data-driven runs help you keep testing stable and audit friendly with less maintenance. The following demo illustrates these features in practice, automating the creation of a purchase requisition within SAP while maintaining stability across UI changes. Demo: Automating Purchase Requisition Creation in SAP with TestCompleteQT - Error No such interface supported
Has anyone been able to test modern QT applications 6.7 or 6.8 and get it to work. I cannot even get the simple example applications from QT to function. According to support currently 6.7 and 6.8 are supported, but neither seem to work. Just using the object browser shows error for most items, and none of the QT related methods are even displaying or accessible. See attached image. Any one have a solution to this? **I tried to upload a small zip file that contains the QT sample app, but the forum prevents it from being uploaded.
Trouble Recording Tests for WPF WebView2 Application – Entire Window Detected Instead of UI Elements
Hi everyone, I'm currently evaluating TestComplete to see if it's a good fit for testing my WPF application, which uses a WebView2 container to render our web-based UI. During my trial, I’ve run into a major roadblock: when I try to record tests or use the Object Spy, TestComplete only detects the entire application window as a single object. It doesn’t recognize or allow interaction with individual UI elements inside the WebView2 control. I’ve tried both keyword test recording and using the Object Spy, but neither approach identifies the DOM elements or controls within the WebView2 content. Instead, TestComplete treats the entire WebView2 area as a single object. Additionally, I wasn’t able to find any documentation or official guidance regarding TestComplete’s support for desktop applications using WebView2. This makes it difficult to determine whether this is a limitation of the tool or if there’s a configuration I’m missing. The previous posts regarding this issue are in the realm of 6-8 years old so I'm hoping there is a current fix to this issue. Has anyone successfully tested a WPF + WebView2 application with TestComplete? Are there any configurations, plugins, or workarounds that allow TestComplete to access and interact with the DOM inside WebView2?
