Selenium vs. Cypress: Let the Code Speak
HTML-код
- Опубликовано: 10 май 2021
- In this corner, we have long-time reigning champ: Selenium WebDriver
And over in this corner, we have heavyweight newcomer: Cypress
Which of these will take the belt???
If you’re doing any automated testing, surely you’ve heard of Selenium WebDriver and Cypress, the two most popular web automation frameworks in the market. There have been several articles comparing and contrasting the capabilities of these two amazing frameworks, but it all feels very academic.
This webinar is going to take another approach...it will be a battle of the code! Automation expert, Angie Jones, will represent Selenium WebDriver while Colby Fayock, developer extraordinaire, will represent Cypress. Round for round, Angie and Colby will take coding tasks and implement them in Selenium as well as Cypress, then analyze how each of the frameworks perform to solve real world testing challenges. You, the audience, will weigh in to judge each round.
Join them and hear for yourself what the code has to say! 
Кино
This was awesome! Great entertainment! I found myself cheering for Selenium while learning about the use case for Cypress.
Great Job all!
I love this type of videos, not academic, or very strict theoretical, this is a video that explains the real automation day, thank you so much for that, I have worked with both of them, and I have to accept that Cypress was easier to me, BUT I had some problems when the login feature is external to the application. I googled for information but I saw that a lot of people were having the same issue, (2019)
I love Selenium because I can get more structured my FW. (also is more difficult to understand), but I love CY because it is pretty easy to use and implement.
I would like to see Selenide (Selenium underhood) beside Selenium.
Appreciate, if you can find some time to come up with a video for TestCafe vs Cypress vs Playwright too
Gogogo Selenium!!!!!!!!!!
practical comparison would be selenide vs cypress
I thought the same, and selenide would have been a clear winner..
This was great! The ending was epic hah
Love Angie's playfulness. Selenium fan forever.
Love it.
Big thanks to Applitools for arranging all this! For me the winner is clearly Selenium, I mean.. round 8 was really unnecessary. If you have to test your API's through your front-end you're clearly doing it wrong. Moreover, why would someone even bother deploying the web component when you can have the results of your API tests much sooner.. But ok, Applitools is developing plugins for both Selenium and Cypress so they didn't wanna get into the battle since it was not theirs to begin with. Congrats for organising this though!
I love this
Isn't there a Kotlin port/extensions for Selenium that can make the methods concise?
nice awesome
One of my biggest issues with Cypress is they don't really give you full control. They give you control over how they think things should be done. In the real world, things aren't ideal or perfect. I've made much simpler suites using selenium than I have with Cypress.
👍
Wow first comment ! yeah
@@dracosh What's the point of wasting time on a comment that doesn't make sense for you? Hmm
10:50 isn't true that you should know CSS vocabulary, you will need to understand the tool, as needed using "By.id" or assertEquals
cucumber + selenium is better
It is inaccurate that you can't use multitabs in cypress, because you can simulate multi tabs inside your tab
Cypress is much better, selenium is outdated and their documentation sucks