and Selenium – What We Learned and How it Changed Our Automation Strategy

Did you know Selenium test automation appears in approximately 80% of QA job postings? It is also by far the most frequently listed automation skill on QA resumes. However, if you ask an experienced Selenium test engineer to consider an alternate UI tool, that is NOT Selenium-based … you will usually get push back, a negative or even defensive response. Why? Especially, when you hear common stories of flaky tests and various degrees of how to deal with timeouts and countless frameworks.

If you ask a UI/UX engineer, well .. you will get a more positive reaction. During the past 3 years, continues to gain more users and support from both the DEV and QA communities. From Jest, Enzyme, Selenium, to Cypress – what are we to do? Is Cypress really the “Selenium Killer”?

Join us and learn and hear Peter Kim share (and demo) how Cypress can successfully be leveraged in your QE strategy.

Session Takeaways:

  • What is Cypress?
  • How to automate with Cypress
  • Selenium/Cypress Pros/Cons
  • Demo on automating the same scenarios with Selenium and then Cypress
  • How to leverage Cypress into your automation strategy (even if you have already invested in Selenium)

Location: Coronado 4/5 Date: April 1, 2020 Time: 2:30 pm - 3:30 pm Peter Kim