March 2023 Summaries

The Cypress Ambassador Spotlight highlights Rafał Krząpa, a dedicated advocate of Cypress who shares his knowledge through articles, public speaking, and mentoring younger testers. As a QA Lead at a major Polish company, he leverages his experience to help others resolve issues with Cypress and appreciates features such as easy debugging and test organization. His passion for sharing knowledge began during the COVID-19 pandemic when he launched his own software testing page, marking a significant milestone in his career. The Cypress Ambassador program aims to support and celebrate individuals like Rafał by providing them with opportunities to engage with a global community, offering resources and visibility to further their advocacy efforts.

With the release of Cypress 12.9, a new feature has been added to the Debug page, enhancing the continuous integration (CI) debugging experience by allowing users to navigate between test runs. This improvement enables users to view, investigate, and rerun failed tests recorded to the Cypress Cloud directly from the local Cypress app, without needing to switch contexts. The navigation feature is particularly beneficial for projects with multiple test runs per commit, as it provides greater flexibility and insight into debugging workflows. To utilize the Debug page, users must ensure that their git is properly configured and that they are sending git data to Cypress Cloud, as the feature relies on local git history to display relevant Cloud runs. Additionally, users are encouraged to explore the Cypress Steps Plugin, which enhances the command log by adding test steps and errors. For more details on the Debug page and other updates in version 12.9, users can refer to the documentation and changelog.

The blog post, authored by Adam Stone-Lord, discusses the benefits and methodology of using Cypress Component Testing for test-driven UI development. It highlights the shift from traditional testing methods, which often rely on simulated DOM environments like jsdom, to Cypress's approach that allows components to be rendered in a real browser. This real-time rendering provides immediate visual feedback, enhancing the development workflow by allowing developers to iterate on components rapidly and view changes instantly. The post illustrates the process with an example of building a notification component for Cypress's Real World App, emphasizing the importance of writing tests before development to define component APIs and behaviors. This approach not only aids in creating a robust, loosely-coupled code but also serves as documentation for future developers, helping prevent regressions and ensuring the component meets specified requirements. Furthermore, the post encourages leveraging Cypress Cloud for enhanced testing efficiency and scalability, offering resources such as webinars and documentation for further learning.

The Cypress Ambassador Spotlight on Preeti Bellad highlights her motivations and contributions as a Cypress Ambassador, emphasizing her desire to share her deep QA expertise to enhance Cypress features and assist others with problem-solving in the community. Bellad actively contributes by addressing queries on Cypress community channels and sharing insights via LinkedIn posts, with her favorite Cypress features being the debugging facility in GUI mode and the spying and stubbing of network calls. Her professional pride lies in being acknowledged as the top university graduate in her Engineering Bachelor's course. For newcomers to Cypress, Bellad recommends starting with the documentation and approaching it with an open mind. The Cypress Ambassador program aims to support advocates by offering speaking opportunities and personalized hubs while celebrating their contributions to the community. The program seeks to expand its offerings and encourages engagement through upcoming events and opportunities.

Women in test automation are essential contributors to software development, bringing diverse perspectives and skills that enhance the quality and inclusivity of software products. Despite the significant role they play, many women leave their tech careers by age 35, highlighting the need for supportive environments that promote gender parity and equal opportunities. Organizations can support women by fostering allyship, encouraging open-mindedness, and providing opportunities for mentorship and professional growth. These efforts not only help women thrive in their careers but also contribute to breaking down gender barriers and biases in the tech industry. The experiences of women in automation testing demonstrate their resilience and determination, inspiring others and paving the way for future generations. By sharing their stories, these women emphasize the importance of diverse voices in driving innovation and progress in the tech sector. The blog encourages participation in programs and communities that support women, aiming to empower more women to pursue and succeed in tech careers.

Test isolation is a crucial best practice in software testing that ensures tests are run independently, preventing one test's state from affecting another and thereby ensuring reliable and reproducible results. With Cypress version 12, test isolation is enforced by default, resetting the test and browser state before each test to clear any potential interference from previous tests, including the DOM state, cookies, and local and session storage. This approach not only enhances the reliability of test results by eliminating dependencies between tests, but also allows for parallelization within CI/CD pipelines, significantly improving test execution time. Techniques such as using beforeEach hooks to define shared setups and the cy.session() command for preserving login sessions are recommended to maintain test independence while optimizing performance. While disabling test isolation can improve performance for certain test suites, it introduces risks of misleading failures and increased complexity in debugging, highlighting the importance of maintaining isolated tests to ensure a reliable and scalable testing framework.

The Cypress Ambassador Spotlight highlights Joël Grimberg, an enthusiastic advocate for Cypress, a tool that simplifies test automation. Grimberg, who is passionate about training and coaching development teams on the effective use of Cypress, values the tool's ability to provide a DOM snapshot with every command and appreciates the Smart Orchestration feature of the Cypress Dashboard. Outside of his professional life, he enjoys playing musical instruments, reading, and running. Becoming a Cypress Ambassador is a significant professional milestone for Grimberg, inspiring others by his journey. The Cypress Ambassador program, designed to support top advocates worldwide, offers speaking opportunities, personalized hubs, and network visibility, while emphasizing community spirit and advocacy. The program is expanding to include new experiences and resources, and there are plans for more engagement opportunities with ambassadors throughout the year.

Cypress has introduced the Component Framework Definition API in version 12.7, which enhances the platform's extensibility by allowing developers to integrate third-party libraries and frameworks more seamlessly into Cypress for component testing. This update simplifies the configuration process, enabling developers to quickly set up and test components with minimal code, typically under 100 lines. The API includes features such as automatic detection of libraries, scaffolding of necessary files, and detailed documentation to facilitate the creation of framework definitions, such as for Solid.js, and provides mounting adapters for rendering components. As the API continues to evolve, Cypress aims to extend support to more complex platforms like Nuxt, SvelteKit, and Qwik, and encourages developers to engage with their community through forums like Discord and GitHub for support and collaboration.