Robust automated tests, data-testid and QA leadership.

Articles for Lead QA, CTOs and founders who want their automation to stop breaking every sprint.

·6 min read

A data-testid naming convention that scales beyond 10 devs

Without a convention, your data-testid attributes turn into a museum of styles after six months. Here's the kebab-case scope-element-role pattern that survives team growth, with concrete examples and how to enforce it without becoming the DOM police.

Read article →
·8 min read

data-testid is not a code smell - a nuanced reply to Testing Library

Kent C. Dodds and the Testing Library community argue data-testid is an a11y smell. They have a point. They also miss one. Here's why both camps are right, and how to combine them in practice.

Read article →
·7 min read

Why your Playwright tests break every sprint (and it's not Playwright's fault)

Your e2e suite isn't fragile because the framework is bad. It's fragile because your selectors borrow stability from things that were never meant to be stable. Here's the real diagnosis, with names.

Read article →
·6 min read

Why robust automated tests start with data-testid

Most flaky Playwright and Cypress suites don't fail because the framework is bad. They fail because the selectors are fragile. Here is the case for treating data-testid as production code.

Read article →