Automated UI Testing Tools

OpenOnco quality control: testing a closely integrated diagnostics database and codebase: LLM Data Review + UI Regression Testing. OpenOnco grew from prototype to production in about a month: 80+ diagnostic tests, complex filtering, PDF export, comparison tools. 12K lines of code. Manual QA stopped working, fortunately some smart software folks advised us. Here's our system: (1) Multi-LLM Data Verification Before each deploy, I run the full database through Claude, Grok, GPT-5, and Gemini 3. Each model reviews test data for: → Inconsistencies between related tests → Outdated info vs. current clinical guidelines → Missing fields that should be populated → Logical errors (FDA-approved test with no approval date) Different models catch different things. Claude finds logical inconsistencies. GPT-5 catches formatting. Grok flags outdated clinical data. Gemini spots missing cross-references. (2) Automated UI Regression Testing Regression testing: "Did my changes break something that was working?" For us this means testing actual user workflows — clicking buttons, filling forms, navigating between pages — and verifying the interface behaves correctly every time. We test the actual UI, not just components in isolation: → Filter interactions: Click "IVD Kit" filter → verify correct tests appear → click "MRD" category → verify intersection is correct → clear filters → verify all tests return → Test card workflows: Click test card → modal opens with correct data → click "Compare" → test added to comparison → open comparison modal → verify all fields populate → Search behavior: Type "EGFR" → verify matching tests surface → clear search → verify full list returns → Direct URL testing: Navigate to /mrd?test=mrd-1 → verify modal auto-opens with correct test → Navigate to /tds?compare=tds-1,tds-2,tds-3 → verify comparison modal loads with all three → PDF export: Generate comparison PDF → verify page count matches content → verify no repeated pages (caught a real bug where Page 1 rendered on every page) → Mobile responsiveness: Run full suite at 375px, 768px, 1024px, 1440px breakpoints We run these tests using Playwright — an open-source browser automation framework. It launches real browsers (Chrome, Firefox, Safari), executes user actions, and asserts outcomes. Tests run on every push via GitHub Actions; deploy is blocked if anything fails. Full suite takes ~4 minutes 🤯🤯🤯 The combination of LLM data review + real UI regression testing catches what unit tests miss: so far, hundreds of issues 👍🏼👍🏼👍🏼

Last week I talked with more than 70 QA Leads from different companies across the globe among my LinkedIn contacts. We talked about UI test automation frameworks. Here are some of the insights... 36% use Playwright 25% use Selenium 16% use Cypress Just 2 companies keep using Webdriver IO 10% use Playwright and Cypress 5% use Selenium and Cypress 3% use Playwright and Selenium 10% of those who currently use Playwright transitioned from Selenium recently. Companies that have both, Playwright and Cypress are generally happy with both frameworks. So they keep running older projects on Cypress but use Playwright for the new projects and do not rush with the transition. Companies that use Selenium and Cypress, or Selenium and Playwright, are thinking of making a transition from Selenium or are in the process of doing it. Few big companies have all 3 big frameworks in their tech stack. In summary, Playwright is already No. 1 in terms of adoption. Selenium is holding second place, but I noticed a higher desire to transition from Selenium than from Cypress. So I think in 1-2 years Selenium will be the 3rd.

As a backend developer, my job doesn’t end at writing an API–it starts there.  Once the API is developed, the real challenge begins: testing. Thinking through every possible scenario where it could fail. Manually setting up test cases in Postman. Verifying if it works across different environments. Ensuring role-based access control behaves as expected. And if the API internally calls other APIs? That means setting up an entirely different set of tests.  It’s a time-consuming, tedious process. And let’s be honest, testing has never been the most exciting part of development.  Recently, I came across KushoAI, and it completely changed my perspective. Instead of manually writing and managing test cases, I could just provide my API details–a cURL request, Open API specs, Postman collection, or HTTP request–and Kusho would do the rest.  - It auto-generates test cases, covering even those edge cases I might have missed.   - It runs tests across different environments effortlessly.   - It handles user roles and access governance without extra setup.   - It even lets me create end-to-end test suites by simply defining API workflows, ensuring everything works together.  What used to take hours of effort now happens in minutes. And the best part? I no longer have to second-guess whether my API will work in production.  But that’s not all–Kusho.AI isn’t just transforming API testing, it’s redefining UI testing too. Imagine this: instead of manually writing long automation scripts or spending hours thinking of test scenarios, you just record your user journey using the Kusho.AI Chrome extension–and that’s it! Kusho automatically generates comprehensive Playwright test scripts for you. -  Use the app like a real user–Kusho does the rest. -  No need to write automation scripts–it’s all generated for you. -  Find UI bugs before they reach production. Now, software developers and testers can validate their front-end effortlessly–having to write a single line of automation code. Kusho.AI is making testing smarter and efficient. Whether you’re testing APIs or UIs, it’s a game-changer for developers who want to ship reliable software faster and with confidence. Check it out here: https://kusho.ai/ #SoftwareTesting #API #UITesting #Automation #KushoAI

Testing with AI: Post 3 ------------------------- Continuing my Testing with AI series, today I’m sharing another amazing AI-powered assistant in software testing—TestCraft. What is TestCraft? In their own words: ============================ TestCraft is a Chrome extension designed to be a companion to your software testing. With TestCraft, you can select UI elements directly from your browser and leverage the capabilities of large language models (LLMs) to generate innovative test ideas, write automation scripts across various frameworks and programming languages, and perform accessibility checks. What makes TestCraft special? ============================ 1) It’s open source—easy to start, and free to explore. 2) You can install it as a Chrome extension, select elements directly on the page, and automate them effortlessly. 3) It supports popular frameworks like Cypress, Selenium, and Playwright. 4) Programming languages supported: JavaScript, TypeScript, Java, C#, and Python. My experience with TestCraft: ====================== I tried using it with Cypress and JavaScript, and here’s what I found: (1) It automatically generated a variety of test cases, including edge cases, which saved me a lot of time. (2) The tool provided a great starting point, though some minor tweaks were needed—particularly around error messages. But honestly, that wasn’t a big deal. (3) For beginners in automation, this tool is fantastic, offering a solid base on which to build. (4) Even experienced testers will find it useful, as it generates a comprehensive list of test cases, saving time on repetitive tasks. The best part? It’s so simple to use! Just install the extension, select elements on the page, and let TestCraft do the rest. While it’s not perfect yet (minor adjustments are required), it’s worth trying out. I’ve attached some screenshots from my experience with the tool to give you an idea. Give it a shot—you might just save yourself hours of work! Link -> https://lnkd.in/gZityxRR #TestingWithAI #TestCraft #AutomationTools #Cypress #Selenium #Playwright #Efficiency #ABAutomationHub