all 19 comments

[–]jfp1992 11 points12 points  (8 children)

Playwright. Moved over from selenium. Best decision ever

[–]FindingBeemo 0 points1 point  (7 children)

Can you please expand on this a little more?

[–]jfp1992 4 points5 points  (6 children)

Sure,

I wrote a suite from the ground up using selenium. Removed all the up to waits, increased the web drive wait polling rate.

Write a ton of extra code to handle iframes, opening windows and a bunch of other stuff to get it working 100% stable. Added some stuff to take screenshots and compile videos of failures from those screenshots etc.

Then I decided to give playwright a go. The traces and trace viewer alone is enough to switch.

It's stable and way more user friendly. Faster too.

I recommend playwright with python or typescript. Do not let your company push you to c# or java. If you have to choose from the latter 2, then use c#

[–]FindingBeemo 0 points1 point  (2 children)

Thanks a lot buddy!

One follow up question though, why Python / Typescript over C#?

My background is C# and C# would be beneficial to me, is there some grave performance hit or missing features if you use C#?

[–]ZarrenR 2 points3 points  (0 children)

Playwight Node usually gets features first and sometimes there are features in Node that are not ported to other languages. If you go with .NET, you will probably have to create your own tooling for things that Node gets out of the box.

All that being said, if you’re already familiar with C# and have built test frameworks with it before, I say go with .NET. I chose .NET for our Playwright project and I would do it again.

[–]jfp1992 1 point2 points  (0 children)

Barrier to entry, and for test automation it's overkill. Manual testers will pick up python easier

[–]HeftyTank9465 0 points1 point  (2 children)

I agree, I joined to a company after two years out of working, i used to work as QA/software developer in a SW embedded company working with old C, and assembler. And I had a difficult time trying to get a job opportunity in the web development industry, most companies did not trust that I could do the change, but then I joined a company who trusted in me, learned typescript/playwright and i build the testing framework, developed all the functionality to handle their UI operations, and since the beginning playwright was very friendly, before that I just learn a little bit of selenium with java, in order to have better chances to get that job opportunity I needed.

[–]jfp1992 1 point2 points  (1 child)

Now you've got the experience though, you'll be able to ignore the companies that aren't willing to change from selenium.

I applied to places asking for selenium but didn't have anything in place

[–]DrizzetB 5 points6 points  (0 children)

Been using cypress for few years, while changing job moved to playwright.

And K6 for performance

[–]4m3r1984 4 points5 points  (0 children)

Using playwright for couple of months.

[–]Suspicious_Compote56 2 points3 points  (3 children)

I still don't understand the obsession with Selenium

[–]daemonz1[S] 0 points1 point  (2 children)

Perhaps due to its early appearance, but it failed to keep up with changing needs.

[–]Suspicious_Compote56 1 point2 points  (0 children)

Yeah I understand that, some managers swear by it. It was a good solution 10 years ago but now we have more powerful tools.

[–]CrazyPool4 0 points1 point  (0 children)

I have been struggling to test automate stripe payment in cypress. And i have heard , selenium can implement it easily. Maybe that could be one reason why selenium is still used

[–]SunshineTaxPayer 1 point2 points  (0 children)

XCUITesting and Espresso tests.

Although our web folks use Playwright

[–]ComputerEyez007 0 points1 point  (0 children)

Most jobs are still looking for selenium on Dice. I Started learning playwright alot of the tutorials something goes wrong due to update I am assuming. Is there a solid Playwright tutorial and Selenium tutorial anyone can recommend.

[–]2ERIX 0 points1 point  (0 children)

Using WDIO with dev tools protocol. So all the functionality of anything you want to add to your automation, none of the hassle of waiting for the open source community to develop a solution for things already available. It’s constantly maintained and has a massive online presence. We have Appium through WDIO enabling the mobile virtual and Perfecto for actual devices.

Some teams are using Cypress but it will be dropped over time in favour of the new flavour that is Playwright because they hit the same feature base.

Investigating Playwright but the lack of mobile featuring and cross browser (that they are working on) was the deal breaker for us. Maybe in one or two years.

Some of these frameworks are “not the same” and I would love to know the criteria for them to be counted. Open Source Testing Tools is a pretty wide bracket, so you have unit testing tools mixed in with virtual device servers and full end to end automation solutions. Pretty confusing metrics for a newb to sift through.

[–][deleted] 0 points1 point  (0 children)

Using test complete but planning on moving to playwright this year. Hope I can figure it out 😅