playwright

Shoot - good call. For anyone reading this: Playwright is a very popular browser automation library. Developers use it to automate websites, spanning use-cases like QA Testing, Web scraping, Form filling, etc https://github.com/microsoft/playwright

How does this compare to Playwwright? It got a similar feature recently [0] [0] https://github.com/microsoft/playwright/releases/tag/v1.59.0

The popular Playwright MCP uses the Chrome accessibility tree to help agents navigate websites: https://github.com/microsoft/playwright/blob/ed176022a63add8...

Also recently found it unnecessarily difficult to do profiling of page workers using Playwright's CDPSession wrapper (and they don't seem to have any plans to improve it: https://github.com/microsoft/playwright/issues/22992#issueco...), whereas it was pretty painless in Puppeteer. So, definitely more useful if you care about more than just your main thread.

It’s not too bad to get this working through dev tools and playwright, but I’m hesitant to bundle it into a repo or share my elisp because I don’t want to get banned by Anthropic. Here’s a hint: https://github.com/microsoft/playwright/issues/10369#issueco...

Hey Pavel, this is Namu, the creator of Browser MCP. You’re right, this is an adaptation of Playwright MCP to automate the user’s local browser as mentioned in the GitHub README and here: - https://github.com/BrowserMCP/mcp/blob/3e6824de6f36eba7d2d3b... - https://news.ycombinator.com/item?id=43613905 Thanks for all your work to Playwright and Playwright MCP. I’m a big fan! (For those not familiar, Pavel is the largest contributor to both Playwright and Playwright MCP: https://github.com/microsoft/playwright/graphs/contributors, https://github.com/microsoft/playwright-mcp/graphs/contribut...)

Rundoc is very interesting. Great work! I believe there are two ways to do what you want. 1. Use the VSCode extension APIs and the built-in commands[1] to write an extension that unit tests your tutorials For example, you could use vscode.executeCodeActionProvider which will return the actions that VSCode suggests at a specific point in the file. For the shortcuts, I think the only option would be to read user's keybindings.json file directly. This is the easiest way I think and may be enough but generally speaking, VSCode's APIs are very restrictive and may not give you everything you need. 2. VSCode being an Electron app can be run from Playwright (similar to Selenium) which should give you full control to drive and inspect it. I haven't done this myself but apparently Playwright is used internally to test VSCode as well. So it should b

SeleniumBase modifies the webdriver so that it doesn't get detected when used alongside the CDP stealth mode and methods. It'll download chromedriver for you. Not sure what you mean by the multiple branches, as there's just the primary one. What 1000-line methods are you referring to? By "flags", do you mean the different command-line options available? As for Playwright, they aren't undetected: See https://github.com/microsoft/playwright/issues/23884#issueco... - "Playwright is an end-to-end testing framework, where we expect you test on your own environments. Bypassing any form of bot protection is not something we can act on. Thanks for your understanding." On the contrary, SeleniumBase is OK with bypassing bot detection: https://github.com/seleniumbase/SeleniumBase/blob/master/exa...

A typical test runner implements a sharding feature that splits tests to run on different machines. However, the sharding algorithm often randomly splits tests, leading to uneven execution times across shards. Tenbin provides tools to minimize the differences in execution time across shards. It uses the execution times of past test run when splitting tests. For example: shard default use tenbin 1/3 3min 4min 2/3 5min 4min 3/3 4min 4min The optimization of the sharding algorithm is considered in E2E testing tools where test execution time is a more critical issue. In Playwright, this is being discussed in https://github.com/microsoft/playwright/issues/17969.

I'm not convinced. It looks like v0.10.0 contains ~half of Google's Puppeteer code and even in the latest release[0]the core package references Google's copyright several hundred times. Conceptually, the core, the bridge between a node server and the injected Chrome DevTools Protocol scripts are the same. Looks like Playwright started as a fork and evolved as a wrapper that eventually included APIs for Python and Java around Puppeteer. At the core there is a ton of code still used from Puppeteer. [0] https://github.com/microsoft/playwright/tree/48627ad48405583...

That is a huge oversimplification, if I ever saw one. If you look at the early commits, you can see that it isn't just a simple fork. For starters, the initial commit[1] is already using Typescript. As far as I am aware puppeteer is not and is written in vanilla JavaScript. The license notice you mention is indeed there [2], but also isn't surprising they wouldn't reinvent the wheel for those things they wrote earlier and that simply work. Even if they didn't directly use code, Microsoft would be silly to not add it given their previous involvement with puppeteer. Even if it was originally a fork, they are such different products at this point that at best you could say that playwright started out as a fork (Which, again, it did not as far as I can tell). [1] https://github.com/microsoft/playwright/commit/9ba375c063448... [2] https://gith

I tend to agree. An example of how it can be net-zero gain is in this screenshot[1]. To have something maintainable, you have to do your own refactoring pass on the generated code. At that point, it's not much effort to write the test yourself than it is to refactor all of the redundancies. 1. https://github.com/microsoft/playwright/assets/13063165/7794...

Hah yeah that's confusing. https://playwright.dev/python/docs/intro is actually the documentation for pytest-playwright - their pytest plugin. https://playwright.dev/python/docs/library is the documentation for their automation library. I just filed an issue pointing out that this is confusing. https://github.com/microsoft/playwright/issues/29579

Author here. Can you show an example of how Playwright would progress a timer on a page? For example, how would you make this component pass faster than 60 seconds? export const Countdown = () => { const [time, setTime] = React.useState(60); React.useEffect(() => { const interval = setInterval(() => { setTime(t => t - 1); if (t === 1) clearInterval(interval); }, 1000); return () => clearInterval(interval) }, []); return time > 0 ? <>Time left {time}</> : <>Done</> }; Short of using Playwright Component Tests, this isn't possible. I also found an issue where the only solution was to inject sinon into the page which I wouldn't consider a great option: https://github.com/microsoft/playwright/issues/10230