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

Staying confident in terms of code changes - An introduction to Cypress

36751965e79dca4618cccc3c08efc912?s=47 Ramona Schwering
April 30, 2021

Staying confident in terms of code changes - An introduction to Cypress

It’s important to write a test
for any code change. Regardless of which test you write, they will make you confident that another code change won’t break your code. However, when it comes to UI testing, some developers tend to be reluctant a lot. Are those tests slow, flaky, hard to write
and maintain?

Cypress.io (or Cypress for short) is currently getting a lot of attention when it comes to end-to-end testing. Especially in JavaScript environments, Cypress.io seems to be slowly gaining acceptance. It does a lot of things right and is preferable to selenium-based approaches in my opinion.

In my session, I want to introduce Cypress to you and explore its possibilities by writing the first tests for the TechFairLive website - so that we can overcome those concerns together.


Ramona Schwering

April 30, 2021


  1. None
  2. None
  3. None
  4. None
  5. None
  6. None
  7. None
  8. None
  9. None
  10. None
  11. None
  12. None
  13. None
  14. cy.intercept({ url: '/widgets/checkout/ info', method: 'GET' }).as('checkoutAvailable'); // … cy.wait(‚@checkoutAvailable')

    .its(‚response.statusCode‘) .should('equal', 200);
  15. None
  16. None
  17. None
  18. None