Cypress vs. Playwright: Let the Code Speak
ฝัง
- เผยแพร่เมื่อ 8 ก.พ. 2025
- See who will be crowned the winner in this epic matchup between test automation frameworks Cypress and Playwright.
Cypress Versus Playwright, presented by Applitools. See the session materials, including the example code, at applitools.inf...
Rather than compile lists of feature comparisons, this matchup is a battle of the code where Cypress Ambassador Filip Hric and Automation Panda Andrew Knight implement small coding challenges in JavaScript using Cypress and Playwright, respectively. They then compare and contrast their solutions, and the audience chooses the winner.
See comparisons of Cypress and Playwright in:
API requests
Inline frames
Alerts
Page Objects...and more!
From the audience:
"This was great. Loved the playful banter."
"Event was really well done..fair play to all involved"
"Very Useful and Interesting Sessions"
Interesting point - migrating the cypress project to the latest cypress version(v10.6.0 atm) reduces the running speed to an average of 12 seconds, while playwright takes 9 seconds on my machine, pretty big improvement.
Those intros were lit AF and great panels as well.
Thank you! This was excellent and very informative. Something else I've noticed with Playwright is how similar the syntax is to Jest and RTL. My team's unit and integration tests are written using these frameworks, and it's nice to stick with something similar for E2E testing,
Thank you for this video. The real value of this is not whether Cypress or playwright wins, but really the learning from seeing both framework side-by-side. Both frameworks are excellent. My personal choice is playwright, but mostly because of the python support.
First one where you share and debate the alternative approaches for different areas. Well done for balanced comparison and possible cross learning better than others I’ve seen.
Please list the video. It will be so helpful for the QA community ;)
Love this! Playwright does not have implicit waits at the assertion level, only at the action level.
I think are great tools, nonetheless
Thank you for the fun and informative workshop!
Hi guys! Thanks for a great and funny workshop! Your work is constructed in the coolest way possible, keep up doing this! :)
I just wanted to leave a comment regarding Alerts: both Cypress and Playwright are accepting alerts by default (if no specific settings are defined), but don't you think that it might by risky in terms from the security side of things?
To be fair, you can easily add a custom command to handle s with Cypress. No plugins needed.
As someone who used both I like playwright more.
Amazing tools! Good job guys!
Kudos to you guys. Was a very good and informative session!
With a fair amount of experience with TestCafe, I think I can confidently say that it'll give playwright a very tough competition.
I don't like having a testing framework being part of the automation system. I personally use ava for all my testing. So, I just want to have access to things like contained text and attributes (which I can get if I can get the element object), then handle the testing in whatever framework I choose.
Why no scenario in which Cypress has a distinct advantage because it runs in the browser?
Thanks for this informative video.
Philip was too nice, whereas Andy was ruthless 😂
Do you have a python playwright course to recommend?
how to click on capcha checkbox , knowing it's in please ?
My gosh, @AutomationPanda has a villainous laugh! Disney needs to hire him for next Minions villain voiceover.
Loves the discussion
I would love if this type of technology could come to mobile app testing. Appium and Detox suck in comparison. I've been a Cypress person up until now but I will look into Playwright :)
The example with the manipulation of the target of the link looks very bad to me.
There is a very strong coupling here between the test code and the specific implementation. If for example there is a click event that calls preventDefault() and then opens the window using JS, the webpage behavior will remain the same but the script will fail.
Cypress at least has external libraries to handle touch-based actions in a couple of lines of code, Playwright doesnt have anything like that still, you need to come up with some custom JS based scripts or dispatchEvents functions, which not always work. So I think it handles mobile testing much better
why doesn't playwright offer support for Angular?
there is a 3rd party package and vanilla typescript can be used
would be nice to use component testing too, will be interesting once it finishes experimental phase
Cypress now has experimental Safari support.
not the best choice of language for PW, if it was Python or Java it would be less verbose. (But Cypress doesn't support those langs right).
What's Captain America's niece doing here??!! ;)
Cypress is more elegant
based on inner feelings or some tangible proof?
@@romanleca4969 Sure, it is based on inner feelings. My comment was expressing my personal opinion.
@@arzievsultan, I'd say, elegance is very hard to evaluate objectively, since it is primarily a subjective term. btw, there is a fresh rematch on this th-cam.com/video/RwNZTjwhgXc/w-d-xo.html
I thought I was a Playwright fanboy, but this guy has drunk so much of that kool-aid it makes me cringe 😆