playwright-dotnet VS Playwright

Playwright

Check out Playwright which is developed by Microsoft. It's like Selenium, but newer and maybe better. You can use it outside unit tests as a regular library.

SDET? Check out Playwright's .NET connector: https://github.com/microsoft/playwright-dotnet

I'd suggest looking into https://github.com/microsoft/playwright-dotnet, it has been so much nicer to work with than Selenium.

I believe playwright can do the job, https://playwright.dev/dotnet/

Then you'd take that output and generate a PDF with Chrome: https://playwright.dev/dotnet/

If you've already got ASP.NET generating pages then you should try use this to save pages as PDF: https://github.com/microsoft/playwright-dotnet

If you've ever wanted to pull data periodically from a website, or you are a QA automation person looking to do E2E (end to end) testing, then Playwright might be an option for you. Similar to Cypress or PhantomJS, Playwright is a library that allows you to automate ineractions with websites, you can even take screenshots and PDFs!

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.

Playwright is a modern end-to-end testing framework for web apps. It supports multiple browsers, parallel execution, and, importantly for this post, built in reporters for turning raw test results into human-readable formats.

There is no way to ensure this BeforeAll hook executes only once across the entire test run, as many people expect. Despite its name, BeforeAll is called once per worker, not once per test run.

Playwright is a powerful open-source browser automation tool developed by Microsoft and often seen as a natural evolution of Puppeteer. In fact, many of its core features were inspired by Puppeteer—but with broader capabilities and stronger support for modern testing needs. Unlike Puppeteer, which only supports Chromium, Playwright allows testing across Chromium, Firefox, and WebKit, enabling true multi-browser automation with a single API. It also supports both headless and headed modes, making it flexible for various stages of the testing lifecycle.

GitHub metrics also show Playwright's popularity: it has over 74,000 stars, much larger than Selenium's 32,000. The number of projects depending on Selenium is still large, but Playwright is far away (around 412,000 repositories use Playwright vs. 354,000 for Selenium).

Playwright is an end-to-end testing library for reliable, cross-browser automation. It supports Chromium, Firefox, and WebKit, and allows mocking network responses and testing real user workflows. It offers auto-waiting, resilient web-first assertions, and built-in tracing to eliminate flaky tests.

One thing I hate about building a SaaS is that I'm constantly worried it might break after adding a new feature. To give you peace of mind, we've integrated a full suite of end-to-end tests using Playwright. These tests act like a robot user, clicking through your app to verify that everything from user sign-ups to critical payment flows is working exactly as it should.

Fast and reliable end-to-end testing for modern web apps | Playwright

Playwright v1.54 isn’t a flashy release—but it’s a smart one. With enhanced test annotations, CHIPS-aligned cookie handling, and cleaner reporting, it's setting the groundwork for privacy-centric and maintainable testing at scale.

This guide shows how to test the entire registration flow, including real email confirmation, using Playwright and temporary inboxes created with Tigrmail. You'll get a working test in minutes and a clean way to automate email-based flows.