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
Support Current FireFox Versions
We currently are on FireFox Version 128ESR, which was released in July of 2024. When I opened a support ticket, I was informed that you only support 115esr which was release in July of 2023. This means that I'm unable to run automation on FireFox as I don't control what version of FireFox my organization uses.
Button with "..." not completing selection - step stops after dropdown choice (Chrome & Edge)
Hello, We are experiencing an issue when selecting buttons that open a dropdown menu - specifically the ones with "...". When TestComplete tries to click and select an option from that dropdown, it opens it and seems to pick the right step, but nothing changes afterward. It looks like the action is registered, yet the test does not continue with the next actions. Environment: Chrome 140.0.73399.208 (Official Build) (64-bit) TestComplete 15.76.5 x64 Same behavior reproduced in Edge 140.0.3485.94 (Official Build) (64-bit) Attachments: Run_Test.mp4 - playback shows TestComplete marking the step as passed (green), but the website state does not change. Has anyone seen similar behavior or a configuration/workaround that forces TestComplete to execute the actual interaction (click/selection) instead of resulting in no UI change? Best regards, Aleksandar
Don't update Chome to v140
For those of you that didn't follow this ticket: Chrome minimizes and reopens every on screen action | SmartBear Community When Chome v139 came out TC stopped working with Chome (and edge). This was fixed in TC v15.77.6. Now Chrome updated again to v140, Testcomplete v15.77.6 does not work with Chome again. If you updated Chome already i recommend downgrading Chrome back to v138 or v139.TC\TE - ObjectSpy issue with latest MS Edge 138.0.3351.121
Just checking to see if others experience this issue. For the most part, the rest of the products I automate and their frameworks do not have this issue. I have one product, that does not change that must from developer changes. It has always worked until a few months back when ... Scripts that worked previously are failing due to TC\TE unable to penetrate the webpage to find the web elements as usual. Scripts can log into the application, but from there ... ObjectSpy can only outline the outer boundary. Manually going into Object Browser with the web page open, I can see and go the the page objects (highlight on screen) that the test script should be finding when running the script. But since not able to penetrate the web page and ObjectSpy red line outlines the outer panel, the value I am trying to enter into a text box jumps up to the MS Edge URL section. I have uninstalled/re-installed the latest TC\TE to verify issue still exists. TestExecute extention is in the Edge browser. I know MS Edge updated around this time period. This is issue is not encountered with Chrome, just MS Edge ? I had opened an IT ticket for this and worked with support, but no solution came from it. I am thinking of switching to using Chrome instead of MS Edge, but this issue bugs me for why it stopped working. I continue to try different things from day to day. This issue has killed my automation for this product. Suggestions? Has this issue been reported from others, and work-around or patches available?
