# Cypress An open-source platform for end-to-end and component testing of web applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cypress Cloud MCP adds test details, filters, and compact responses DevFeed: [Cypress Cloud MCP adds test details, filters, and compact responses]() Original publisher: [Read original article]() Published: 2026-09-15T16:21:48Z Content type: release Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [MCP](), [Test coverage]() Tags: [cypress](), [mcp](), [release](), [responses](), [september-2026]() ### AI overview Cypress Cloud MCP now provides compact responses by default, new per-spec and per-test tools, filters by run, spec, and test status, and duration data across multiple levels. It also adds deeper links for accessibility and UI coverage reports. ### Source excerpt New tools, more data, smaller responses: what's new in Cypress Cloud MCP as of September 2026. ## Cypress Ambassador Spotlight: Maksym Donets DevFeed: [Cypress Ambassador Spotlight: Maksym Donets]() Original publisher: [Read original article]() Published: 2026-09-10T16:12:22Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [Cloud](), [Automation]() Tags: [ambassador](), [automation](), [bugs](), [cloud](), [community](), [cypress](), [debugging](), [learning](), [qa](), [testing]() ### AI overview An ambassador spotlight featuring Maksym Donets, an Automation QA Engineer who discusses learning, sharing, helping developers debug failed pipelines with Cypress Cloud, and using cy.session() with cy.request() to simplify session handling and speed up tests. He also shares advice for getting started with Cypress and mentions catching bugs with end-to-end testing. ### Source excerpt Welcome back to another edition of our Ambassador Spotlight series, where we shine a light on the Cypress community members who make testing better for everyone through the blogs they write, the talks they give, and the day-to-day help they offer to fellow developers. Curious about the program? You can learn more about it here. This time, we're catching up with Maksym Donets, an Automation QA Engineer with a straightforward philosophy on testing and an even more straightforward philosophy on li ## Build custom workflows with Cypress Cloud Webhooks DevFeed: [Build custom workflows with Cypress Cloud Webhooks]() Original publisher: [Read original article]() Published: 2026-09-08T17:17:31Z Content type: tutorial Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Cloud](), [Automation](), [Messaging](), [GitHub](), [Google Chat](), [Slack]() Tags: [automation](), [cypress](), [github](), [how-to](), [integration](), [integrations](), [mcp](), [slack]() ### AI overview This tutorial introduces Cypress Cloud webhooks for building custom automation workflows. It explains how webhooks can deliver run results and metadata to external systems, trigger actions based on test outcomes, customize notifications, and reduce routine CLI or MCP requests when analyzing runs with AI tools. ### Source excerpt Webhooks are a new addition to Cypress Cloud, supporting more flexible automation workflows beyond what is built into the platform itself. Learn why we've added them and how to get started using them in your project. Integration support in Cypress Cloud Cypress Cloud supports a wide range of integrations out of the box. If you need a GitHub status check for every group of tests in your test run, we've got you covered. Slack and Teams messages when a run fails? That's there, along with deskto ## Cypress Ambassador Spotlight: Marcelo Costa DevFeed: [Cypress Ambassador Spotlight: Marcelo Costa]() Original publisher: [Read original article]() Published: 2026-09-03T16:46:28Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [Automation]() Tags: [ambassador](), [automation](), [community](), [cypress](), [qa](), [tech-lead](), [testing]() ### AI overview This Cypress Ambassador Spotlight introduces Marcelo Costa, a QA Automation Engineer and mentor who shares testing knowledge through community support, articles, and talks. He discusses helping Cypress users, favorite features such as cy.intercept and cy.session, testing practices, and a professional milestone involving a new tech stack. ### Source excerpt Welcome back to our Ambassador Spotlight series! Here, we celebrate the incredible individuals within the Cypress community who go above and beyond, sharing their expertise through insightful blogs, engaging talks, and everyday support. Discover more about our Ambassador program here. This week, we introduce Marcelo Costa, a dedicated QA Automation Engineer and mentor known for tackling real-world testing challenges and sharing those solutions with the world. Join us as we explore what inspired ## Cypress 16: faster tests, starting with HTTP/2 support DevFeed: [Cypress 16: faster tests, starting with HTTP/2 support]() Original publisher: [Read original article]() Published: 2026-09-01T17:28:34Z Content type: release Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [HTTP](), [Chromium](), [Node.js](), [Streaming](), [Vite]() Tags: [chromium](), [ci](), [cypress](), [http](), [node-js](), [streaming](), [tests](), [vite]() ### AI overview Cypress 16 improves end-to-end test performance with HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie and storage commands, and automatic memory management. The release also updates Node.js, Electron, and Chromium versions and removes Cypress.env() as part of its security work. ### Source excerpt 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. ## Implicit Assertions Are More Readable DevFeed: [Implicit Assertions Are More Readable]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-09-01T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [test](), [API](), [properties]() Tags: [api](), [cypress](), [how-to](), [products](), [properties](), [test]() ### AI overview A tutorial on making Cypress API tests more readable by using descriptive assertions, precise value ranges, implicit assertions, and cy-spok for validating nested response objects. ### Source excerpt Recently I saw a Linkedin post that shows "b ## Test Replay now redacts sensitive network data before upload DevFeed: [Test Replay now redacts sensitive network data before upload]() Original publisher: [Read original article]() Published: 2026-08-31T22:12:34Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Authorization](), [data](), [ci](), [Cloud]() Tags: [authorization](), [ci](), [cloud](), [cypress](), [data](), [logs]() ### AI overview Cypress Test Replay now redacts sensitive authorization and credential-like values from captured network logs on the user's machine before uploading them to Cypress Cloud. Redaction is enabled by default, while project-level settings allow teams to disable it. ### Source excerpt Test Replay automatically redacts sensitive values from captured network logs before that data reaches Cypress Cloud. If your team turned Test Replay off in the past because of what your network logs held, this is the change that may let you turn it back on. You keep full CI debugging, and the values you didn't want stored are removed on your machine before Test Replay data is uploaded. Redaction is on by default, and you can turn it off for one project at a time in project settings. What g ## Cypress Ambassador Spotlight: Sehani Chathurangi DevFeed: [Cypress Ambassador Spotlight: Sehani Chathurangi]() Original publisher: [Read original article]() Published: 2026-08-28T16:06:18Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [Test automation](), [selectors]() Tags: [ambassador](), [automation](), [best-practices](), [community](), [cypress](), [knowledge-sharing](), [qa](), [selectors](), [testing]() ### AI overview An Ambassador Spotlight article introduces Sehani Chathurangi, a Senior Software Quality Assurance Engineer, CypressConf speaker, and blogger. She discusses her Cypress advocacy, community knowledge sharing, custom commands, and the use of data-* attributes to create stable selectors in automated tests. ### Source excerpt Welcome back to the Ambassador Spotlight series! Each edition, we shine a light on one of the testers and builders shaping the Cypress community and the people in it sharing their knowledge through blogs, talks, and everyday community support. Curious about the program itself? Learn more here. This week, meet Sehani Chathurangi, a Senior Software Quality Assurance Engineer, CypressConf speaker, and prolific blogger who shares real-world testing solutions with the community. Find out what drew h ## New: Finish Cypress Cloud runs faster with the Run Completion API DevFeed: [New: Finish Cypress Cloud runs faster with the Run Completion API]() Original publisher: [Read original article]() Published: 2026-08-26T18:51:15Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [API](), [CI/CD](), [Accessibility](), [ui]() Tags: [accessibility](), [api](), [continuous-integration](), [cypress](), [testing](), [ui]() ### AI overview The article introduces the Run Completion API for Cypress Cloud. It lets a run finalize immediately after test recording ends instead of waiting for additional test groups, helping workflows that depend on finalized pass/fail results complete sooner. ### Source excerpt Starting now, all Cypress Cloud plans can use the Run Completion API, allowing the Cypress Cloud run to finalize immediately at the end of test recoding, instead of staying open for new tests. Here's why that's important and how it can save you time. Cloud runs can have multiple groups of tests Cypress Cloud runs are often made up of many isolated cypress run groups. These may represent things like: * separate parallel machines * different browsers running the tests * different testing t ## Meet cypress tap: give your AI agent the context the Cypress app shows you DevFeed: [Meet cypress tap: give your AI agent the context the Cypress app shows you]() Original publisher: [Read original article]() Author: Authoring; Not Just Debugging Published: 2026-08-18T19:50:51Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [AI Agent](), [Command-line interface](), [Testing](), [Document Object Model (DOM)](), [aria]() Tags: [ai-agent](), [cli](), [code](), [cypress](), [testing]() ### AI overview Cypress tap is a beta set of CLI commands that lets an AI coding agent drive an already running Cypress open session from the terminal. The agent can run specs, read failures, pin snapshots for time travel, and inspect the application's DOM and accessibility tree while authoring or debugging tests. ### Source excerpt cypress tap is a new set of CLI command to pull Cypress app context into your terminal. It lets AI agent drive a Cypress open session from the terminal, so it can author new tests, extend existing ones, and read failures the way the Cypress app shows them. ## Cypress Ambassador Spotlight: Josué Lobo DevFeed: [Cypress Ambassador Spotlight: Josué Lobo]() Original publisher: [Read original article]() Published: 2026-08-13T14:11:26Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Test automation](), [Testing](), [Open Source](), [selectors]() Tags: [ambassador](), [automation](), [best-practices](), [community](), [content](), [cypress](), [learn](), [open-source](), [selectors](), [testing](), [tutorials](), [verify]() ### AI overview This Cypress Ambassador Spotlight introduces Josué Lobo, describing his work creating Cypress content and helping others learn test automation. He discusses Cy.prompt, custom commands, getting started with open-source projects, and his professional milestones. ### Source excerpt Welcome back to another Ambassador Spotlight! This series is all about introducing you to the amazing testers and builders who make the Cypress community what it is. Our Ambassadors are a huge part of what we do, sharing their expertise through content, events, and community chats to help everyone improve their testing skills. Want to see what the program is all about? Learn more here. This week, meet Josué Lobo, one of the newest members of our Ambassador program. Learn about his biggest profe ## Cypress Security Incident: Status and Response DevFeed: [Cypress Security Incident: Status and Response]() Original publisher: [Read original article]() Published: 2026-08-13T00:47:40Z Content type: news Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [incident](), [Security](), [data](), [ci](), [Git]() Tags: [2026](), [ci](), [cypress](), [data](), [git](), [incident](), [security](), [third-party]() ### AI overview Cypress provides updates on a security incident involving a third-party analytics environment. The article clarifies what recorded test content contained, distinguishes it from unaffected test artifacts, and explains how repository URLs are captured from CI environments, including possible access tokens. ### Source excerpt Last updated: August 17, 2026. This page is our central record for this incident and will be updated as our investigation progresses. Security Incident Update: August 17, 2026 As our investigation continues, we are expanding on two parts of our previous post that have prompted the most questions: what the test data encompasses, and how Cypress records the repository URL associated with your runs. What "test data" encompasses Test data, also referred to as recorded test content, is data as ## How to Stop or Skip Cypress Test Commands DevFeed: [How to Stop or Skip Cypress Test Commands]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-08-07T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Mocha](), [test](), [Code]() Tags: [callback](), [command](), [commands](), [condition](), [cypress](), [object](), [products](), [skip](), [syntax](), [test](), [testing](), [tests]() ### AI overview This tutorial explains three ways to stop or skip Cypress test execution: using Cypress.stop, skipping the current Mocha test, and skipping the remaining commands in the Cypress command queue. It describes the trade-offs of each approach, including whether later tests run and whether completed commands remain visible. ### Source excerpt Let's say you have a long-ish Cypress test and you know a place where it might fail. You want to stop / skip the test commands. ## BrowserStack Newsletter July 2026 DevFeed: [BrowserStack Newsletter July 2026]() Original publisher: [Read original article]() Author: Devanshi Jain Published: 2026-08-05T10:02:29Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Test automation](), [Artificial Intelligence](), [Playwright](), [Selenium](), [Cypress](), [ide](), [Application Performance Management (APM)](), [dashboards](), [Extension](), [Emulator](), [simulator]() Tags: [2026](), [agentic-ai](), [automation](), [automation-testing](), [cursor](), [cypress](), [features](), [ide](), [newsletter](), [product](), [selenium](), [testing]() ### AI overview BrowserStack's July 2026 newsletter announces Test Companion, an agentic AI feature for IDE-based test automation, and BrowserStack Load Testing, which combines backend load generation, real-browser performance, and APM metrics. It also highlights updates for certificates, screenshots, emulators, simulators, mobile browsers, Chrome extensions, audio logs, and diagnostic data. ### Source excerpt Read what's new at BrowserStack in July 2026 - New launches, product features, and more! ## Cypress Ambassador Spotlight: Peter Souza DevFeed: [Cypress Ambassador Spotlight: Peter Souza]() Original publisher: [Read original article]() Published: 2026-08-03T13:48:42Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [Test automation](), [API](), [payload](), [ui](), [React]() Tags: [ambassador](), [api](), [automation](), [community](), [cypress](), [payload](), [react](), [testing]() ### AI overview This Cypress Ambassador Spotlight introduces Peter Souza and discusses his work supporting the Cypress community. He describes Cypress as easy to use and helpful for improving product reliability, shares pair programming and problem-solving practices, highlights cy.intercept for waiting on APIs and modifying payloads, and recommends test isolation as a best practice. The article also mentions his interests in React.js, music, exercise, and outdoor activities. ### Source excerpt It's time for another Ambassador Spotlight, a series introducing you to the testers, builders, and problem solvers who make up the Cypress community. This is where people in test automation come to share their experience, learn something new, and find others who care about software quality as much as they do. Our Ambassadors are a driving force here, bringing real depth to the craft of testing and championing quality across the applications they build and the teams they work with. Through conten ## Handling Application States and Retries in Cypress End-to-End Tests DevFeed: [Handling Application States and Retries in Cypress End-to-End Tests]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-07-28T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [test](), [App]() Tags: [api](), [can](), [cypress](), [errors](), [flaky](), [plugin](), [products](), [retry](), [test](), [testing](), [tests]() ### AI overview This tutorial explains how to design Cypress end-to-end tests for loading, empty, and error states. It recommends detecting known error states immediately and using in-place retries with cypress-recurse when appropriate, instead of relying only on whole-test retries. ### Source excerpt Imagine a typical application that loads some data. The app starts in the initial state, starts loading, then one of 3 possible states ar ## Cypress Ambassador Spotlight: Boris Selivanov DevFeed: [Cypress Ambassador Spotlight: Boris Selivanov]() Original publisher: [Read original article]() Published: 2026-07-24T13:43:32Z Content type: opinion Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Test automation](), [Testing](), [selectors](), [race-condition](), [Network](), [npm]() Tags: [ambassador](), [automation](), [cypress](), [flaky](), [how-to](), [npm](), [race-condition](), [selectors](), [testing]() ### AI overview This Cypress Ambassador Spotlight presents Boris Selivanov's advice on sharing reusable testing patterns, choosing stable selectors, and building scalable test automation. It highlights cy.intercept() for controlling network traffic and reducing flaky tests, recommends retry-ability and aliases instead of arbitrary cy.wait(ms), and suggests starting with a real application test after installing Cypress. ### Source excerpt What motivates you to be a Cypress Ambassador? I see being an Ambassador as the ultimate form of asynchronous collaboration. My goal is to share things that move the needle for other engineers. By comparing how different teams solve the same testing problems, we can turn isolated project victories into shared wins. How do you currently help others that are either using Cypress or interested in using Cypress? I'm the person teammates ping when a test goes flaky or they're not sure how to appro ## Read your Cypress Test Replay from the terminal, and hand it to your agent with the Cypress Cloud CLI DevFeed: [Read your Cypress Test Replay from the terminal, and hand it to your agent with the Cypress Cloud CLI]() Original publisher: [Read original article]() Published: 2026-07-23T21:46:47Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Command-line interface](), [JSON](), [ai-coding](), [ci](), [Cache](), [Cloud]() Tags: [ai-coding](), [cache](), [ci](), [claude-code](), [cli](), [codex](), [copilot](), [cypress](), [json]() ### AI overview The Cypress Cloud CLI brings Cypress Cloud run data and Test Replay into the terminal as structured JSON. It supports failed-run triage, inspection of test errors and timelines, CI integration, and use by shell-based agents such as Claude Code, Codex CLI, and Copilot CLI. ### Source excerpt The Cypress Cloud CLI, published as @cypress/cloud, brings your run data and Test Replay into the terminal as structured JSON. Triage a failed run yourself, wire the commands into CI, or hand them to a shell-based agent that can read the full failure context without you in the middle. ## Cypress Ambassador Spotlight: Javier Flores DevFeed: [Cypress Ambassador Spotlight: Javier Flores]() Original publisher: [Read original article]() Published: 2026-07-16T21:08:08Z Content type: opinion Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [Cucumber](), [Bootcamp](), [selectors](), [debugging](), [Automation]() Tags: [ambassador](), [automation](), [community](), [cypress](), [debugging](), [flaky](), [learning](), [projects](), [selectors](), [testing]() ### AI overview This interview highlights Javier Flores's work as a Cypress Ambassador, QA Automation Lead, mentor, and bootcamp instructor. It discusses practical Cypress testing, Cucumber exercises, interactive time-travel debugging, automatic waiting, deterministic tests, stable selectors, and beginner-friendly end-to-end testing practices. ### Source excerpt What motivates you to be a Cypress Ambassador? I want to help grow a strong, practical testing community around Cypress. I show people working code and let them build confidence by doing. That's the same philosophy behind the bootcamp I run: everyone leaves with their own repo, not just notes. How do you currently help others that are either using Cypress or interested in using Cypress? I mentor teammates and collaborate closely with developers and product owners to improve testing practices ## The Electron browser is being deprecated in Cypress DevFeed: [The Electron browser is being deprecated in Cypress]() Original publisher: [Read original article]() Published: 2026-07-10T15:15:58Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Electron](), [Testing](), [browsers](), [Chromium](), [Continuous integration]() Tags: [browser](), [browsers](), [chrome](), [chromium](), [continuous-integration](), [cypress](), [edge](), [firefox](), [testing]() ### AI overview Cypress is deprecating its bundled Electron browser starting with Cypress 16.0.0 and plans to remove it in a future major version. The article explains that tests can produce inconsistent results in Electron compared with users' installed browsers, and recommends moving local and CI runs to installed browsers such as Chrome for Testing, Chrome, Firefox, or Edge. ### Source excerpt We're deprecating the Electron browser in Cypress, starting in Cypress 16.0.0, with removal in a future major version. After years of seeing inconsistent results between Electron and the browsers people actually use, we are standardizing on installed browsers for more reliable test results. ## BrowserStack Newsletter May 2026 DevFeed: [BrowserStack Newsletter May 2026]() Original publisher: [Read original article]() Author: Devanshi Jain Published: 2026-06-24T04:07:56Z Content type: news Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Application Performance Management (APM)](), [dashboards](), [Artificial Intelligence](), [Mobile Testing](), [iOS](), [Cypress](), [Figma](), [Robot Framework](), [Storybook]() Tags: [2026](), [ai](), [ai-agents](), [features](), [launch](), [metrics](), [newsletter](), [performance](), [product](), [testing]() ### AI overview BrowserStack's May 2026 newsletter highlights a QA Leadership Summit session on building trustworthy AI testing workflows, the launch of BrowserStack Load Testing, and product updates across mobile testing, visual review, accessibility, scanning, and automation. The Load Testing platform combines backend load generation, real-browser performance, and APM metrics, using AI agents to correlate data and identify root causes. ### Source excerpt Read what's new at BrowserStack in May 2026 - New launches, product features, and more! ## Preventing Cypress Test Failures When Reloaded Elements Detach from the DOM DevFeed: [Preventing Cypress Test Failures When Reloaded Elements Detach from the DOM]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-06-17T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Document Object Model (DOM)](), [navigation]() Tags: [blog-post](), [component](), [cypress](), [demo](), [how-to](), [navigation](), [products](), [repo](), [testing](), [verify]() ### AI overview This tutorial explains why Cypress end-to-end tests can fail when client-side navigation updates the page after a command has found an element. It demonstrates how delayed rendering can leave an old element attached to the test subject and recommends waiting for the expected component or DOM state before continuing the command chain. ### Source excerpt Have you ever encountered end-to-end test error "... failed because the page updated as a result of this command, but you tried to c ## How to Test Negative States and Cached Network Requests with Cypress DevFeed: [How to Test Negative States and Cached Network Requests with Cypress]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-06-10T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Testing](), [Cypress](), [Network]() Tags: [cypress](), [how-to](), [network](), [network-testing](), [products](), [test](), [testing](), [web]() ### AI overview This article explains how to test negative states reliably in Cypress. It recommends confirming that the application has reached a known final state before asserting that a network request did not occur, or using a timeout when no completion state is available. ### Source excerpt Let me get back to the testing of negative states one ## Breakpoint 2026: Highlights from Day 3 DevFeed: [Breakpoint 2026: Highlights from Day 3]() Original publisher: [Read original article]() Author: Shweta Chhillar Published: 2026-06-02T13:03:05Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [AI Agent](), [Model Context Protocol](), [Test automation](), [MCP](), [LangChain](), [observability](), [Retrieval Augmented Generation (RAG)](), [Playwright](), [Cypress](), [debugging](), [Selenium]() Tags: [2026](), [agent](), [ai](), [automation](), [breakpoint](), [ci-cd](), [debugging](), [github](), [github-copilot](), [langchain](), [mcp](), [model-context-protocol](), [observability](), [qa](), [rag](), [testing](), [vscode]() ### AI overview A recap of Breakpoint 2026 Day 3 covering practical masterclasses and lightning talks on AI-driven test generation, non-deterministic testing, MCP-powered QA workflows, automated AI evaluation, and production testing practices. ### Source excerpt All sessions, masterclasses, and lightning talks from Breakpoint 2026 Day 3, covering AI agent testing, test automation with LangChain and CrewAI, MCP-powered QA workflows, Playwright network interception, non-deterministic testing, and building production-grade AI systems. [Next page]()