Beating SAP Testing Bottlenecks with TestComplete
1) 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 TestComplete
QT - 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?
Getting “NameError: 'aqFileSystem' is not defined” after upgrading to TestComplete v15.77.6.7 (x64).
This issue did not occur in the previous versions of TestComplete. It seems that the aqFileSystem object is no longer being recognized or initialized properly after the latest update. Can anyone find a solution to solve this issue???Stop Skimming PDFs, Start Automating PDF Testing
On the surface, PDFs look simple, but testing them is a whole different story. Invoices, contracts, statements, compliance reports… they’re often the last thing that lands in a customer’s hands. That also means even the smallest issue, like a missing field or a misplaced decimal, can turn into something big. The challenge is that PDFs aren’t like web pages or apps where you can easily inspect elements. They’re containers packed with content, layout, images, and data from different systems. When you add in dynamic content that changes for every customer, formatting that has to stay perfect, and the regulatory risks in industries like finance or healthcare, you start to see why manual testing just doesn’t cut it. It’s slow, inconsistent, and doesn’t scale. This is where automation becomes essential. With automation, you can make sure data is always accurate, layouts stay consistent, and testing scales across thousands of documents without slowing down your team. Instead of spending hours opening PDFs by hand, QA can focus on higher-value work while still knowing that every report or statement going out the door is right. That’s exactly where TestComplete comes in. It’s built to handle the tough parts of PDF testing so you don’t have to. You can validate content down to the last character, run visual checks to keep layouts consistent, and plug it all straight into your CI/CD pipeline. The result is faster releases, fewer headaches, and a lot more confidence that the documents your customers see are exactly as they should be. Click on this link and check out a quick demo to see how TestComplete makes PDF testing easier and more reliable in action.
Sys.OleObject. Microsoft Office (Word, Excel)
I want to get the properties and methods of an already running Microsoft Office (Word, Excel) application. For this I use OLE object but I get an error "This command is not available because no document is open." I take into account what is written in the documentation: Note for Microsoft Office users: In order to be able to get an OLE object for an already running application, this application must be registered in the Running Object Table (ROT). However, Microsoft Office applications that are launched from the shell (for example, from the Start menu or the TestedApps project item) do not register their running objects at startup, but rather once the application loses focus. So, if you obtain an OLE object for an already running Office application, you may get errors when accessing its properties and methods (for more information on this problem, see http://support.microsoft.com/kb/238610/). To work around the problem, you can activate any window other than the tested Office application before attaching to its OLE server. This will allow the Office application to register itself in the ROT, so you will be able to work with it via OLE. In scripts, you can activate a window using the Activate or Click action. For example, use the following statement to activate the Windows taskbar This worked in TestComplete9 but doesn't work now (TestComplete15). Maybe there is some solution for this case? I use DelphiScript
