July 2026 Summaries

Boris Selivanov, a Cypress Ambassador, views his role as a means of promoting collaborative problem-solving among engineers by sharing strategies for overcoming testing challenges. He assists colleagues by providing scalable solutions rather than temporary fixes, emphasizing the importance of using stable selectors in testing. His favorite Cypress feature is cy.intercept(), which allows testers to manage network traffic, ensuring tests are reliable and repeatable. He advocates against using arbitrary wait times, preferring the efficiency of retry-ability and cy.intercept() aliases. Outside work, Boris enjoys watching FIFA World Cup matches, and professionally, he takes pride in building and scaling automation frameworks and facilitating training sessions to empower teams in test automation. For newcomers to Cypress, he recommends skipping tedious configurations and diving straight into testing with real applications to quickly grasp the framework's potential.

The blog post discusses the introduction of the Cypress Cloud CLI, a tool that allows developers to access and manage their Cypress Cloud run data directly from the terminal, enhancing the efficiency of test triage processes. By converting manual investigation processes into structured JSON commands, the CLI provides detailed insights into test failures, including error messages, stack traces, and Test Replay timelines, which can be seamlessly integrated into workflows with shell-based agents like Claude Code and Codex CLI. This innovation reduces the bottleneck between identifying and fixing test failures by enabling developers and their AI agents to quickly access and analyze the relevant data, thereby streamlining the troubleshooting process. Additionally, the CLI is designed to work in conjunction with other Cypress Cloud tools, such as the Data Extract API and Cloud MCP, to provide comprehensive access to test data and enhance collaboration between humans and AI in debugging processes. The setup is straightforward, and the tool is available on all Cypress Cloud plans, encouraging users to incorporate it into their workflows to accelerate the triage loop.

Javier Flores, a Cypress Ambassador, is dedicated to building a robust testing community by emphasizing hands-on learning and practical application. He mentors colleagues and conducts an online bootcamp where participants gain practical experience with Cypress and Cucumber by creating their own repositories. Flores particularly values Cypress's interactive time-travel debugging and automatic waiting features, which simplify testing by eliminating guesswork and timing issues. He advocates for writing small, independent, deterministic tests and using stable selectors to maintain test suite reliability. Outside of professional pursuits, Flores enjoys traveling, movies, and spending time with his family, along with experimenting with automation projects. As a QA Automation Lead, he takes pride in establishing a successful automation practice and enjoys seeing similar success in his bootcamp students. For newcomers to Cypress, he recommends starting with basic installations and gradually exploring core commands and features to build understanding.

Cypress has announced the deprecation of the Electron browser in its testing framework, starting with version 16.0.0, due to inconsistencies that arise from running tests in Electron compared to installed browsers like Chrome, Firefox, or Edge. The decision aims to provide more reliable test results by ensuring that tests reflect the actual behavior of applications in the browsers used by end users. The bundled Electron browser, previously included to simplify initial setup, is now considered outdated as setting up browsers in various environments has become more straightforward. The Electron browser's inconsistencies, such as lagging behind in Chromium updates and differing behavior from real Chrome, have led to challenges in debugging and maintaining test reliability. The Cypress team advises users to transition to installed browsers to avoid disruptions, providing guidance on configuring local and CI environments accordingly. The change is intended to align testing practices with user experiences, ensuring that testing outcomes are more predictable and trustworthy.

In a blog post by Emily Wisniewski, the focus is on optimizing the context footprint of Cypress when used with AI coding assistants like Claude Code. Typically, test outputs from Cypress remain in the conversation context and are re-sent on every API call, leading to unnecessary costs. Through benchmarking, it was discovered that using specific Cypress configurations could reduce the context footprint by approximately 75%. This was achieved by changing the mocha reporter to the dot reporter and quieting the Cypress CLI output, which significantly reduced the number of cache_write tokens needed. While the immediate cost savings per session might seem negligible, the cumulative savings become significant over longer sessions with extensive test suites. The author suggests encoding these configurations as a rule in the agent's settings to ensure consistent application without manual intervention, thereby minimizing recurring costs and optimizing token usage in AI-supported testing environments.

Tatiana Mikhaleva, the Founder of DevOps.Pink and a Cypress Ambassador, is dedicated to making complex cloud-native tools more accessible and bridging the gap between developers and QA by promoting reliable automation. Her efforts include creating visual guides for integrating Cypress into CI/CD pipelines and mentoring underrepresented groups in tech. Mikhaleva finds time-travel debugging to be a revolutionary Cypress feature for visual learners, and she advocates for testing behavior rather than implementation to create resilient test suites. Outside of her professional work, she enjoys hiking, design, and curating the aesthetic of her platform. Her proudest professional milestone is transforming fear into confidence in engineers through her community, DevOps.Pink, and she encourages new Cypress users to engage with automation directly to experience its benefits.

cy.prompt, initially an experimental feature, is now becoming a core component of Cypress Cloud starting August 1, 2026. It enables teams to write tests in plain language, which are then converted into Cypress code, and includes a self-healing capability that adapts tests to UI changes, reducing maintenance time. Over 2,000 teams have adopted cy.prompt, and its usage will be measured in executions with the new plan, where each command counts as one execution regardless of the steps included. While paid plans offer flexibility without unexpected charges, free plans pause new cy.prompt authoring and AI self-healing once the execution limit is reached until the next billing cycle. Users can monitor their usage through the Billing & Usage page and set alerts to manage their allocations effectively.

Anvesh Puli, a Cypress Ambassador, is driven by a passion for the "build and break" cycle, using challenges in testing and automation as opportunities to evolve the tool and solve community issues. He actively engages with users through one-on-one sessions, demos, and online platforms like Discord and LinkedIn, serving as a resource for those looking to enhance their testing skills. His favorite Cypress feature is the Selector Playground, which streamlines the process of grabbing UI elements, while his best practice is understanding commands thoroughly instead of relying on copy-pasting. Outside of his professional life, Puli enjoys adrenaline-inducing sports, outdoor adventures, and filmmaking. He takes pride in his professional achievements, such as winning the IBM Tech 2023 award and contributing to software developments in AI and Kubernetes. For newcomers to Cypress, he recommends starting with "npm install cypress" and encourages learning through experimentation. His favorite saying emphasizes persistence and consistency as keys to growth.