playwright-dotnet VS library

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!

Give the official QuestPDF repository a star ⭐ so more people will know about it. Most developers evaluate project maturity based on the star count so let's help them make the right decision!

There are already a couple of free or paid libraries in the .NET ecosystem that can be used to generate PDF files. The way how QuestPDF differs is simple: instead of relying on an HTML-to-PDF conversion, it implements its own layouting engine that renders the full content using the SkiaSharp library (a Skia port for .NET, used in Chrome, Android, MAUI, etc.).

Hi, can you please elaborate more about your question? Or create a discussion on the repository page? https://github.com/QuestPDF/library/discussions I am not sure exactly what requirement you would like to achieve :)

QuestPDF is my go-to.

Hi :) That is a good point about most of the APIs available. I truly believe that it does not apply to the QuestPDF library. The Fluent API here is used only to describe the document's content, to create new element instances and assign them to parents. In other words, there is no business logic involved in this code area. Please analyze the QuestPDF.Fluent namespace. You will find that most of the API invocations are super simple and straightforward.

check out https://github.com/questpdf/library