Does Cypress support Safari and Internet Explorer?

No, and it's annoying as hell because everyone asks this. Cypress only supports Chrome and Firefox because of how it runs inside the browser. This means you're fucked if you need full browser coverage - you'll have to use Playwright or crawl back to Selenium if Safari support is a dealbreaker.

What's the difference between free Cypress and Cypress Cloud?

The Cypress app is completely free and open-source. You can write, run, and debug tests locally without paying anything. Cypress Cloud is a paid service that adds parallelization and analytics. It starts around $70/month and gets expensive fast if you have multiple projects.

Can Cypress test mobile applications?

No, it can't test native mobile apps. It can only test responsive web apps through device emulation. If you need to test actual mobile apps, you're stuck with Appium or other mobile-specific tools that are even more painful.

How does Cypress handle authentication and cookies?

Cypress lets you authenticate via API calls and set tokens or cookies directly instead of filling login forms repeatedly. This is faster and more reliable than UI-based authentication. The programmatic approach works great for testing workflows that require authenticated users.

What languages can I use with Cypress?

JavaScript and TypeScript only. If your team uses Python, Java, or C#, you're out of luck. This is a deliberate decision that enables tighter integration with JavaScript tools but limits adoption in mixed-language environments.

How fast are Cypress tests compared to Selenium?

Cypress is faster than Selenium because there's no network overhead between test runner and browser. But Playwright often outperforms both, especially for parallel execution. If you need to run hundreds of tests quickly, Playwright might be better.

Can Cypress handle file uploads and downloads?

Yes, but with limitations. File uploads work through the `cy.selectFile()` command and basic downloads through `cy.readFile()`. For complex file handling, you'll need custom commands or plugins.

What's the learning curve for Cypress?

Pretty low if you know JavaScript. You can write effective tests within hours. The visual test runner and debugging tools make it much easier to learn than Selenium's command-line hell.

Does Cypress work with React, Angular, and Vue?

Yes, it works great with modern JavaScript frameworks. Component testing support lets you test individual components in isolation, which is useful for catching issues that Jest might miss.

Why does Cypress break every time I update Chrome?

Because browser automation is inherently fragile and anyone who tells you otherwise is selling something. Chrome 120 broke half our tests because they changed how `click()` events bubble in certain DOM contexts. Cypress 13.6.1 fixed it 3 days later, but that's 3 days of "tests are broken, don't deploy" emails. I now pin Chrome to version 119 in CI using `--pin-chrome-version=119` and only update after Cypress catches up. Welcome to the joy of depending on other people's software.

Can I test multiple tabs or windows?

Not really, and it's frustrating. Cypress focuses on single-tab testing which covers most use cases but breaks down for complex multi-tab workflows. You'll need workarounds or different tools for those scenarios.

What are Cypress's main limitations?

No Safari support, JavaScript-only, single-origin constraints, and limited multi-tab functionality. The visual test runner requires a display server for CI (though headless mode fixes this). These limitations are deal-breakers for some teams but worth it for the debugging experience.

Currently viewing the AI version

Switch to human version

Cypress E2E Testing: Technical Reference

Overview

Type: Browser automation testing framework
License: MIT Open Source (free core, paid cloud features)
Language: JavaScript/TypeScript only
Architecture: Runs inside browser JavaScript runtime (not remote WebDriver)

Browser Support & Limitations

Supported: Chrome, Firefox
Not Supported: Safari, Internet Explorer
Critical Limitation: No Safari support eliminates full browser coverage
Single Origin Constraint: Cannot test across multiple domains in one test (breaks OAuth flows)

Core Architecture Advantages

No Network Overhead: Direct DOM communication vs WebDriver's HTTP requests
Auto-waiting: Automatic element existence and actionability checks
Real Debugging: Time-travel debugging with browser DevTools integration
Speed: Browser-native execution vs remote control latency

Critical Failure Scenarios

Version Breaking Changes

Cypress 12.2.0: Broke CommonJS configs without warning
Cypress 13.x: Requires Node 16.14+ minimum
ESM Configuration: Existing cypress.config.js may need rename to .mjs or "type": "module" in package.json
Error Pattern: SyntaxError: Cannot use import statement outside a module
Angular Support: Minimum Angular 18.0.0 (drops legacy versions)

Environment Issues

Linux CI (Ubuntu 20.04+): DBus error spam in logs (non-functional, ignorable)
Error Pattern: Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket
Chrome Updates: Browser updates break tests until Cypress catches up (3-day typical lag)
Mitigation: Pin Chrome version in CI: --pin-chrome-version=119

Performance Benchmarks

Test Suite Speed: 8 minutes for 200 tests (vs Playwright 3 minutes)
Parallel Execution: Requires paid Cypress Cloud (vs built-in free alternatives)
Threshold: 500+ tests favor Playwright for speed

Cost Structure

Free Tier

Core Cypress app (unlimited local usage)
Up to 3 users
500 test results/month

Paid Cypress Cloud

Team Plan: $67/month minimum
Real Cost Example: $433/month for 3 projects with 150 tests each (parallel execution)
Cost Comparison: More expensive than typical AWS hosting ($280/month for 50k users)

Resource Requirements

Setup Complexity

Installation: Simple npm install
Learning Curve: Low for JavaScript developers (hours to productivity)
Setup Time: Minimal vs Selenium's driver dependency management

Expertise Requirements

Mandatory: JavaScript/TypeScript proficiency
Debugging: Browser DevTools knowledge
CI Integration: Docker/container experience helpful

Feature Comparison Matrix

Capability	Cypress	Selenium	Playwright	TestCafe
Language Support	JS/TS only	Multi-language	Multi-language	JS/TS only
Browser Coverage	Chrome, Firefox	All browsers	All browsers	All browsers
Parallel Execution	Paid Cloud	Manual setup	Built-in free	Built-in free
Mobile Testing	Emulation only	Real devices	Real + emulation	Emulation only
Setup Complexity	Simple	Complex	Moderate	Simple
Flake Resistance	High	Moderate	High	High

Critical Warnings

What Documentation Doesn't Tell You

Cypress Studio: Experimental record-replay generates buggy code requiring manual cleanup
Component Testing: Only valuable over Jest when CSS-in-JS timing issues matter
Multi-tab Testing: Not supported (single-tab focus only)
File Operations: Limited upload/download capabilities require custom commands

Production Gotchas

Display Server: CI requires headless mode or display server
Memory Usage: Browser instances consume more resources than WebDriver
Network Timing: Still subject to application load timing issues

Decision Criteria

Choose Cypress When:

JavaScript/TypeScript ecosystem
Chrome/Firefox coverage sufficient
Developer experience prioritized over test speed
Budget allows cloud features for team collaboration
Complex debugging requirements (time-travel debugging valuable)

Avoid Cypress When:

Safari support required
Non-JavaScript team
500+ test suites requiring fast parallel execution
Multi-domain testing critical
Budget constraints (cloud features expensive)

Migration Considerations

From Selenium: Expect 50%+ reduction in flaky tests
Time Investment: 2-4 weeks for team proficiency
Breaking Changes: Version updates require testing environment validation
CI Adaptation: Docker images recommended over custom setup

Operational Intelligence

Community & Support Quality

Discord Community: Responsive (12-minute response times for complex issues)
Documentation: Above-average quality with functional search
GitHub Issues: Active but buried solutions in comment threads
Plugin Ecosystem: Most community plugins abandoned or poorly maintained

Real-World Implementation

Success Pattern: API authentication + UI workflows (faster than form-based login)
Failure Pattern: Relying on Cypress Studio for production tests
Debugging Advantage: Visual test runner saves hours vs Selenium's blind debugging
CI Strategy: Pin browser versions, use official Docker images, implement retry logic

Performance Optimization

Component Testing: Catches CSS-in-JS timing issues missed by Jest
Auto-waiting Improvements: Handles modern SPA lazy loading better
Memory Management: Browser instances require adequate CI resources
Parallel Strategy: Evaluate cost-benefit of Cypress Cloud vs Playwright migration for large suites

Useful Links for Further Investigation

Essential Cypress Resources

Link	Description
Cypress Documentation	The official docs are actually decent, unlike most framework documentation that reads like it was written by aliens. Start here for installation and basic concepts. Their search actually works, which puts them ahead of 90% of tech docs.
Cypress Installation Guide	Basic setup instructions. Usually works fine unless you have a weird Node.js version or corporate firewall blocking npm downloads.
Writing Your First Test	The official tutorial is worth doing if you're new to Cypress. Takes about 30 minutes and covers the basics without too much fluff.
Cypress Best Practices	Read this before you write your first real test. It'll save you from common mistakes like using .then() everywhere and writing brittle selectors.
Cypress Cloud Dashboard	The paid cloud service. Useful for teams but gets expensive as fuck. Try the free tier first to see if you actually need the features.
Cypress GitHub Repository	The source code repo. Mainly useful for checking if your issue is already reported or finding workarounds buried in 500-comment issue threads.
Learn Cypress Platform	Interactive courses that are better than most online training. Worth the free registration if you learn better with hands-on exercises.
Cypress Real World App	The best resource for seeing how to structure real tests. When I couldn't figure out how to test file uploads properly, I found their example in 5 minutes and copy-pasted the working code. Saved me 3 hours of trial and error.
Cypress Discord Community	Where you go when the docs don't help and Stack Overflow has 3 answers from 2019 that don't work. Posted a weird selector issue at 1am and got a working solution in 12 minutes from someone who'd hit the exact same bug. The community is actually helpful, unlike most tech Discord servers where asking questions gets you told to "read the docs" by 14-year-olds.
Test Automation University - Cypress Courses	Free courses that are surprisingly good. Skip the "comprehensive" courses - they're outdated by the time you finish them.
Cypress YouTube Channel	Official videos that are occasionally useful. Most of the good content is in community talks, not the marketing videos.
Cypress Blog	Release announcements and case studies. Useful for staying current but skip the marketing fluff.
GitHub Actions Integration	The most common CI setup. Works well once you figure out the caching and parallelization config.
Docker Images	Pre-built Docker images that save you from dependency hell. Use these unless you have specific requirements.
CircleCI Orb	Makes CircleCI setup easier. Still requires tweaking but better than configuring from scratch.
GitLab CI Integration	Decent guide for GitLab setups. The caching examples actually work, unlike most CI documentation.
Cypress Plugin Directory	Community plugins that sometimes work. Most are abandoned or poorly maintained by people who lost interest. Start with the official ones.
Cypress Testing Library	Adds Testing Library selectors to Cypress. Useful if your team already uses Testing Library patterns.
Percy Visual Testing	Visual regression testing that works but costs money. Only worth it if visual changes are a real problem for your team.