I'm really frustrated with our Cypress test suite. Every sprint, it breaks not from actual software bugs, but simply because class names are changed, elements are moved, or the design system gets updated. Just this past week, we rolled out a new component library and ended up with 25 failing tests. I wasted Thursday and part of Friday fixing selectors instead of working on real features that our users need. The product team keeps wondering why our frontend is always behind, and I feel like I have this massive Cypress suite, which almost feels like an additional product we have to manage. I'm aware testing is crucial, but there has to be a more efficient way to run things. I've heard about self-healing tests that adapt to changes in selectors—are those legitimate, or just a marketing gimmick? I can't keep spending whole sprints on test maintenance. Is there something wrong with my Cypress setup, or do others experience this too?
5 Answers
You should make your CI enforce a 100% success rate on all tests before allowing any merges. Always ensure branches are up to date to avoid broken builds. Also, consider adopting a stable scheme of data attributes instead of class names to make your tests less sensitive.
You’re definitely not alone! A lot of developers loathe end-to-end testing for this exact reason. It can consume so much time that could be spent building features instead of maintaining tests.
I’ve found AI really helpful for refactoring tests. If you describe the changes clearly, AI can help adjust your selectors effectively. Just keep in mind that using user-visible text or ARIA labels can help identify when real changes occur.
Honestly, if someone’s changing things that end up breaking the tests, they should fix those before merging any updates. Why isn’t this part of your CI checks? You could prevent these wrinkles from reaching the main branch in the first place.
It sounds like you're relying heavily on class names as selectors. That would definitely lead to constant issues when they change. I recommend using ARIA roles or creating data-test ID selectors. They’re more stable and less likely to break with design updates.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads