September 2026 Summaries

No summary generated yet.

Cypress Cloud MCP has introduced compact default responses, new tools for retrieving per-spec and per-test results, and filters that let coding agents focus on specific runs, specs, or test statuses. The update adds duration data across runs, specs, tests, and individual attempts, plus commit author and CI build identifiers, Test Replay links, and deep links for accessibility and UI coverage reports. These capabilities support workflows such as producing release reports, identifying slow tests, distinguishing flaky failures from consistent ones, investigating errors through replay timelines, creating Jira tickets for serious accessibility issues, and auditing skipped or pending tests. The release is already available to all connected Cypress Cloud MCP users without requiring updates.

Cypress Ambassador Maksym Donets, an Automation QA Engineer, is featured for his focus on learning, sharing knowledge, and helping developers debug failed pipelines through Cypress Cloud. He identifies cy.session() as his preferred Cypress feature because it simplifies login and user-switching sessions while improving test speed, and he pairs it with cy.request() as a favored practice for faster test execution. Donets is particularly proud of catching nearly all bugs through end-to-end testing, advises newcomers to begin by searching for Cypress installation instructions, and enjoys CrossFit outside work.

Cypress Cloud has introduced webhooks to let teams send completed test-run results and related metadata, including tags, branches, and commit information, directly to custom endpoints for automation and integrations beyond its built-in GitHub, Slack, Teams, Jira, notification, and reporting capabilities. Webhooks can trigger workflows such as customized messaging, Google Chat notifications, conditional CI test reruns, and deeper analysis through Cypress AI tools or local Cypress App integrations, while reducing repeated CLI, MCP, and routine API requests. Available on all paid Cypress Cloud plans, webhooks currently support the run.completed event and can be configured by project administrators and owners; teams with parallel or grouped runs may instead use the Run Completion API when they need notification after all expected groups finish. Cypress plans to expand webhook events and payloads based on user feedback.

Cypress’s Ambassador Spotlight highlights Marcelo Costa, a QA Automation Engineer and mentor who contributes to the community through Reddit and Telegram support as well as Dev.to articles on topics such as global hooks, cy.prompt(), and Excel validation. Costa cites Cypress’s active community as a key motivation for becoming an Ambassador and identifies cy.intercept as his favorite feature because it can validate, alter, or mock network requests while coordinating frontend testing through aliases and cy.wait. His preferred best practice is using cy.session with cacheAcrossSpecs enabled to reuse login sessions across test specifications. He encourages newcomers to learn through whatever format suits them, prioritize hands-on practice, and view failure as part of the learning process. Outside work, Costa enjoys films, language learning, swimming, vinyl music, travel, and exploring restaurants, and he is particularly proud of recognition from a former Tech Lead for his automation testing skills after adopting a new technology stack.

Cypress 16 focuses on accelerating and stabilizing end-to-end testing through default HTTP/2 support in Chromium-based browsers, zero-delay typing, a faster visibility-checking algorithm, retryable cookie and storage queries, and automatic browser memory management for long-running suites. The release upgrades its underlying platform to Node.js 24, Chromium 146, Electron 41, Vite 8, and newer Angular support, while enhancing security by replacing browser-exposed Cypress.env() with cy.env() for sensitive values and Cypress.expose() for non-sensitive configuration. It is a breaking release that removes or deprecates several APIs and capabilities, including cy.exec(), cy.end(), CoffeeScript support, certain runtime configuration changes, older component-testing framework versions, and eventually Electron support, though migration alternatives are provided. Cypress recommends using its migration guide and AI-assistant prompts to assess compatibility, update dependencies, and modify affected code, while also highlighting numerous Cypress 15 improvements in AI-assisted testing, tooling, performance, memory handling, and bug fixes for teams not yet ready to upgrade.