Accessibility Testing Made Easy: How TestComplete Ensures Web Compliance
Most test automation focuses on functionality but in regulated industries like healthcare, finance, and education, teams must also prove accessibility and compliance. TestComplete’s Web Audit Checkpoints make this simple by integrating accessibility scans directly into automated tests, identifying errors like missing alt text, deprecated tags, and invalid HTML. Teams can set practical thresholds (e.g., zero critical errors, limited warnings) to balance enforcement and flexibility. This ensures every regression run checks not only if features work, but if they meet legal and usability standards. The result is faster compliance, reduced risk, and higher-quality user experiences for everyone. Check out our demo video to see how accessibility testing in TestComplete fits seamlessly into your automation pipeline and helps you build more inclusive, compliant web applications. Accessibility Testing in Testcomplete Demo
KeyWord Test Operations Favorites Category
The Frequently Used category is overall great, but I have some gripes with it. Unable to manually choose the order of the Operations that appear. The Operations supposedly order themselves automatically based on how often they are used, but it sometimes seems a bit arbitrary, with some Operations appearing on the list i think i use less than some Operations that do not show up on the list. Only 10 Operations can be displayed at a time. This is too few Operations to show and i often find myself needing to type search for addition Operation i often use. In the default Workspace layout / 'Desktop' / screen arrangement there is room for maybe at least another 10 Operations to be displayed on a 1080p monitor. showing 20 might be a bit excessive tho. Unable to choose which Operations appear. While this problem generally sorts itself out after a long time in usage, it would be nice to be able to just choose what shows up, or if the usage data where to ever be wiped for some reason (getting a new workstation, etc) I think adding a Favorites Category would solve all of the above small issues.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.
Automatic creation of "Variables"
While recording a test, we input values into one or more fields of a form under test. Currently TestComplete "hard codes" these as constant values in the test steps. even when we create a script out of these steps, the constant values go in there. In order to make the script work for generic test data, testers have to manually create variables and assign the values, which takes as much time as there are input fields. In order to reduce the cycle time from recording to replay with any test data, it is suggested that: For all input fields that the user enters some value during recording of a test, TestComplete has to create as many variables automatically Assign the default values to these variables with the values supplied / keyed-in by testers during test recording. This feature can be made available as one of the project / tool options.
project explorer tree expansion
With right click on a branch in the project explorers tree the option for collapsing/expanding appears. But everytime it collapses/expanses the whole tree and not certain branches. When you working with complex projects it would be great to have the option to just collapse/expand a single branch.
Keyword tests in different directories should be allowed to have the same name
We have different directories for keyword tests associated with each page of our application. As we work on them, we would like to have that keyword test called something like Sandbox. Being in different directories, that should be allowable, but TestComplete complains. For example, given KeywordTests->LoginTests->Sandbox, we should be able to create a keyword test KeywordTests->UserAdminTests->SandboxWhen change a name in NameMapping, Then the object name in script tests would also update
Let's say you don't like the name you gave an object in the NameMapper. When you change the name of that object, the name will also be updated in any and all Keyword tests which this object was used in. However, the name will Not be updated when used in script tests. It would be nice if the name would be updated in Scripts. Sometimes we think of better naming conventions and want to rename some objects.
