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

E2E testing as it should be

E2E testing as it should be

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 first tests for the https://phpugms.github.io/ website (or any other if I need more test cases) - so that we can overcome those concerns together.

36751965e79dca4618cccc3c08efc912?s=128

Ramona Schwering

August 24, 2020
Tweet

Transcript

  1. E2E testing how it should be @leichteckig

  2. E2E testing how it should be @leichteckig

  3. E2E testing how it should be @leichteckig

  4. E2E testing how it should be @leichteckig

  5. E2E testing how it should be @leichteckig

  6. E2E testing how it should be @leichteckig

  7. E2E testing how it should be @leichteckig

  8. E2E testing how it should be @leichteckig

  9. E2E testing how it should be @leichteckig

  10. E2E testing how it should be @leichteckig Custom commands Custom

    commands Cypress.Commands.add('awaitAndCheckNotification', (message) => { cy.get('.sw-notification .sw-alert__message') .should('be.visible') .contains(message); });
  11. E2E testing how it should be @leichteckig

  12. E2E testing how it should be @leichteckig