Cypress has been gaining popularity during last couple of years. This tool aims to redefine a lot of established concepts that were present in end-to-end testing. Starting with Cypress feels like taking on a totally new testing journey. To be honest, it IS a different journey, but an exciting one. In this webinar, Cypress Ambassador Filip Hric, walks you through the first steps of how to start working with Cypress. Take away a solid understanding of what this tool can and cannot do for you.
2. 👋 Filip Hric
- Studied psychology
- almost 6 years at Slido
- Mostly test automation
- Cypress ambassador
- filiphric.com - Cypress tips
every week
- Workshops, presentations,
webinars, courses, streaming,
youtube, consultations
3. What is Cypress?
- a tool for testing anything that runs in browser
- built completely from scratch, doesn’t use Selenium
- tests are written in JavaScript and TypeScript
- runs inside browser, great debugging tools
- completely open source
- has a paid Dashboard service
9. Testing, the way it should be (?)
- cypress was built for developers
- fast test development
- typescript support
- built for browser, works great with devtools
- integrates in CI/CD pipelines
- powerful network stubbing
- manipulate DOM elements
- automatic retries and great adaptation to changing DOM
13. Cypress is here to stay
- tests written in the language of web
- massively improved speed of delivery for e2e tests
- taps into the power of node ecosystem
- plays well with browser
14. Some critique of Cypress
- uses JS to trigger events like type, click etc.
- cannot open multiple tabs
- multiple domain support
- lack of iframe support
- no support for Safari & Internet Explorer
17. 17
let’s stay in
touch!
- filiphric.com - my blog
- filiphric.com/youtube
- filiphric.com/discord
- filiphric.com/twitter
- filiphric.com/linkedin
- filiphric.com/github
Notas do Editor
I kinda don’t like this question, because it feels like asking how is car different from a motorcycle
these are completely different approaches to testing
your code written in java, ruby, whatever, processed by selenium, basically doing http calls to your browser
architecture of Cypress is slightly different
so why build a testing tools for developers? why didn’t Cypress build a tool for testers?
Testing is not divided from development, it is not part of development, testing IS development
when dev writes a code and examines how that runs - it isn’t that he suddenly stopped developing - it’s a part of workflow
but for some reason we have divided it - different people, different building different company
there may be good reasons for that
but I believe there are some great advantages to understanding how web apps work and to get that developer lens sometimes
cypress definitely encourages that
and to circle back on my initial point and answer the question
partially yes, testers should understand the app they are testing, it should never be a black box
visual testing, code coverage, any tool from npm
and since I picked these, I have answers to all of them
at the end of the day it’s still important you use your own judgement, so don’t feel like I’m pushing you towards something
there are interesting things ahead, so the only question left is to ask: