A podcast featuring Philip Heretz, a Cypress test automation expert, discusses the tool’s usability, limitations, and best practices, alongside his journey in testing and advocacy for continuous learning. Topics include Cypress’s developer-friendly design, challenges like third-party testing, and resources like Test Automation University for skill development.

How To Test This?

interview episodes where Mamadou N’diaye talks with with software testing experts

• https://podcasters.spotify.com/pod/show/spidey1944
• https://www.youtube.com/@HowToTestThis
• https://www.linkedin.com/in/mamadou-ndiaye-consultant/

Episode Details

• Show Notes: https://podcasters.spotify.com/pod/show/spidey1944/episodes/How-to-Test-with-Cypress---Filip-Hric-e3e82pj
• Published: 2026-01-27T02:48:55Z
• Duration: 00:50:57
• Author: Mamadou N’diaye

Overview

The podcast discusses Cypress, a modern test automation tool tailored for web applications. It emphasizes Cypress’s benefits, including its ease of use, fast test execution, and clear error messages, which make it ideal for beginners. Running directly in the browser, Cypress provides more reliable and consistent test results compared to older tools like Selenium. However, it has limitations when dealing with external applications, third-party authentication, and complex interactions like pop-up windows.

The conversation delves into important Cypress concepts such as command chaining, retry mechanisms, and techniques to avoid flaky tests. It also underscores the need for continuous learning and collaboration between testers and developers. Practical advice includes experimenting with new features, working through example projects, and utilizing the plugin ecosystem to enhance Cypress’s capabilities. Additionally, the episode explores broader testing strategies and the evolving role of testers, highlighting the increasing influence of AI in test automation.

What If

• What if you built a web application to better understand the developer experience and refine your test automation strategy?
  Concrete Move: Spend 2 weeks building a basic web app (e.g., a to-do list or blog) using React or Vue, then implement Cypress for E2E testing.
  Why Now: Youll gain empathy for developers and firsthand experience in identifying edge cases, which directly improves your ability to structure test scenarios.
  Expected Upside: Youll create a reusable test suite and better understand how to architect tests for real-world applications, reducing friction when collaborating with developers.

• What if you integrated AI-powered tools like Cursor or Claude Code into your Cypress test-writing workflow to boost productivity?
  Concrete Move: Use Cursor or Claude Code to generate boilerplate test scripts for common UI interactions (e.g., form submissions, navigation flows) in Cypress.
  Why Now: The text highlights AIs growing role in test automation, and experimenting now positions you to adopt cutting-edge practices before competitors.
  Expected Upside: Youll reduce manual scripting time by 30% while ensuring test scripts align with Cypresss chaining syntax, minimizing errors and flakiness.

• What if you launched a blog or YouTube series documenting your Cypress learning journey and sharing tips for beginners?
  Concrete Move: Publish a weekly article or video on platforms like Medium or YouTube, covering topics like Cypress command chaining, error debugging, or POM alternatives.
  Why Now: The text emphasizes the value of sharing knowledge to build a community and reinforce your own expertisethis is actionable and leverages your existing skills.
  Expected Upside: Youll establish yourself as a thought leader, attract potential clients or collaborators, and create a long-term knowledge asset that drives passive income or visibility.

Takeaway

• Install and experiment with Cypress immediately: Start by installing Cypress and creating example projects to understand its command chaining, retryability, and error messages, which are critical for writing stable, readable tests.
• Learn JavaScript, HTML, and CSS fundamentals: Understand basic HTML tags, CSS selectors, and JavaScript syntax to effectively use Cypress for test automation, even if you’re not a full-time developer.
• Avoid over-abstracting test code with Page Object Model (POM): Instead of forcing POM into Cypress, prioritize direct, readable test logic to simplify debugging and reduce maintenance overhead.
• Leverage Test Automation University (TAU) for structured learning: Use TAUs free courses, especially the Cypress-specific content, to build expertise in test automation and stay updated on best practices.
• Share knowledge through blogs or social media: Publish your learning journey, test strategies, and Cypress tips to build an audience, reinforce your understanding, and contribute to the testing community.