Cypress Commands Overview
cy.get()cy.find()cy.debug()cy.visit()cy.mount()cy.click()cy.type()cy.pause()cy.within()cy.contains()cy.each()cy.dblclick()cy.filter()cy.eq()cy.clearCookie()cy.end()
Cypress Cloud MCP is Generally Available
Today, Cypress Cloud MCP is generally available!
When we launched Cloud MCP in beta two months ago, we had a hypothesis: developers shouldn't have to copy-paste stack traces into a chat window to get their AI assistant to help them debug. Cypress Cloud already had all the context their assistant needed. We just needed to close the gap.
The response told us the hypothesis was right. In the 9 weeks since beta, over 500 organizations connected, and more than 1,000 developers have used it to query.
How the Cypress Cloud Errors Tab Helps You Triage Faster
The Errors tab in Cypress Cloud groups test failures by error type so you can tell if you have one problem or forty.
Cloud MCP Now Includes Cypress Accessibility
Use AI agents to take quick, actionable next steps on accessibility issues.
Cypress AI Skills: Get More From Your AI Coding Assistant
AI coding tools can write Cypress tests. What they tend to struggle with is writing them well.
Ask an AI assistant to generate a Cypress test and you'll probably get something that runs. But look closer and you'll find CSS class selectors instead of data-cy attributes, cy.wait(3000) instead of network aliases, and no awareness of the custom commands your team already built.
Cypress Test Replay Now Captures Canvas Elements by Default
Canvas capture is now on by default in Test Replay for all projects in Cypress Cloud. If your tests interact with canvas elements, you no longer need to contact Cypress to enable capture.
Cypress Cloud: Give Your AI Assistant Access to Your Test Runs
We are releasing the beta of Cloud MCP — a remote Model Context Protocol (MCP) server that connects AI coding assistants and AI Agents directly to Cypress Cloud.
If you've ever finished a CI run, watched it go red, and then spent the next ten minutes copy-pasting stack traces into a chat window, you know exactly what problem we're solving.
Introducing Studio AI: Stronger Validation, Less Friction
A passing test run does not always equal release confidence.
Confidence comes from knowing your tests validate what users actually experience. Not just that a flow executed, but that the UI state changed appropriately, the right text appeared, and element visibility updated as expected.
How cy.prompt Generates cy.contains, cy.press, and Handles Sensitive Data
cy.prompt now supports text-based targeting via cy.contains, keyboard interactions through cy.press, and non-existence assertions using visible content.
Fix Cypress CI Failures Caused by No Spec Files Found
Stop Cypress from failing your CI build when no spec files are found. Learn when to use --pass-with-no-tests, when to leave it off, and what else shipped in 15.11.0.
Environment Variable Access in Cypress v15.10.0+: Migrating to cy.env() and Cypress.expose()
Starting in Cypress 15.10.0, Cypress.env() is deprecated and will be removed in Cypress 16.0.0. This change is driven by the way Cypress.env() hydrates all Cypress environment values into the browser context, including values a test may never read.
What's New in Cypress Accessibility?
Over the last year, we've delivered some of the most requested features by current Cypress Accessibility customers, and extended the range of use cases and environments we support.
Introducing Cypress.stop(): A Simple Way to Halt Test Runs
We’re thrilled to announce Cypress.stop(), a powerful command that allows you to stop test execution programmatically.
Just Launched: Accessibility Branch Review - Spot New Issues in Seconds
This comes up because everybody's been through a certain kind of pain in their accessibility remediation work, where fixing one issue can expose, or even directly cause, another problem.
Announcing Cypress 14 — See What's New!
We’re excited to announce the release of Cypress 14! This update has improvements and updates to make your testing experience even smoother.