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

Labels:

Comments

Post a Comment

Popular posts from this blog

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (en...
Post a Comment
Read more

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Post a Comment
Read more

ChainTest Reporting Framework (ExtentReports is being sunset)

  ExtentReports is being sunset and will be replaced by ChainTest Reporting Framework. 1. What is ChainTest? ChainTest is an open-source test reporting and analytics framework designed to enhance the way QA teams manage and analyze their test results. Think of it as a central hub for all your test data, offering: Real-time analytics : Stay updated with the latest test outcomes. Historical reports : Compare results over time to identify trends and improve processes. Static reports : Easily share detailed HTML reports with stakeholders. Multi-project dashboards : Consolidate data from different projects into a single view. This tool is designed to integrate seamlessly into your existing testing workflows, providing both flexibility and scalability. 2. Why Use ChainTest? Let’s talk about why ChainTest stands out: Enhanced Visibility : Gain clear insights into your test execution metrics, helping your tea...
Post a Comment
Read more