March 2025 Summaries

Ryan Emberling, a Cypress Ambassador, is motivated to share his knowledge about Cypress and automated testing, helping others through teaching and collaboration on QA challenges. He highlights the importance of treating tests as sacred and addressing failures promptly to maintain quality. Emberling's favorite Cypress feature is test replay in Cypress Cloud, and he recommends new users start by outlining their application's UX structure. Outside of work, he enjoys playing music and cards, running an open source web app for card games, and collaborating with other developers. He is proud of his work on E-TRIALS, a platform democratizing educational research. The Cypress Ambassador program aims to support and showcase advocates like Emberling, offering opportunities for connection and community engagement.

Cypress Accessibility has introduced updates to its Results API, enhancing the process of accessibility checks by using server-side processing during test runs recorded to Cypress Cloud. This approach, which operates outside of typical in-test scans, offers benefits such as eliminating the need for special setups, avoiding performance impacts on test execution, and ensuring consistent results. The accessibility checks run in parallel to test executions, ensuring that tests can fully execute while capturing comprehensive user journey data. However, developers and testers require automated feedback when accessibility standards are not met, which is addressed by the Cypress Accessibility Results API. The latest updates to the API include detailed breakdowns of accessibility reports for individual pages or components, along with accessibility scores and counts of failed elements, providing teams with the ability to manage outcomes efficiently and notify relevant parties of specific failures. This non-disruptive, always-on accessibility check system allows for customizable policy settings and escalation procedures based on detected issues.

The introduction of Cypress.stop() provides a simple way to halt test runs programmatically, allowing for faster feedback and increased flexibility in testing. This command enables users to stop tests immediately upon failure or based on other conditions, making testing more efficient and predictable. Cypress.stop() works by halting execution within the current spec file on the current machine with a single command, and can be used in various scenarios, such as stopping tests on failure or when certain conditions are not met. While Cypress.stop() offers in-spec control and debugging capabilities, it is distinct from Auto Cancellation in Cypress Cloud, which provides global scope, failure thresholds, and better resource allocation, making it a better choice for complete run-level control. Overall, Cypress.stop() is a powerful tool that can be used to improve testing efficiency and is now available for use, with more details available in the official documentation.