Cypress Documentation Source

UI Coverage is a feature in Cypress Cloud that provides a visual map of which interactive elements (buttons, inputs, links, and controls) your Cypress tests exercise and which they miss.

Unlike code coverage, which tracks which lines of source code were executed, UI Coverage measures whether the actual user-facing interactive surface of your application is being tested. It works by analyzing the DOM snapshots captured by Test Replay during your recorded runs.

Key benefits include:

• Visualizing untested surface: View a single coverage score and per-view scores to rank pages by risk.
• Identifying exact gaps: Locate specific untested elements via inspectable DOM snapshots.
• Discovering missing flows: Find untested links that lead to pages your suite never visits.
• Automating gap closure: Use Test Generation or the Cypress Cloud MCP to create tests for missing coverage.
• CI/CD Integration: Use the Results API to fail CI or block pull requests when coverage drops.

Cypress is a quality platform designed for modern web applications, providing tools for end-to-end, component, and accessibility testing. The platform scales from local development to CI/CD environments through several distinct products:

• Cypress App: A free, open-source, locally installed application used for writing and running tests.
• Cypress Cloud: A paid service designed for CI integration. It provides test recording, analytics, flaky test management, and smart orchestration (parallelization) to make CI runs faster and more reliable.
• UI Coverage: A premium solution that provides a visual overview of test coverage across all pages and components, identifying untested areas of the application.
• Cypress Accessibility: A premium solution that performs accessibility checks during normal test runs to detect barriers for users with disabilities without requiring extra code changes or performance penalties.

Pricing & Availability

• Cost: Cloud MCP is free for all Cypress Cloud plans, including the Starter plan.
• Availability: Generally available as of May 20th, 2026.
• Requirements: No minimum Cypress App version is required.

Usage Limits

• Rate Limit: 100 tool requests per hour across all plans.
• Data Retention: Data availability follows your existing Cypress Cloud test recording and retention policies.
• Increases: Contact support@cypress.io to request higher limits.

Security & Privacy

• Privacy: Cypress cannot see your AI conversation, chat history, or context window. Cypress only receives the specific inputs required for a tool call (e.g., getRuns(projectId: 100, runNumber: 45, limit: 10)).
• Data Usage: Cypress does not train LLMs on your data. Test results, stack traces, and replay links are used only to fulfill the specific request.
• Access Control:
  • Read-only: Cloud MCP cannot modify test code or delete runs.
  • User-scoped: The agent can only access data that your specific Cypress Cloud user has permission to see.
  • Opt-in: The integration must be enabled in the Cypress Cloud Integrations page.

The Cypress App is the local development tool designed to shorten the testing loop. Key features include:

• Time Travel: Hover over commands in the Command Log to see snapshots of the application at each step.
• Debuggability: Use Developer Tools and readable error messages/stack traces to debug failures.
• Automatic Waiting: Cypress automatically waits for commands and assertions to pass before moving on, eliminating the need for manual wait or sleep commands.
• Spies, Stubs, and Clocks: Control and verify the behavior of functions, timers, and server responses.
• Network Traffic Control: Stub and test network requests and edge cases without a live server.
• Cypress Studio & Studio AI: Record user interactions to generate E2E tests and use AI to recommend assertions.
• Cross Browser Testing: Run tests in Firefox, Chrome, Edge, and Electron locally or in CI.

Enterprise Reporting organizes insights into several specialized tabs to help govern your test program across all projects in an organization:

• Overall Usage: Tracks test utilization, concentration across projects, and trends over time.
• Test Results: Provides status rates (pass/fail) at three levels of granularity: runs, specs, and individual tests.
• Test Setup: Monitors configuration metrics, such as the ratio of end-to-end tests to component tests, suite size changes, use of Cypress smart orchestration, and Cypress version distribution.
• Test Execution: Analyzes environment details, including browser usage consistency, execution time changes, and average failure/error rates.
• Flaky Tests: Tracks flaky test occurrences and rates. Using the flake rate (% of runs that are flaky) allows for direct comparison between projects regardless of run volume.
• UI Coverage: Monitors trends in UI coverage scores to detect improvements or drift.
• Cypress Accessibility: Tracks accessibility score trends, severity breakdowns, and rule-specific violations (e.g., weekly average violations per rule).
• Raw Data: Provides examples of granular data that can be used for programmatic integration.