Playwright, every mention

mentionsepisodesper episode tap a year for its mentions

Verbatim, from the transcripts: the passages where Playwright comes up

loading…

▶ 38:29 Ryan Lopopolo Uh, there was one point where we had wired Playwright directly up to the Electron app, uh, with MCP. 3 times in the scene

▶ 23:35 Samuel Colvin The interesting thing here is we, we take this, we take Playwright and we have a like open page function when it has access to the browser and it will return me an instance of this page type. 2 times in the scene

▶ 58:20 Alessio Fanelli If I build a better linter that is private to me or like a better, uh, test suite, like a better playwright replacement, like in theory, I'm kind of overfitting the model to perform better, right?

▶ 52:05 David Soria Parra And there, there's still use cases for developers in general, like, first of all, as builders, but also like, I still love my playwright MCP server, man.

▶ 10:26 Mike Krieger That's going to come from sort of additional vision capabilities that, you know, we'll work on, but I think that's going to be a really key piece of, of closing that loop so that, you know, model, and I've seen people do this with cloud…

▶ 53:11 Alessio Fanelli And now I'm mostly bottlenecked by your playwright. 3 times in the scene

▶ 4:22 unnamed speaker And then we had Selenium, we had Playbrite, we had all these different browser things, but it's always been super hard to do.
▶ 12:48 Paul Klein So let's say you're using, um, a popular browser automation framework like Puppeteer, Playwright, and Selenium. 2 times in the scene
▶ 33:48 Paul Klein Puppeteer, Playwright, Selenium. 5 times in the scene
▶ 37:56 Paul Klein Well, yeah, I mean, Puppeteer, Playwright, and Slending, we're all designed as testing frameworks, right?

Turn any episode into a week of clips.