Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Atlanta Code Camp 2019: And Now Selenium's watch is Ended

Atlanta Code Camp 2019: And Now Selenium's watch is Ended

UI tests have long been valuable as a tool to automatically verify that all of the components of an application are working together correctly. They have a (much deserved) reputation of being difficult to write, brittle, taking a long time to execute, full of false negatives, and difficult to maintain. In this presentation we will learn about techniques to mitigate many of these problems using a new browser-based UI testing tool called Cypress that will make it easier for you to write UI tests that are more flexible and run faster than the Selenium equivalent.

Matthew Y Knowles

September 14, 2019
Tweet

More Decks by Matthew Y Knowles

Other Decks in Programming

Transcript

  1. Matthew Knowles Software Craftsman at Greater Sum www.GreaterSum.com @MatthewYKnowles [email protected]

    And Now Selenium’s Watch is Ended Using Cypress to write UI tests that are less brittle and run faster
  2. Roadmap • Tests • Testing with Selenium • Testing with

    Cypress • Live coding Cypress tests • Advanced UI testing techniques
  3. Why Write Tests? • Verify functionality • Defend against unexpected

    change • Executable documentation of the code
  4. Why Write UI/E2E Tests • Verify that the critical path

    works • Exercise your code in a live or live like environment
  5. Why Write UI/E2E Tests • Human Readable • Behavior Driven

    Development (Dev/Product/Test) • Executable specification
  6. When not to use Cypress • Firefox, Safari, and Edge

    • Access outside the browser • Has been out of beta less than 1 year