---
title: "cy.blog()"
url: "https://www.cypress.io/blog/author/jennifer"
description: "Read every Cypress blog post by Jennifer Shehane, newest first, from testing techniques to Cypress product news."
---

# cy.blog()

Releases, AI-assisted testing, and quality guides from the Cypress team. See what changed, whether it affects you, and how teams ship with confidence.

## Articles written by Jennifer Shehane

[How to connect Claude Code to Cypress Claude Code writes better Cypress tests when it knows your conventions, can check its work in a live session, and can see your run history. Learn how to set up Cypress AI Skills, Cloud MCP, and cypress tap, and which pieces your team needs. Read more](/blog/how-to-connect-claude-code-to-cypress)

[Find elements the way your users do with cy.getByRole() Cypress 16.2.0 adds cy.getByRole(), a built-in query that finds elements by role and accessible name. By default, it matches only native elements, so your tests catch a <button> swapped for a <div role="button">. Here’s why that matters, and how to move off Cypress Testing Library. Read more](/blog/find-elements-the-way-your-users-do-with-cy-getbyrole)

[Cypress 16: faster tests, starting with HTTP/2 support Cypress 16 goes after slow test suites from every angle: HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie commands, and automatic memory management. Most of it arrives without editing a single test. Here's what changed, why, and how to upgrade. Read more](/blog/cypress-16-faster-tests-starting-with-http2-support)

[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. Now with expanded defaults, accurate flaky test status, and direct Test Replay links. Read more](/blog/how-the-cypress-cloud-errors-tab-helps-you-triage-faster)

[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. Here's what changed, what gaps remain, and how to adjust the setting if your project needs it. Read more](/blog/cypress-test-replay-now-captures-canvas-elements-by-default)

[Write Cypress tests in plain English: AI-powered test automation is now in beta Writing tests has always required a translation step. You know exactly what the test should do. Getting that into code is the part that slows everything down. You stop mid-flow to find the right selector, check whether the element has a stable attribute, write the command, run it, fix it, run it again. By the time the test exists, you have lost the thread of whatever you were actually building. cy.prompt was built to remove that step. Describe what you want in plain English and Cypress handles Read more](/blog/write-cypress-tests-in-plain-english-ai-powered-test-automation-is-now-in-beta)

[cy.prompt can now wait for network requests cy.prompt now supports waiting for network requests by referencing aliases you've already defined with cy.intercept. You can keep your test instructions in one place, without breaking out of the prompt block to insert manual waits. Read more](/blog/cy-prompt-can-now-wait-for-network-requests)

[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. This post covers what changed and how sensitive data in the DOM is handled automatically. Read more](/blog/how-cy-prompt-generates-cy-contains-cy-press-and-handles-sensitive-data)

[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. Read more](/blog/fix-cypress-ci-failures-caused-by-no-spec-files-found)

[What’s new in cy.prompt for AI testing in Cypress We’ve made a series of focused updates to cy.prompt based on how teams are using AI in real Cypress test suites. Learn what’s new, why it matters for reliability and readability, and what improvements are coming next. Read more](/blog/whats-new-in-cy-prompt-for-ai-testing-in-cypress)

[AI self-healing in Cypress: reliable tests with full visibility cy.prompt brings transparent self-healing to Cypress tests, adapting to UI changes while showing exactly what healed and why. Get clear logs, reliable tests, and the option to generate code once and commit it for full control in CI. Read more](/blog/ai-self-healing-in-cypress-reliable-tests-with-full-visibility)

[Interact and Assert on Shadow DOM in Cypress Studio Cypress Studio Now Supports Shadow DOM Interaction and Assertions Read more](/blog/interact-and-assert-on-shadow-dom-in-cypress-studio)

[AI testing in Cypress: scroll elements into view with cy.prompt Cypress now supports AI-powered scrolling in cy.prompt. Write natural language instructions like “scroll to Dec 7” and let Cypress handle the rest. See how AI-driven testing is evolving in Cypress. Read more](/blog/ai-testing-in-cypress-scroll-elements-into-view-with-cy-prompt)

[Clearer command logs: Hide HTTP requests in the Cypress App When running Cypress tests, your Command Log can fill up fast, especially when your app makes lots of network calls. While these entries are helpful when you’re debugging, they can also add noise when you just want to focus on the test flow. That’s why we’ve added a new option to the Cypress App to hide HTTP requests. A cleaner view in the Command Log When you don’t need to inspect network calls, you can now hide them directly from the Command Log. Deselect the “Show HTTP Requests” toggle i Read more](/blog/clearer-command-logs-hide-http-requests-in-the-cypress-app)

[Cypress Studio: No-Code Test Generation Now Built In Cypress Studio now ships by default in Cypress 15.4.0. Record and generate end-to-end tests without writing code. Try the built-in test recorder today. Read more](/blog/cypress-studio-no-code-test-generation-now-built-in)

[More keys, more power: cy.press() got an upgrade in Cypress 15.1.0 When we first introduced cy.press() in Cypress 14.3.0, it unlocked something our community had been asking for: a way to send real, native keyboard events to the browser. The initial release focused on one of the most important keys for accessibility testing: Tab, so you could confidently verify focus management and keyboard navigation. With Cypress 15.1.0, we've expanded support far beyond Tab. You can now use cy.press() to simulate letters, numbers, special characters, and a wide range of nam Read more](/blog/more-keys-more-power-cy-press-got-an-upgrade-in-cypress-15-1-0)

[Cypress 15: The foundation for what’s next Cypress 15 is here, and while this release might look mostly foundational on the surface, it’s setting us up for something much bigger. We’ve made changes across the board to improve stability, clear out legacy support, and upgrade core parts of the platform. But the big story is this: Cypress Studio is evolving. A new era for Cypress Studio If you've used Cypress Studio before, you know the promise. You can click through your app and record tests automatically. In Cypress 15, we’ve taken tha Read more](/blog/cypress-15-the-foundation-for-whats-next)

[cy.prompt frequently asked questions cy.prompt() is now available to everyone. For full details on how cy.prompt() works and how to enable it, check out our docs. We’ve received a ton of excitement (and a bunch of questions) about cy.prompt, so we wanted to take a moment to share some answers and give a quick update on where things stand. If you haven’t already, check out Brian Mann’s full demo - it answers many of the early questions we’ve seen. So, let’s dive in. What's the difference between cy.prompt and an MCP server? Cy Read more](/blog/cy-prompt-frequently-asked-questions)

[Automating Tests with Natural Language: Highlights from Frontend Nation 2025 cy.prompt() is now available to everyone. For full details on how cy.prompt() works and how to enable it, check out our docs. At Frontend Nation 2025, Cypress founder Brian Mann took the stage to explore the future of end-to-end testing using natural language. His talk, “Lessons from the AI Battlefield,” cut through the hype and showed what it actually takes to automate browsers with plain English and how Cypress is doing it differently. Update: The recording of Brian Mann's Frontend Nation ta Read more](/blog/automating-tests-with-natural-language-highlights-from-frontend-nation-2025)

[Press tab in your tests: Introducing cy.press() Tab key testing is here with cy.press()! This long-requested feature gives you the ability to trigger real native keyboard events in your tests, starting with support for the Tab key. This is a big step toward improving accessibility testing and ensuring smooth keyboard navigation experiences in your application. Why we built cy.press() Historically, Cypress users have relied on cy.type() to simulate keyboard input. While cy.type() is great for typing characters in typeable elements, it does Read more](/blog/press-tab-in-your-tests-introducing-cy-press)

[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. Why we built Cypress.stop() Testing should be efficient, predictable, and provide feedback as fast as possible. Whether you want to stop tests immediately upon failure or skip execution based on some other condition, Cypress.stop() provides faster feedback and the flexibility you need. How Cypress.stop() works With a single command, Cypress.stop() halts execution within th Read more](/blog/introducing-cypress-stop-a-simple-way-to-halt-test-runs)

[Announcing Cypress Support for Firefox over WebDriver BiDi We’re thrilled to announce that Cypress now supports automating Firefox using the new WebDriver BiDi protocol! This milestone, released in Cypress 14.1.0, reflects our ongoing commitment to staying ahead with the latest browser versions in the testing industry. What Is WebDriver BiDi? WebDriver BiDi (Bidirectional) is an emerging, cross-browser automation protocol that combines the best aspects of WebDriver Classic and the Chrome DevTools Protocol (CDP). With bi-directional communication buil Read more](/blog/announcing-cypress-support-for-firefox-over-webdriver-bidi)

[Cypress 14 is Here — 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. Here’s what’s new: ✨ Key Highlights * Expanded Component Testing Support: Cypress now works with the latest versions of React, Angular, Next.js, Svelte, and Vite — with improved performance for component test runs. * Chrome document domain fixes: Chrome’s deprecation of document.domain is handled seamlessly. Use cy.origin() for cross-subdomain naviga Read more](/blog/cypress-14-is-here-see-whats-new)

[Takeaways from Write the Docs + Open Help Cincinnati This weekend I attended Write the Docs + Open Help Cincinnati. Write the Docs + Open Help is an event that brings together documentation contributors to share and learn from one another. The weekend included a day of talks and day of unconference sessions and lightning talks. It also included three days of documentation sprints led by Open Help, which I was unable to attend. I work as the main contributor and maintainer of Cypress’ documentation. My background is in web design and more recently Read more](/blog/takeaways-from-write-the-docs-cincinnati)

[10 ways we improved our docs As part of our strategy towards going open source, we wanted to make several improvements to our documentation. There were a few problems we wanted to address: 1. There was no clear explanation of why you would want to use Cypress. 2. There were no clear “Getting Started” guides that introduced you to Cypress. 3. Most API commands were missing explanations of critical core concepts. 4. We found many users were confused by the Cypress ✨ magic ✨. 5. Our users asked the same questions o Read more](/blog/10-ways-we-improved-our-docs)