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 TestCompleteGeneral 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.
Right-Click Menu on SVG Map Not Detected in TestComplete
Hello SmartBear Support, I’m encountering an issue in TestComplete related to right-click actions on an SVG map. When I record a test that includes a right-click on the SVG element, TestComplete does not detect or interact with the context menu that appears after the right-click. Even when I try to run the test manually (by simulating the same right-click action), the menu still isn’t recognized or interacted with during playback. This behavior used to work correctly in previous versions, so it may be a regression in the current release. Could you please advise on possible causes or workarounds for this issue? Thank you, Mihaela Duca Version of TestComplete 15.77.6.7 x64Stop 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.
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!Accelerating Quality: How TestComplete Leads in Test Creation, Execution, and Object Recognition
Temil Sanchez, the new Product Manager for TestComplete, shares insights from a recent evaluation comparing TestComplete and Ranorex. TestComplete stood out for its faster test creation, intuitive interface, and superior object recognition, which reduce maintenance and ensure robust automation. Looking ahead, the focus is on integrating AI to further accelerate test creation, enhance resilience, and help teams release quality software faster.
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?
