Skip to main content

Stop Overengineering: Why Test IDs Beat AI-Powered Locator Intelligence for UI Automation

 

We have all read the blogs. We have all seen the charts showing how Generative AI can "revolutionize" test automation by magically resolving locators, self-healing broken selectors, and interpreting UI changes on the fly. There are many articles that paints a compelling picture of a future where tests maintain themselves.

Cool story. But let’s take a step back.

Why are we bending over backward to make tests smart enough to deal with ever-changing DOMs when there's a simpler, far more sustainable answer staring us in the face?

-           Just use Test IDs.

That’s it. That’s the post. But since blogs are supposed to be more than one sentence, let’s unpack this a bit.

1. Test IDs Never Lie (or Change)

Good automation is about reliability and stability. Test IDs—like data-testid="submit-button"—are predictable. They don’t break when a developer changes the CSS class, updates the layout, or renames an element. You know what you're looking for, and it's always there.

2. Why Teach AI What You Already Know?

Generative AI for testing is impressive, sure. It can "guess" the right element even if the locator changes. But why make the AI guess when you could just tell the DOM exactly what to look for from the start? AI should augment your testing strategy, not clean up a mess that could’ve been avoided with proper conventions.

3. Efficiency Beats Elegance in Testing

We’re not building art. We’re validating functionality. Test IDs are low-friction, high-impact tools. They cut through the noise. No need for complex AI models to resolve fuzzy locators or map intent to UI. A test ID is a direct line to what you care about. And it's faster—both in test runtime and in human time.

4. Over-Engineering Doesn’t Scale

The Medium article talks about AI fixing flaky tests and adapting to UI changes. But let’s be real: this adds another layer of complexity. More moving parts. More things that can go wrong. More infrastructure to maintain. If your AI model fails, now your tests are broken, and you’ve got an AI debugging session on your hands. Why not prevent the flakiness in the first place with a simple, durable solution?

5. Developers Can (and Should) Help

Adding data-testid attributes is a tiny investment with massive payoff. It’s part of building testable software. Just like accessibility tags or semantic HTML, it's about building UIs that cooperate with the tools that rely on them.

Note* You can keep chasing the AI-powered dream of resilient, self-healing test automation. Or you can just use test IDs and build a system that’s reliable from day one.

AI is great—but not when it’s solving a problem that shouldn’t exist in the first place.

 

Labels:

Comments

Post a Comment

Popular posts from this blog

ARIA Snapshot in Playwright

  What is an ARIA Snapshot in Playwright? An  ARIA snapshot  in Playwright is a structured representation of a page’s  accessibility tree , which is used by assistive technologies (e.g., screen readers) to interpret the content of a web page. This snapshot helps verify if elements have the correct  roles, names, and properties  required for accessibility. Playwright provides the page.accessibility.snapshot() API to capture this accessibility tree at any given moment during test execution. How Does ARIA Work? ARIA ( Accessible Rich Internet Applications ) is a set of attributes that help improve accessibility by defining roles, states, and properties for elements that are not natively accessible. Example: In this case, the aria-label ensures that screen readers identify the button as “Submit Form.” How to Use ARIA Snapshots in Playwright? Playwright’s  accessibility.snapshot()   method retrieves the  accessible structure  of the page. Ex...
Post a Comment
Read more

Bruno vs Postman: Which API Client Should You Choose?

  As API testing becomes more central to modern software development, the tools we use to test, automate, and debug APIs can make a big difference. For years, Postman has been the go-to API client for developers and testers alike. But now, Bruno , a relatively new open-source API client, is making waves in the community. Let’s break down how Bruno compares to Postman and why you might consider switching or using both depending on your use case. ✨ What is Bruno? Bruno is an open-source, Git-friendly API client built for developers and testers who prefer simplicity, speed, and local-first development. It stores your API collections as plain text in your repo, making it easy to version, review, and collaborate on API definitions. 🌟 What is Postman? Postman is a full-fledged API platform that offers everything from API testing, documentation, and automation to mock servers and monitoring. It comes with a polished UI, robust integration, and support for collaborati...
Post a Comment
Read more

🔧 Self-Healing Selenium Automation with Java — A Smarter Way to Handle Broken Locators

  How to build smarter, more resilient automated tests? We’ve all been there — our Selenium test cases start failing because of minor UI changes like updated element IDs, renamed classes, or even reordered elements. It’s frustrating, time-consuming, and often the most dreaded part of maintaining automated tests. But what if your automation could heal itself? 💡 What is Self-Healing Automation? Self-healing automation  refers to the capability of a test automation framework to recover from minor UI changes by automatically trying alternative locators when the primary one fails. It’s like giving your test scripts a survival instinct. 🔨 🛠️ Implementation in Java + Selenium: Step by Step Step 1: Create a Self-Healing Wrapper We start by creating a custom class called SelfHealingDriver. This class wraps the standard WebDriver and handles locator failures gracefully. public   class   SelfHealingDriver { private   WebDriver driver ; public   SelfHealingDri...
Post a Comment
Read more