I've plenty of experience with both. Until BiDi comes in and is supported Playwright is hands down much better if you want reliable tests. Also depending on the app being tested and more often the JS front end library used Angular, React, others, while i had code for Selenium to worth with shadow roots, selenium couldn't reliably work with the shadow dom nodes, same test would fail 40-60% of the time. Playwright on the other hand, automating the same exact pages 100% success 100% of the time. Not to mention a number of things PW has done to help reliably get and work with screen elements Selenium, well you could get kind of the same functionality but will require someone rather knowledge a fair amount of work to get things to get Selenium to have the same functionality that is simply baked in and supported by PW out of the box. I've been away from Selenium for about 3 years now, i doubt it has support to intercept REST/Http requests? PW has this out of the box too...
And even then, Playwright might use BiDi aswell (You can see they experiment with it in the PR's) so it'll still be better, as their API and Documentation is so much more up to date and maintained.
@@ValorHeart Ya i'm rather active in PW's discord, BiDi comes up once in a while. And the PW team mentions they are actively monitoring looking at it but that is about it. If it gets working BiDi i think will be one of the best if not the best solution, so that for me isn't the issue with it. The problem is no one is really picking up the gauntlet taking the lead and driving the process. I've seen a few things over the last 30 or 40 years look great, promising but never coming to fruition, or when if and when they did, there wasn't much adoption. Bidi's biggest weakness will be getting a standard common solution in all the browsers. Looking at PW's issues, might be me but lots of basic functionality just seems broken in BiDi currently. While BiDi looks promising the problem is it is more a sink, i.e. no income and doesn't, nor will it drive revenue... I wouldn't expect much change with BiDi or that it will be accepted all that quickly it after give years now, from what i'm seeing, there is very little traction on improving it... Glad to be wrong but, not seeing it.
Hi, thank you for your suggestion! We’re always looking for ways to make our content more helpful and engaging. We’ll take this feedback into account for future videos :)
I have 10 plus exp in auromation, what you think should i go with playwright or cypress
Check the job market and see which has more job offers in Playwright or Cypress.
Playwright for sure. Especially for Test Automation. Not sure about RPA though.
I've plenty of experience with both. Until BiDi comes in and is supported Playwright is hands down much better if you want reliable tests. Also depending on the app being tested and more often the JS front end library used Angular, React, others, while i had code for Selenium to worth with shadow roots, selenium couldn't reliably work with the shadow dom nodes, same test would fail 40-60% of the time. Playwright on the other hand, automating the same exact pages 100% success 100% of the time. Not to mention a number of things PW has done to help reliably get and work with screen elements Selenium, well you could get kind of the same functionality but will require someone rather knowledge a fair amount of work to get things to get Selenium to have the same functionality that is simply baked in and supported by PW out of the box. I've been away from Selenium for about 3 years now, i doubt it has support to intercept REST/Http requests? PW has this out of the box too...
And even then, Playwright might use BiDi aswell (You can see they experiment with it in the PR's) so it'll still be better, as their API and Documentation is so much more up to date and maintained.
@@ValorHeart Ya i'm rather active in PW's discord, BiDi comes up once in a while. And the PW team mentions they are actively monitoring looking at it but that is about it. If it gets working BiDi i think will be one of the best if not the best solution, so that for me isn't the issue with it. The problem is no one is really picking up the gauntlet taking the lead and driving the process. I've seen a few things over the last 30 or 40 years look great, promising but never coming to fruition, or when if and when they did, there wasn't much adoption. Bidi's biggest weakness will be getting a standard common solution in all the browsers. Looking at PW's issues, might be me but lots of basic functionality just seems broken in BiDi currently. While BiDi looks promising the problem is it is more a sink, i.e. no income and doesn't, nor will it drive revenue... I wouldn't expect much change with BiDi or that it will be accepted all that quickly it after give years now, from what i'm seeing, there is very little traction on improving it... Glad to be wrong but, not seeing it.
you should show more visuals of the software, looking at your face for 7 minutes talking is not engaging
Hi, thank you for your suggestion! We’re always looking for ways to make our content more helpful and engaging. We’ll take this feedback into account for future videos :)
@@oxylabs she did a great job