Playwright Tests Timing Out on CI Pipeline
Your Playwright end-to-end tests pass consistently in local development but timeout or fail intermittently on CI platforms like GitHub Actions, Vercel, or GitLab CI. Tests that complete in seconds locally take minutes on CI before being killed by the timeout, and the same test suite may pass on one run and fail on the next.
CI environments have significantly fewer resources than developer machines. Shared runners have limited CPU, memory, and no GPU acceleration for browser rendering. Combined with the overhead of starting a Next.js development server and launching browser instances, tests that are fast locally can exceed CI timeouts by a large margin.
V0-generated Playwright configurations often use default settings optimized for local development, not for resource-constrained CI environments where tests run headless on shared infrastructure.
Error Messages You Might See
Common Causes
- Dev server slow to start on CI — next dev takes 30+ seconds on CI runners, causing tests to start before the server is ready
- Default timeouts too short — Playwright's 30-second default timeout insufficient for CI rendering speeds
- Too many parallel workers — default worker count matches CPU cores, which overwhelms CI runners with limited resources
- Browser installation missing — Playwright browsers not cached between CI runs, adding minutes to each pipeline
- Animations and transitions — CSS animations that complete instantly locally take full duration on underpowered CI
- Network requests to external services — tests hitting real APIs that are slow or rate-limited from CI IP addresses
How to Fix It
- Use production build — run
next buildthennext startinstead of next dev for faster, more consistent performance on CI - Increase timeouts — set
timeout: 60000in playwright.config.ts and per-test timeouts for slow operations - Limit workers — set
workers: 1orworkers: process.env.CI ? 1 : undefinedto prevent resource contention on CI - Cache Playwright browsers — add browser cache to your CI configuration to avoid downloading browsers on every run
- Wait for server properly — use
webServer: { command: 'next start', url: 'http://localhost:3000', reuseExistingServer: !process.env.CI } - Mock external APIs — use Playwright's route.fulfill() to mock external API responses and eliminate network dependencies
Real developers can help you.
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.
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.
PawelPloszaj
I'm fronted developer with 10+ years of experience with big projects. I have small backend background too
Jaime Orts-Caroff
I'm a Senior Android developer, open to work in various fields
Kingsley Omage
Fullstack software engineer passionate about AI Agents, blockchain, LLMs.
Pratik
SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure
Bastien Labelle
Full stack dev w/ 20+ years of experience
Tejas Chokhawala
Full-stack engineer with 5 years experience building production web apps using React, Next.js and TypeScript.
Focused on performance, clean architecture and shipping fast.
Experienced with Supabase/Postgres backends, Stripe billing, and building AI-assisted developer tools.
Franck Plazanet
I am a Strategic Engineering Leader with over 8 years of experience building high-availability enterprise systems and scaling high-performing technical teams. My focus is on bridging the gap between complex technology and business growth.
Core Expertise:
🚀 Leadership: Managing and coaching teams of 15+ engineers, fostering a culture of accountability and continuous improvement.
🏗️ Architecture: Enterprise Core Systems, Multi-system Integration (ERP/API/ETL), and Core Database Structure.
☁️ Cloud & Scale: AWS Expert; architected systems handling 10B+ monthly requests and managing 100k+ SKUs.
📈 Business Impact: Aligning tech strategy with P&L goals to drive $70k+ in monthly recurring revenue.
I thrive on "out-of-the-box" thinking to solve complex technical bottlenecks and am always looking for ways to use automation to improve business productivity.
MFox
Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Why do tests pass locally but fail on CI?
CI runners have less CPU, memory, and no GPU. Tests that complete in milliseconds locally can take seconds on CI. Increase timeouts and reduce parallelism.
How do I cache Playwright browsers on GitHub Actions?
Use actions/cache with key based on playwright version: path: ~/.cache/ms-playwright, key: playwright-${{ hashFiles('package-lock.json') }}.
Should I use next dev or next start for CI tests?
Always use next build && next start for CI. The production build is faster, more consistent, and closer to what users actually experience.