Users don't use data-testid, so why do your tests?

TK Dodo is a platform dedicated to sharing insights and resources on software development, technology trends, and career growth. Through articles, interviews, and community engagement, TK Dodo empowers developers to navigate their career paths, stay updated with industry advancements, and cultivate  skills for personal and professional development.

TkDodo

Using data-testid attributes in tests is an accessibility smell because users can't see or interact with test IDs. Role-based selectors (via Testing Library or Playwright) are superior because they mirror how real users interact with apps, catch inaccessible markup like clickable divs lacking semantic roles, and provide implicit a11y testing. If a role-based selector can't find an element, that's a signal the UI itself is inaccessible. Practical tips include using semantic HTML for implicit ARIA roles, associating form labels, using headings and landmarks, leveraging Testing Playground, and navigating with the keyboard to catch issues.

Test IDs are an a11y smell

<p>I can’t tell you the amount of times I’ve had an agent write tests only to get stuck and start using <code>data-testid</code> workarounds that end up not testing the implementation very well</p>
