Cursor
testing
E2E Tests Timing Out in Cursor-Generated Test Suites
End-to-end tests generated by Cursor using Playwright, Cypress, or Selenium time out during execution. Tests hang waiting for elements that never appear, pages that never load, or network requests that never complete. The tests work sometimes but fail intermittently, making your test suite unreliable and CI pipelines unpredictable.
E2E test flakiness is the number one reason teams abandon automated testing. Cursor generates tests that follow the happy path but don't account for the asynchronous, timing-dependent nature of real browser interactions. The AI writes selectors for elements that may not exist yet, clicks buttons before they're interactive, and asserts content that loads asynchronously.
The result is a test suite that passes locally (where the app is fast) but fails in CI (where resources are limited and the app is slower), or passes 80% of the time and fails randomly on the other 20%.
Error Messages You Might See
TimeoutError: Waiting for selector "button.submit" exceeded 30000ms
TimeoutError: page.waitForNavigation: Timeout 30000ms exceeded
Error: Element is not visible or not an HTMLElement
CypressError: Timed out retrying after 4000ms: Expected to find element: '[data-cy=result]'
Test timeout of 60000ms exceeded
Common Causes
- Static waits instead of dynamic waits — Cursor uses
await page.waitForTimeout(3000)instead of waiting for specific elements or conditions, which is both slow and unreliable - Fragile CSS selectors — Tests use selectors like
.sc-bdfBwQ.iQNHGt(auto-generated class names) that change every build, or deeply nested selectors that break with minor DOM changes - Missing API/network wait — The test clicks a submit button and immediately checks for a success message, without waiting for the API request to complete
- Element not interactable — The test tries to click an element that's rendered but covered by a modal, loading overlay, or tooltip
- CI environment is slower — Tests assume fast load times from local development. CI runners have less CPU/memory, making everything slower and timing-dependent tests fail
- Navigation not awaited — The test clicks a link that triggers navigation but checks for content before the new page loads
How to Fix It
- Use data-testid attributes — Add
data-testid="submit-button"to important elements and select withpage.getByTestId('submit-button'). These are stable across builds and style changes - Wait for specific conditions, not time — Replace
waitForTimeoutwithawait page.waitForSelector('[data-testid="success-message"]')or Playwright's auto-waiting assertions likeawait expect(page.getByText('Success')).toBeVisible() - Wait for network idle after actions — Use
await page.waitForLoadState('networkidle')orawait page.waitForResponse(url => url.includes('/api/submit'))after form submissions - Increase default timeout for CI — Set
timeout: 60000in your Playwright/Cypress config for CI environments while keeping shorter timeouts locally - Use Playwright's built-in auto-waiting — Playwright's
click(),fill(), andexpect()methods auto-wait for elements to be visible and interactive. Use these instead of manual waits - Add retry logic for flaky assertions — Use Playwright's
expect().toBeVisible({ timeout: 10000 })or Cypress's built-in retry-ability to handle timing variations
Real developers can help you.
Yovel Cohen
I got a lot of experience in building Long-horizon AI Agents in production, Backend apps that scale to millions of users and frontend knowledge as well.
Costea Adrian
Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system.
Nam Tran
10 years as fullstack developer
Vlad Temian
15+ years shipping production infrastructure for startups. Former CTO at qed.builders (acquired by The Sandbox).
Cursor ambassador and agentic tooling builder.
I've scaled systems, automated deployments, and built observability tools for AI coding workflows. I specialize in taking vibe-coded apps from broken prototype to production-ready: fixing Supabase auth/RLS, Stripe integrations, deployment pipelines, and cleaning up AI-generated spaghetti.
I build tools in this space (agentprobe, claudebin, micode) and understand both sides: how AI generates code and why it breaks.
https://blog.vtemian.com/
Matthew Butler
Systems Development Engineer @ Amazon Web Services
Stanislav Prigodich
15+ years building iOS and web apps at startups and enterprise companies. I want to use that experience to help builders ship real products - when something breaks, I'm here to fix it.
Sage Fulcher
Hey I'm Sage! Im a Boston area software engineer who grew up in South Florida. Ive worked at a ton of cool places like a telehealth kidney care startup that took part in a billion dollar merger (Cricket health/Interwell health), a boutique design agency where I got to work on a ton of exciting startups including a photography education app, a collegiate Esports league and more (Philosophie), a data analytics as a service startup in Cambridge (MA) as well as at Phillips and MIT Lincoln Lab where I designed and developed novel network security visualizations and analytics. I've been writing code and furiously devoted to using computers to make people’s lives easier for about 17 years. My degree is in making computers make pretty lights and sounds. Outside of work I love hip hop, the Celtics, professional wrestling, magic the gathering, photography, drumming, and guitars (both making and playing them)
Anthony Akpan
Developer with 8 years of experience building softwares fro startups
Caio Rodrigues
I'm a full-stack developer focused on building practical and scalable web applications. My main experience is with **React, TypeScript, and modern frontend architectures**, where I prioritize clean code, component reusability, and maintainable project structures.
I have strong experience working with **dynamic forms, state management (Redux / React Hook Form), and complex data-driven interfaces**. I enjoy solving real-world problems by turning ideas into reliable software that companies can actually use in their daily operations.
Beyond coding, I care about **software quality and architecture**, following best practices for componentization, code organization, and performance optimization.
I'm also comfortable working across the stack when needed, integrating APIs, handling business logic, and helping transform prototypes into production-ready systems.
My goal is always to deliver solutions that are **simple, efficient, and genuinely useful for the people using them.**
Basel Issmail
’m a Senior Full-Stack Developer and Tech Lead with experience designing and building scalable web platforms. I work across the full development lifecycle, from translating business requirements into technical architecture to delivering reliable production systems.
My work focuses on modern web technologies, including TypeScript, Angular, Node.js, and cloud-based architectures. I enjoy solving complex technical problems and helping teams turn product ideas and prototypes into working platforms that can grow and scale.
In addition to development, I often collaborate closely with product managers, business analysts, designers, and QA teams to ensure that solutions align with both technical and business goals.
I enjoy working with startups and product teams where I can contribute both as a hands-on engineer and as a technical partner in designing and delivering impactful software.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
How do I make E2E tests less flaky?
Three key practices: 1) Never use fixed timeouts (waitForTimeout), always wait for specific conditions. 2) Use stable selectors (data-testid) instead of CSS classes or XPath. 3) Wait for network requests to complete before asserting results. Also run tests in a consistent environment with controlled test data.
Should I run E2E tests in CI on every commit?
Run fast unit tests on every commit. Run E2E tests on pull requests and before deployments. E2E tests are slow and resource-intensive, so running them on every commit slows down the feedback loop. Use parallelization and test sharding to speed them up when you do run them.