Join atslido.com

#SanaeBEER

Audience Q&A Session

E2E tests don’t have to eat your time

Join atslido.com

#SanaeBEER

What area do you work in?

Join atslido.com

#SanaeBEER

What is the main reason not to write e2e tests?

Test strategies

● Many different strategies

● All have the same goal in mind

● All aimed at working software and

overall quality

● In my opinion, it is users that

determine quality

● That is why I think that focus on

users is key

Join atslido.com

#SanaeBEER

Do you agree that users determine quality? (1 star = strongly disagree, 5 stars =

strongly agree)

The more tests resemble the way your software is used, the more confidence they can give you

– Kent C. Dodds

Slido QA- Started with no automatic tests (1 tester, 5 developers)- List of scenarios that I would go through manually, before every release- This would lead to regressions found in last minute, slowing down releases- Challenges:

- We need automation - write tests quick, with a simple tool that is easy to learn- We want to make QA process faster- We want to give developers freedom to refactor and make bold changes- We want to keep our users safe, not harming their events - there are no second

chances on live events- We decided to use Cypress

Demo time!

Let’s go practical

Main points● Mocha syntax● cy.visit()● Automatic run on save● cy.type()● Assertion on url● Assertion on class● Time travel● Assertion on question length● Routing● Stubbing

○ Back to presentation● Headless mode● CI, parallel, dashboard

Run tests in CI

Great documentation here!

Dashboard

Parallelization

I love the simplicity of Cypress. But mostly, I love that we can avoid difficult setups and think about our tests as real user stories.

– me, just now

Follow me on twitter @filip_hricI post blogs and Cypress tips

Want a Cypress t-shirt?Feedback my talk at link.cypress.io/filip

Join atslido.com

#SanaeBEER

Audience Q&A Session